Analyze dependencies and determine what infrastructure must be added to tools/scripts/Set-WellKnown.ps1 and internal/testhelp/wellknown.go so that acceptance tests for a new resource have all…
$ npx skills add microsoft/terraform-provider-fabric --skill wellknown-analyzer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install microsoft/terraform-provider-fabric wellknown-analyzer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/microsoft/terraform-provider-fabric.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/wellknown-analyzer .claude/skills/wellknown-analyzer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "wellknown-analyzer" agent skill from https://github.com/microsoft/terraform-provider-fabric/tree/main/.github/skills/wellknown-analyzer into .claude/skills/wellknown-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wellknown-analyzer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/microsoft/terraform-provider-fabric/tree/main/.github/skills/wellknown-analyzerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add microsoft/terraform-provider-fabric --skill wellknown-analyzer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install microsoft/terraform-provider-fabric wellknown-analyzer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft/terraform-provider-fabric.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/wellknown-analyzer .agents/skills/wellknown-analyzer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "wellknown-analyzer" agent skill from https://github.com/microsoft/terraform-provider-fabric/tree/main/.github/skills/wellknown-analyzer into .agents/skills/wellknown-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wellknown-analyzer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add microsoft/terraform-provider-fabric --skill wellknown-analyzer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install microsoft/terraform-provider-fabric wellknown-analyzer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft/terraform-provider-fabric.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/wellknown-analyzer .cursor/skills/wellknown-analyzer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "wellknown-analyzer" agent skill from https://github.com/microsoft/terraform-provider-fabric/tree/main/.github/skills/wellknown-analyzer into .cursor/skills/wellknown-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wellknown-analyzer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/microsoft/terraform-provider-fabric.git --path .github/skills/wellknown-analyzer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add microsoft/terraform-provider-fabric --skill wellknown-analyzer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install microsoft/terraform-provider-fabric wellknown-analyzer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft/terraform-provider-fabric.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/wellknown-analyzer .gemini/skills/wellknown-analyzer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "wellknown-analyzer" agent skill from https://github.com/microsoft/terraform-provider-fabric/tree/main/.github/skills/wellknown-analyzer into .gemini/skills/wellknown-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wellknown-analyzer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install microsoft/terraform-provider-fabric wellknown-analyzerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add microsoft/terraform-provider-fabric --skill wellknown-analyzer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/microsoft/terraform-provider-fabric.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/wellknown-analyzer .github/skills/wellknown-analyzer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "wellknown-analyzer" agent skill from https://github.com/microsoft/terraform-provider-fabric/tree/main/.github/skills/wellknown-analyzer into .github/skills/wellknown-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wellknown-analyzer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add microsoft/terraform-provider-fabric --skill wellknown-analyzer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install microsoft/terraform-provider-fabric wellknown-analyzer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft/terraform-provider-fabric.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/wellknown-analyzer .opencode/skills/wellknown-analyzer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "wellknown-analyzer" agent skill from https://github.com/microsoft/terraform-provider-fabric/tree/main/.github/skills/wellknown-analyzer into .opencode/skills/wellknown-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wellknown-analyzer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
wellknown-analyzerAnalyze dependencies and determine what infrastructure must be added to tools/scripts/Set-WellKnown.ps1 and internal/testhelp/wellknown.go so that acceptance tests for a new resource have all…
Wellknown Analyzer is an agent skill from microsoft/terraform-provider-fabric, published by the product's own GitHub organization. Analyze dependencies and determine what infrastructure must be added to tools/scripts/Set-WellKnown.ps1 and internal/testhelp/wellknown.go so that acceptance tests for a new resource have all required pre-requisite resources available. USE FOR: analyzing well-known test fixture requirements for new resources, determining creation strategies, and generating code snippets for Set-WellKnown.ps1 and wellknown.go additions.
Its SKILL.md is about 3.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering End-to-end testing and Test data and fixtures. It works with Microsoft Azure and Terraform. The repository describes itself as: Terraform Provider for Microsoft Fabric. The licence is MPL-2.0.
5 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 86c83be. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are powershell and go).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Wellknown Analyzer loads about 3.2k tokens when it runs. Until then it costs about 110 tokens; SKILL.md has 960 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from microsoft/terraform-provider-fabric at commit 86c83be, republished under its MPL-2.0 licence (© microsoft). 960 words, ~3,236 tokens.
.claude/skills/wellknown-analyzer/SKILL.md (or your agent's skills folder).Determine what infrastructure must be added to tools/scripts/Set-WellKnown.ps1 so that acceptance tests for a new resource have all required pre-requisite resources available.
Acceptance tests run against real Fabric APIs and need pre-existing infrastructure. The PowerShell script tools/scripts/Set-WellKnown.ps1 creates all required resources and writes their IDs/metadata to a .wellknown.json fixture that tests consume at runtime.
When adding a new resource, you must determine:
CreationPayload or Definition?Read the SDK analysis (from #skill:sdk-contract-navigator) and Fabric API documentation to answer:
| Question | How to Check | Example |
|---|---|---|
Does Create require a workspace_id? | Almost always yes | All workspace-scoped items |
| Does Create require another resource's ID? | Check CreationPayload for reference fields | KQL Database needs parentEventhouseItemId |
Does Create require a Definition? | Check if API requires definition on create | Report needs definition.pbir, Semantic Model needs definition.pbism |
| Does it have a parent resource relationship? | Check if resource is scoped under another | DigitalTwinBuilderFlow requires a DigitalTwinBuilder |
| Does it need data populated after creation? | Check if tests rely on resource content | Lakehouse needs sample data loaded for shortcut tests |
| Question | How to Check | Example |
|---|---|---|
| Does it need an Azure Resource Group? | Check if the resource references Azure resources | Mounted Data Factory, VNet Gateway |
| Does it need a Storage Account? | Check for blob/storage references | Managed Private Endpoints |
| Does it need a Virtual Network? | Check for VNet/subnet references | Virtual Network Gateway |
| Does it need an Azure Data Factory? | Check for ADF references | Mounted Data Factory |
| Does it need Azure RBAC assignments? | Check if Azure roles must be pre-assigned | Network Contributor on VNet |
| Question | How to Check | Example |
|---|---|---|
| Does it need a Service Principal? | Check for role assignment tests | Role assignment resources |
| Does it need an Entra Group? | Check for group-based assignments | Workspace role assignments |
| Does it need specific app registrations? | Check for OAuth/auth requirements | Connection resources |
| Question | How to Check | Example |
|---|---|---|
| Does it need an AzDO project/repo? | Check for Git integration | Workspace Git |
| Does it need a GitHub connection? | Check for GitHub references | Workspace Git |
| Does it need a Fabric Connection? | Check for connection references | Connection role assignments |
| Does it need a Gateway? | Check for gateway-scoped operations | Gateway role assignments, VNet connections |
Read tools/scripts/Set-WellKnown.ps1 to determine what already exists and what's missing.
Set-FabricItem switch blockLook at the switch ($Type) block in the Set-FabricItem function. If the new item type is missing, it needs an entry mapping to its REST API endpoint:
'<NewItemType>' {
$itemEndpoint = '<camelCasePluralEndpoint>'
}The endpoint is the camelCase plural of the item type (e.g. lakehouses, eventhouses, sqlDatabases, dataPipelines).
$itemNaming hashtableEvery item that gets created needs a short naming abbreviation in $itemNaming:
'<NewItemType>' = '<2-5 char abbreviation>'Determine which creation pattern applies.
If the Fabric API can create the item with just displayName and description, add it to the $itemTypes array:
$itemTypes = @('ApacheAirflowJob', ..., '<NewItemType>', ..., 'Warehouse')The loop handles creation automatically:
foreach ($itemType in $itemTypes) {
$displayNameTemp = "${displayName}_$($itemNaming[$itemType])"
$item = Set-FabricItem -DisplayName $displayNameTemp -WorkspaceId $wellKnown['WorkspaceDS'].id -Type $itemType
$wellKnown[$itemType] = @{
id = $item.id
displayName = $item.displayName
description = $item.description
}
}Fabric Items currently using this pattern: ApacheAirflowJob, CopyJob, Dataflow, DataPipeline, DigitalTwinBuilder, Environment, Eventhouse, GraphQLApi, KQLDashboard, KQLQueryset, Lakehouse, Map, MLExperiment, MLModel, Notebook, Reflex, SparkJobDefinition, SQLDatabase, VariableLibrary, Warehouse
If the API requires a creationPayload on create, add a dedicated block after any dependencies have been created:
# Create <NewItemType> if not exists
$displayNameTemp = "${displayName}_$($itemNaming['<NewItemType>'])"
$creationPayload = @{
<requiredField> = <value>
}
$item = Set-FabricItem -DisplayName $displayNameTemp -WorkspaceId $wellKnown['WorkspaceDS'].id -Type '<NewItemType>' -CreationPayload $creationPayload
$wellKnown['<NewItemType>'] = @{
id = $item.id
displayName = $item.displayName
description = $item.description
}Current examples:
databaseType and parentEventhouseItemId (depends on Eventhouse)digitalTwinBuilderItemReference (depends on DigitalTwinBuilder)parentWarehouseId (depends on Warehouse)If the API requires a definition on create (items that are definition-required):
$displayNameTemp = "${displayName}_$($itemNaming['<NewItemType>'])"
$definition = @{
parts = @(
@{
path = '<definition-path>'
payload = Get-DefinitionPartBase64 -Path 'internal/testhelp/fixtures/<item_type>/<file>.tmpl' -Values @(
@{ key = '{{ .PlaceholderVar }}'; value = $actualValue }
)
payloadType = 'InlineBase64'
}
)
}
$item = Set-FabricItem -DisplayName $displayNameTemp -WorkspaceId $wellKnown['WorkspaceDS'].id -Type '<NewItemType>' -Definition $definition
$wellKnown['<NewItemType>'] = @{
id = $item.id
displayName = $item.displayName
description = $item.description
}Current examples:
mirroring.json definitiondefinition.pbism + model.bimdefinition.pbir + report.json + static resources (depends on SemanticModel)eventstream.json definition (depends on Lakehouse)mountedDataFactory-content.json (depends on Azure Data Factory)This strategy also requires:
internal/testhelp/fixtures/<item_type>/Get-DefinitionPartBase64 to Base64-encode the definition contentFor non-Fabric-Item resources that need dedicated setup:
Azure resources:
# Create Azure resource
$resource = Set-Azure<Resource> -ResourceGroupName $wellKnown['ResourceGroup'].name -Name $displayNameTemp ...
$wellKnown['<ResourceKey>'] = @{
id = $resource.Id
name = $resource.Name
}Fabric connections:
$connection = Set-FabricConnection -DisplayName $displayNameTemp -ConnectivityType "<type>"
$wellKnown['<ConnectionKey>'] = @{
id = $connection.id
displayName = $connection.displayName
}Role assignments:
Set-FabricGatewayRoleAssignment -GatewayId $gatewayId -PrincipalId $principalId -PrincipalType 'ServicePrincipal' -Role 'Admin'Domains:
$domain = Set-FabricDomain -DisplayName $displayNameTemp
$wellKnown['<DomainKey>'] = @{ id = $domain.id; displayName = $domain.displayName }Well-known resources are created sequentially. Ensure dependencies are created before dependents:
$itemTypes arrayIf the new resource depends on something not yet created, note it as a prerequisite.
Output a structured recommendation:
Resource: fabric_<name>
Category: Fabric Item / non-item
Creation Strategy: A (simple) / B (payload) / C (definition) / D (non-item infra)List all identified dependencies:
✅ Already exists: <dependency>
❌ Missing: <dependency> — needs to be addedSet-WellKnown.ps1internal/testhelp/fixtures/Provide ready-to-paste PowerShell code for each required change.
wellknown.go)Well-known data is loaded from internal/testhelp/fixtures/.wellknown.json (or the FABRIC_TESTACC_WELLKNOWN env var) and accessed in tests via:
entity := testhelp.WellKnown()["Lakehouse"].(map[string]any)
entityID := entity["id"].(string)| Key | Purpose |
|---|---|
WorkspaceRS | Resource tests (create/update/delete) |
WorkspaceDS | Data source tests (read-only) |
WorkspaceMPE | Managed private endpoint tests |
WorkspaceOAP | Outbound access policy tests |
tools/scripts/Set-WellKnown.ps1internal/testhelp/wellknown.gointernal/testhelp/fixtures/internal/testhelp/fixtures/.wellknown.json© microsoft, MPL-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .github/skills/wellknown-analyzer of microsoft/terraform-provider-fabric.
Open the folder on GitHubat commit 86c83be
Wellknown Analyzer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Wellknown Analyzer this skillmicrosoft/terraform-provider-fabric | 128 | — | ~3.2k | Automated safety check: Pass | MPL-2.0 | |
| Avm Tf TestingAzure/terraform-azurerm-avm-ptn-alz | 135 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Java SDK E2E Test with Replay Snapshotgithub/copilot-sdk | 11k | — | ~1.8k | Automated safety check: Pass | MIT | |
| source-mssql E2E Test Harnessairbytehq/airbyte | 22k | — | ~4.4k | Automated safety check: Pass | Custom licence | |
| Airbyte source-mysql E2E Testsairbytehq/airbyte | 22k | — | ~2.6k | Automated safety check: Pass | Custom licence | |
| Airbyte Postgres Source E2E Testsairbytehq/airbyte | 22k | — | ~2.5k | Automated safety check: Pass | Custom licence |
Azure/terraform-azurerm-avm-ptn-alz
A skill your agent uses for AVM Terraform validation, provider-mocked unit tests, real-Azure integration tests, E2E example tests, PowerShell hooks, OIDC, policy checks, and Avm.Authoring CI behavior.
github/copilot-sdk
Creates a Java SDK end-to-end test for the Copilot SDK that runs against a recorded YAML snapshot through a replay proxy, so CI needs no real authentication.
airbytehq/airbyte
Stands up a throwaway local SQL Server 2022 backend, applies SQL fixtures and runs Airbyte spec, check, discover and read against source-mssql images.
airbytehq/airbyte
Stands up a throwaway local MySQL 8.0 backend, applies SQL fixtures and sweeps the Airbyte spec, check, discover and read commands against a source-mysql image.
airbytehq/airbyte
Starts a local PostgreSQL 16 container, loads SQL fixtures and runs the Airbyte spec, check, discover and read commands against a chosen source-postgres image.
kubernetes-sigs/cloud-provider-azure
Parse a Go e2e test from tests/e2e/, translate each step to kubectl and az CLI commands, and interactively replay the test against a live cluster.
microsoft/terraform-provider-fabric
Given SDK analysis results, automatically determine the correct itemgen archetype and build the full go run tools/itemgen/main.go command.
microsoft/terraform-provider-fabric
Given a Go SDK contract (DTOs), generate the corresponding Terraform schema attributes and model structs with high fidelity.
microsoft/terraform-provider-fabric
Navigate the fabric-sdk-go SDK source to find the correct client factory, DTOs, item type constants, and pager methods for a given Fabric Item or non-item resource.
microsoft/terraform-provider-fabric
Research SDK contracts, design Terraform schema approach, and compose a GitHub issue for a new resource, data source, ephemeral resource, or enhancement to an existing resource.
Works with
Categories
Analyze dependencies and determine what infrastructure must be added to tools/scripts/Set-WellKnown.ps1 and internal/testhelp/wellknown.go so that acceptance tests for a new resource have all…. Wellknown Analyzer is an agent skill from microsoft/terraform-provider-fabric, published by the product's own GitHub organization.go so that acceptance tests for a new resource have all required pre-requisite resources available.
Wellknown Analyzer fits situations like: : analyzing well-known test fixture requirements for new resources; determining creation strategies; generating code snippets for Set-WellKnown.ps1 and wellknown.go additions.
Run `npx skills add microsoft/terraform-provider-fabric --skill wellknown-analyzer -a claude-code`. Or copy the skill folder (.github/skills/wellknown-analyzer in microsoft/terraform-provider-fabric) into .claude/skills/wellknown-analyzer in your project. Claude Code loads it when a task matches its description.
Run `npx skills add microsoft/terraform-provider-fabric --skill wellknown-analyzer -a codex`. Or copy the skill folder (.github/skills/wellknown-analyzer in microsoft/terraform-provider-fabric) into .agents/skills/wellknown-analyzer in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add microsoft/terraform-provider-fabric --skill wellknown-analyzer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/wellknown-analyzer, .gemini/skills/wellknown-analyzer, .github/skills/wellknown-analyzer and .opencode/skills/wellknown-analyzer in your project.
SKILL.md names no scripts, command-line tools or credentials: Wellknown Analyzer is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Wellknown Analyzer is published under the MPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.2k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Wellknown Analyzer: Avm Tf Testing (Azure/terraform-azurerm-avm-ptn-alz, 135 stars), Java SDK E2E Test with Replay Snapshot (github/copilot-sdk, 11k stars), source-mssql E2E Test Harness (airbytehq/airbyte, 22k stars) and Airbyte source-mysql E2E Tests (airbytehq/airbyte, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
microsoft (a GitHub organization, an official publisher) maintains it in microsoft/terraform-provider-fabric, which has 128 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 6, 2026.
Source: microsoft/terraform-provider-fabric on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.
