Anti-Patterns

Don't	Why
Create skill without SDK context	Users must provide package name/docs URL
Put "when to use" in body	Body loads AFTER triggering
Hardcode credentials	Security risk
Skip authentication section	Agents will improvise poorly
Use outdated SDK patterns	APIs change; search docs first
Include README.md	Agents don't need meta-docs
Deeply nest references	Keep one level deep
Skip acceptance criteria	Skills without tests can't be validated
Skip symlink categorization	Skills won't be discoverable by category
Use wrong import paths	Azure SDKs have specific module structures
Omit sync/async + context-manager bullets from Best Practices in Python skills	End users won't follow rules that aren't written down; examples alone aren't enough
Mix sync and async in the same Python example	Demonstrates the anti-pattern the skill is supposed to prevent
Ship regenerated skills with zero test scenarios	Hero workflows and regressions cannot be validated
Claim full API coverage from a single happy-path sample	Hides operation-group and non-hero gaps users need for production
Omit references/*.md coverage for non-hero capabilities	Forces advanced capabilities out of context and leaves API breadth undocumented