agentleFS
Sign inStart free
stevemarksavastevemarksava/superteam/skills/fabric-onelake/SKILL.md

fabric-onelake

Skill1 starsChanged 2 months agoMITView on GitHub

OneLake structure — workspaces, capacity, shortcuts, Delta Lake tables, Domains. The Fabric storage plane laid out cleanly.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never copy data across workspaces when a shortcut works — shortcuts are the OneLake idiom

    line 31
  2. Distinctive:

    Every workspace has a Domain assignment — orphan workspaces fail governance audits

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/fabric-onelake — OneLake Storage and Organisation

OneLake is Fabric's single logical data lake — one tenant, many workspaces, all data addressable via a unified namespace. This skill lays out workspaces, capacity, shortcut strategy, and Delta table registration so the lake stays navigable as it grows.

When to invoke

  • New Fabric tenant or a new capacity is being provisioned
  • Atlas needs a workspace plan across dev/test/prod for a Fabric engagement
  • Cross-workspace data sharing (shortcuts) must be designed before ingestion
  • A Domain (Fabric governance construct) needs to be introduced for a business unit

Steps

  1. Workspace and capacity plan. Enumerate workspaces by lifecycle: <project>-dev, <project>-test, <project>-prod. Map each to a capacity SKU (F2 through F2048 — verify current SKUs at author time). Note per-workspace admin roles.
  2. OneLake path convention. OneLake addresses look like abfss://<workspace>@onelake.dfs.fabric.microsoft.com/<item>.<itemtype>/Files/... or .../Tables/.... Pin conventions: Tables/<zone>/<entity> for lakehouses, Files/raw/<source>/<yyyy>/<mm>/<dd>/ for landing zones.
  3. Shortcuts — cross-workspace and external. For internal reuse, create OneLake shortcuts from consumer workspace back to a producer workspace's gold table (no copy, zero storage cost). For external data (ADLS Gen2, S3, GCS, Dataverse), use shortcuts rather than copy where policy allows. Document every shortcut in the workspace README.
  4. Delta Lake table registration. Register lakehouse tables so SQL, Spark, and Power BI can all read them. Use V-Order optimisation for Power BI read speed. Set retention (vacuum cadence) explicitly — default 7 days is safe but confirm with governance.
  5. Domains organisation. Group workspaces into Domains by business area (Finance, HR, Retail). Domains are Fabric's governance boundary — data owners, endorsements, discovery scope. Every workspace belongs to exactly one Domain.
  6. Access model. Workspace roles (Admin/Member/Contributor/Viewer) at the workspace level; item-level permissions only when a workspace-wide role is too broad. Never grant tenant-admin as a shortcut.

Deliverable format

  • onelake-layout.md — workspace list with capacity SKU, Domain, and lifecycle role
  • shortcuts.md — every shortcut with source, target, and business justification
  • Naming-convention crib sheet ready to paste into workspace READMEs

Non-negotiables

  • Never copy data across workspaces when a shortcut works — shortcuts are the OneLake idiom
  • Every workspace has a Domain assignment — orphan workspaces fail governance audits
  • Capacity SKU is planned, not accidental — right-size against peak Spark + DirectLake load
  • Delta tables always use V-Order for gold-tier read paths

References

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free