skf-create-stack-skill

You can document library integration patterns by scanning dependency manifests and source code to detect co-import patterns, classify integration types, and extract usage conventions with confidence tiers.

A stack skill is a consolidated documentation of how libraries connect within a technology stack. You need to generate one to document cross-library integration conventions and dependency analysis from a project codebase.

Yes, you can build stack skills without a codebase using Compose-Mode Synthesis, which builds consolidated stack skills from pre-existing individual skills and architecture documents while inheriting confidence tiers from source skills.

AST tools are not strictly required for dependency analysis. The core mechanism uses manifest parsing and grep-based co-import detection, with AST or temporal enrichment tools serving as optional inputs for deeper analysis.

You can flag risky integration pairs by incorporating verification verdicts from architecture feasibility reports into the stack skill, marking blocked or risky cross-library integrations during the synthesis process.