fabric-deploy
Skill49 starsChanged 6 months agoMITView on GitHub
⚠️ Artifacts-only mode: When deploy_mode is artifacts_only, this skill is NOT invoked — the pipeline runner handles this phase deterministically. The instructions below apply only when deploy_mode is live. ⚡ Pre-generated handoff: The runner writes deployment-handoff.md with every item in status: not_started and <!-- AGENT: FILL --> markers before this skill is invoked, alongside deploy/workspace/, config.yml, the deploy script, and the taskflow JSON. Your job after running (or choosing to skip) deployment is to update each item's status to deployed…
1 other project uses a version of this.
Adopted by
Most recently taken up by
- wardawgmalvicious/agent-configtheir own version, first seen Oct 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- wardawgmalvicious/agent-config★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
- fabric-designSkill
- fabric-discoverSkill
- fabric-documentSkill
- fabric-healSkill
- fabric-testSkill
- grill-with-docsSkill
- handoffSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 2 are distinctive, and 6 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.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
Check the deploy_mode field in the agent prompt (set in pipeline-state.json):
- Very specific: line 41
After the user confirms deployment is complete, update each item in deployment-handoff.md to status: deployed (or failed with a reason), …
- Very specific: line 47
All items set to status: planned
- Very specific: line 53
Do NOT read registry JSON files directly — use Python tools (deploy-script-gen.py, registry_loader)
- Distinctive: line 54
Follow the architecture handoff exactly — no design decisions
- Distinctive: line 55
Never proceed to next wave if current wave has failures
- Very specific: line 63
Read _projects/[name]/docs/remediation-log.md.
- Very specific: line 77
If category: design → set outcome: escalated, STOP.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
⚠️ Artifacts-only mode: When
deploy_modeisartifacts_only, this skill is NOT invoked — the pipeline runner handles this phase deterministically. The instructions below apply only whendeploy_modeislive.
Fabric Deployment
⚡ Pre-generated handoff: The runner writes
deployment-handoff.mdwith every item instatus: not_startedand<!-- AGENT: FILL -->markers before this skill is invoked, alongsidedeploy/workspace/,config.yml, the deploy script, and the taskflow JSON. Your job after running (or choosing to skip) deployment is to update each item's status todeployed/failedand replace every<!-- AGENT: FILL -->marker with real content.
Deployment Mode
Check the deploy_mode field in the agent prompt (set in pipeline-state.json):
live— User wants to deploy to a live Fabric workspace. Present the deploy script and guide them through running it.artifacts_only(default) — No live deployment. Review generated artifacts and write the handoff with items inplannedstatus.
Instructions
Step 1: Verify Artifacts
Confirm deploy/ contains: .platform files, config.yml, deploy script, and taskflow JSON (auto-generated by pipeline).
Step 2: Deploy or Review
If deploy_mode is live:
Present the deploy script to the user and instruct them to run it:
cd _projects/[name]/deploy
python deploy-[name].pyThe script handles: workspace creation, capacity assignment, fabric-cicd deployment, and Variable Library population — all interactively. The user must have Azure credentials (az login).
After the user confirms deployment is complete, update each item in deployment-handoff.md to status: deployed (or failed with a reason), and replace every <!-- AGENT: FILL --> marker.
If deploy_mode is artifacts_only:
Review the generated artifacts. Present a summary of what would be deployed (items, waves, script location). Update deployment-handoff.md:
deployment_mode: artifacts_only- All items set to
status: planned - Fill in Implementation Notes (deviations only) and the Configuration Rationale table
- Replace every
<!-- AGENT: FILL -->marker
Constraints
- Do NOT read registry JSON files directly — use Python tools (
deploy-script-gen.py,registry_loader) - Follow the architecture handoff exactly — no design decisions
- Never proceed to next wave if current wave has failures
Mode 2: Remediation (Phase 3+)
Fix deployment and configuration issues identified during validation.
Step 1: Load Remediation Log
Read _projects/[name]/docs/remediation-log.md. Filter issues where routed_to: engineer.
Step 2: Fix Issues
- Deployment issues — re-deploy item via
fabric-cicd, verify withvalidate-items.py - Configuration issues — update settings via Fabric REST API or portal, re-run validation
- Transient issues — wait appropriate interval, retry validation
Step 3: Update Remediation Log
Set status: resolved, fill resolution (max 20 words), record resolved_iteration.
Step 4: Escalate Design Issues
If category: design → set outcome: escalated, STOP. Cannot fix architecture — escalate.
Step 5: Trigger Re-Validation
Set outcome: remediated and advance pipeline to re-trigger QA validation.
Max 3 remediation iterations.
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
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.

