Awesome Tech Writing Curator
Use this skill to keep readme.md accurate, narrowly scoped, and easy to
review.
Load First
Read references/repo-standards.md before editing readme.md. It captures the
repo scope, section taxonomy, entry format, sort rules, and recurring gotchas.
Curation Workflow
- Read
readme.md and contributing.md.
- Classify each candidate resource into one current section:
Agent & LLM Skills: concrete agent skills, skill directories, or
machine-readable skill definitions for docs workflows.AI Prompt Libraries: reusable prompt packs for technical writing tasks.Best Practices: guidance on creating, prompting, evaluating, or operating
agent skills and AI-assisted writing workflows.Tools: utilities for creating, validating, or managing skills.
- Reject or flag resources that are outside scope:
- Generic technical writing tutorials, courses, newsletters, or blog posts.
- General writing tools or editors.
- Documentation platforms without machine-readable writing skills, prompts,
lint rules, or skill tooling.
- Resources requiring login for basic inspection.
- Verify the destination section is present in the contents list and has a
matching heading.
- Add or update entries in this exact format:
- [Resource Name](URL): One to two factual sentences explaining what the resource is and why it is relevant to LLM-assisted technical writing workflows.
- Keep entries within each section alphabetized by visible resource name,
case-insensitive.
- Keep descriptions factual and concise. Avoid marketing claims such as
"powerful," "best," "ultimate," or "revolutionary."
- Run the validator:
python3 skills/awesome-tech-writing-curator/scripts/validate_readme.py readme.md
- Fix any reported issues and rerun the validator until it passes.
Description Pattern
Use this shape for descriptions:
- [Name](URL): A [specific type] from [source or project] for [specific docs or skill workflow], useful because [concrete relevance].
Good descriptions answer both:
- What is it?
- Why does it belong in this list?
Gotchas
- The repo file is
readme.md, lowercase.
- Do not add a new section for a single resource. New sections need at least
two fitting resources and a clear distinction from existing sections.
- YouTube resources belong in
Best Practices only when they are guidance for
prompting, skill creation, or agent operation. Generic video tutorials do not
belong.
- For GitHub directories, describe the collection, not just the repository.
- Preserve existing prose style: concise, plain, and contribution-oriented.
1---2name: awesome-tech-writing-curator3description: Maintain the Awesome Technical Writing Skills README. Use when adding, editing, moving, de-duplicating, or validating README entries, sections, descriptions, anchors, or contribution-facing list content for this repository.4---56# Awesome Tech Writing Curator78Use this skill to keep `readme.md` accurate, narrowly scoped, and easy to9review.1011## Load First1213Read `references/repo-standards.md` before editing `readme.md`. It captures the14repo scope, section taxonomy, entry format, sort rules, and recurring gotchas.1516## Curation Workflow17181. Read `readme.md` and `contributing.md`.192. Classify each candidate resource into one current section:20 - `Agent & LLM Skills`: concrete agent skills, skill directories, or21 machine-readable skill definitions for docs workflows.22 - `AI Prompt Libraries`: reusable prompt packs for technical writing tasks.23 - `Best Practices`: guidance on creating, prompting, evaluating, or operating24 agent skills and AI-assisted writing workflows.25 - `Tools`: utilities for creating, validating, or managing skills.263. Reject or flag resources that are outside scope:27 - Generic technical writing tutorials, courses, newsletters, or blog posts.28 - General writing tools or editors.29 - Documentation platforms without machine-readable writing skills, prompts,30 lint rules, or skill tooling.31 - Resources requiring login for basic inspection.324. Verify the destination section is present in the contents list and has a33 matching heading.345. Add or update entries in this exact format:3536```markdown37- [Resource Name](URL): One to two factual sentences explaining what the resource is and why it is relevant to LLM-assisted technical writing workflows.38```39406. Keep entries within each section alphabetized by visible resource name,41 case-insensitive.427. Keep descriptions factual and concise. Avoid marketing claims such as43 "powerful," "best," "ultimate," or "revolutionary."448. Run the validator:4546```bash47python3 skills/awesome-tech-writing-curator/scripts/validate_readme.py readme.md48```49509. Fix any reported issues and rerun the validator until it passes.5152## Description Pattern5354Use this shape for descriptions:5556```markdown57- [Name](URL): A [specific type] from [source or project] for [specific docs or skill workflow], useful because [concrete relevance].58```5960Good descriptions answer both:6162- What is it?63- Why does it belong in this list?6465## Gotchas6667- The repo file is `readme.md`, lowercase.68- Do not add a new section for a single resource. New sections need at least69 two fitting resources and a clear distinction from existing sections.70- YouTube resources belong in `Best Practices` only when they are guidance for71 prompting, skill creation, or agent operation. Generic video tutorials do not72 belong.73- For GitHub directories, describe the collection, not just the repository.74- Preserve existing prose style: concise, plain, and contribution-oriented.
subin23k