AGENT SKILL

markdown-doc-quality

暂无简介

License 许可
MIT
最近更新
2026-11-15
Stars
★ 2
Forks
1

03 SKILL.md 正文

../../../.github/skills/coding-standards/markdown-doc-quality/SKILL.md

04 同仓库更多 Skills

doruit
doruit/forged-with-foundry

linkedin-post-writer

Generates rich, engagement-optimized LinkedIn posts announcing new AI governance control demos, weekly/monthly repo updates, and category-completion milestones for Forged with Foundry

★ 2
doruit
doruit/forged-with-foundry

markdown-doc-quality

Detects AI-slop patterns in Markdown documentation: heading/body contradictions, unverified external claims, hedging filler, missing evidence examples, and inconsistent terminology across .md files

★ 2
doruit
doruit/forged-with-foundry

assess-governance-control

Assess a governance control before implementation

★ 2
doruit
doruit/forged-with-foundry

mermaid-infra-diagram

Generate a control's 'Demo infrastructure setup (simplified)' diagram with real Microsoft/Azure service icons instead of abstract colored boxes. Primary path: draw.io XML rendered headlessly via the bundled VS Code draw.io extension, using the official Azure Public Service Icons set indexed at media/icons/Azure_Public_Service_Icons/icon-index.jsonl. Fallback path: Mermaid architecture-beta with Iconify icon packs, pre-rendered because GitHub does not render Mermaid icon packs live. For controls that deploy Azure resources, follow the KNW-001 reference layout: nested subscription, resource group and resource boundaries, a legend, an outside-scope band and tiered icon sizes. Use when creating or refreshing a control's Demo infrastructure setup (simplified) section, or when a plain flowchart diagram should show recognizable real-world service icons instead of abstract colored boxes.

★ 2
doruit
doruit/forged-with-foundry

linkedin-post-writer

暂无简介

★ 2
doruit
doruit/forged-with-foundry

control-demo-roast

Adversarial pre-announcement review of a Forged with Foundry control demo -- run before linkedin-post-writer, not instead of it -- to catch overclaiming, unproven mechanisms, and stale estimates that would embarrass the team once a technical community actually tries the demo

★ 2