Skip to content
Back to skills

030 Templates De80ec04

ASecurity

Templates are your primary tool for writing READMEs. References provide depth - use them to refine your understanding or handle edge cases. **Tip:** Don't load all references at once. Pick the one most relevant to your situation. --- `references/art-of-readme.md` **Why:** The philosophy behind great READMEs - understanding how readers actually scan and evaluate projects **What:** Cognitive funneling (broad → specific), brevity as a feature, README as the "one-stop shop" that keeps users out o...

  • 9 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 11, 2026
documentationgo

Security analysis

A100/100

Scanned October 11, 2026

npx -y skills add tools-only/X-Skills --skill 030-templates_de80ec04 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of 030 Templates De80ec04?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for 030 Templates De80ec04
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tools-only-030-templates-de80ec04/badge)](https://www.skillsdirectory.com/skills/tools-only-030-templates-de80ec04)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

SKILL.md
# Using References

Templates are your primary tool for writing READMEs. References provide depth - use them to refine your understanding or handle edge cases.

**Tip:** Don't load all references at once. Pick the one most relevant to your situation.

---

### art-of-readme.md
`references/art-of-readme.md`

**Why:** The philosophy behind great READMEs - understanding how readers actually scan and evaluate projects
**What:** Cognitive funneling (broad → specific), brevity as a feature, README as the "one-stop shop" that keeps users out of source code

---

### make-a-readme.md
`references/make-a-readme.md`

**Why:** Practical, section-by-section guidance for what to include
**What:** Walks through each common section (Name, Description, Installation, Usage, etc.) with concrete suggestions. Good reminder: "too long is better than too short"

---

### standard-readme-spec.md
`references/standard-readme-spec.md`

**Why:** Formal specification when consistency or compliance matters
**What:** Required vs optional sections, exact ordering, formatting rules. Useful for OSS projects wanting a standardized format.

Examples:
- `references/standard-readme-example-minimal.md` - Bare minimum compliant README
- `references/standard-readme-example-maximal.md` - Full-featured with badges, ToC, all optional sections


Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…