generate-project-skill

# Generate a project Skill Create a compact, searchable Skill from the project itself. This Skill is for maintainers who author a draft Skill they own. ## Inputs Use the project directory or prepared project source. Ask for the destination only when the request does not provide one. ## Inspect 1. Read project instructions and decision records first. 2. Read manifests, exported entry points, and build configuration. 3. Find the test, lint, typecheck, build, and release commands. 4. Trace the main public workflows through their real entry points. 5. Note generated directories and files an Agent must not edit. 6. Check recent changes when they explain current conventions. ## Project navigation 1. Identify the project name, purpose, key files, and main directories. 2. Use project-relative paths for every file pointer. 3. Add focused search commands for source and documentation. 4. Keep search results linked to the real project files. 5. Never add a generated directory prefix to a project-relative path. 6. Tell the Agent when project changes require a new Skill run. Ignore dependency directories, version-control data, generated output, caches, and credentials. Do not follow symbolic links while collecting project files. ## Output Write one directory whose name matches the Skill name. The directory must contain `SKILL.md`. Use `references/` for architecture details and command guides. Use `scripts/` only for reusable automation. The `SKILL.md` frontmatter must contain on...