We split this skill into the rules it gives an agent

11 rules. About 0 are common, 9 are distinctive, and 2 are very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈9

  Distinctive · estimate

  This author's own choices. Worth a look.

• 2

  Very specific

  Tied to their project's names, files or tools. Probably skip.

• Common
• Distinctive
• Very specific

1. Distinctive:

   Use this skill when a user wants a project initialized with practical Markdown files for agents and collaborators.

   line 10
2. Very specific:

   Check for existing AGENTS.md, CONTRIBUTING.md, DESIGN.md, .github/ISSUE_TEMPLATE/*, and .github/pull_request_template.md.

   line 16
3. Distinctive:

   Default: create all bundled templates.

   line 19
4. Distinctive:

   If the user names specific files, create only those files.

   line 20
5. Distinctive:

   If the project already has equivalent files, either leave them alone or make a focused patch that matches the existing style.

   line 21
6. Distinctive:

   Run the scaffold script when a full default scaffold is appropriate:

   line 22
7. Very specific:

   Use --force only when the user has explicitly approved overwriting existing files.

   line 28
8. Distinctive:

   Keep instructions concise and project-specific.

   line 32
9. Distinctive:

   Avoid vendor-specific agent names unless the user requests them.

   line 33
10. Distinctive:

    If the target is a git repository, inspect git status --short.

    line 36
11. Distinctive:

    Prefer editing the generated files in the target project instead of modifying the bundled templates unless the user is improving this skill …

    line 49

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.