Write a new doc in the right place with the right name. An agent skill from hashgraph-online/awesome-codex-plugins.

Apache-2.0Auto-check passedDevelopment

Install Author

skills CLI
$ npx skills add hashgraph-online/awesome-codex-plugins --skill author -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install hashgraph-online/awesome-codex-plugins author --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/MedAdemBHA/docflow/skills/author .claude/skills/author && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
author
GitHub stars
1.2k
Token cost
~1.7k tokens
SKILL.md length
663 words
Files
1
Skills in repo
686
Repo updated
First seen
Licence
Apache-2.0

At a glance

Write a new doc in the right place with the right name. An agent skill from hashgraph-online/awesome-codex-plugins.

  • Works in 5 steps: Pick the category (what is this doc?) → Apply the naming pattern → Fill the template (or generate a draft… → …
  • Asked to write a doc
  • SKILL.md covers Writing style (enforce on…, 1 — Pick the category (what is…, 2 — Apply the naming pattern and 3 — Fill the template (or…, plus 2 more sections
  • Calls bash

What it does

Author is an agent skill from hashgraph-online/awesome-codex-plugins. Write a new doc in the right place with the right name. Use when asked to "write a doc", "where should this doc go", "add an ADR", "document this decision", "new spec", or "new feature plan".

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Architecture decision records. The repository describes itself as: A curated list of awesome OpenAI Codex / ChatGPT plugins, skills, and resources. The 1 Codex Marketplace. See live plugins at: https://hol.org/plugins/best-codex-plugins. The licence is Apache-2.0.

When your agent uses it

  • Asked to write a doc
  • Where should this doc go
  • Document this decision
  • New feature plan

Example prompts

  • “write a doc”
  • “where should this doc go”
  • “add an ADR”
  • “/author”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Pick the category (what is this doc?)
  2. Apply the naming pattern
  3. Fill the template (or generate a draft from code)
  4. Cross-link (no orphan docs)
  5. After writing

What it can do on your machine

Read from SKILL.md and the folder at commit 78497e5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • bash

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Author loads about 1.7k tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 663 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~50
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from hashgraph-online/awesome-codex-plugins at commit 78497e5, republished under its Apache-2.0 licence (© hashgraph-online). 663 words, ~1,651 tokens.

Download SKILL.mdSave it as .claude/skills/author/SKILL.md (or your agent's skills folder).
name
author
description
Write a new doc in the right place with the right name. Use when asked to "write a doc", "where should this doc go", "add an ADR", "document this decision", "new spec", or "new feature plan".

author

Author docs the docflow way: choose category → apply naming → fill template → cross-link. Companion of router (read side) and changelog (history). Templates live in the plugin's templates/ dir; /docflow:init drops them into a repo.

A doc's filename should tell a teammate what + when without opening it. If it can't, rename.

Writing style (enforce on every doc)

Direct, tech + business. No filler.

  • Tables and bullets over paragraphs. One claim per line.
  • Lead with the outcome/decision; cut "this document describes…", "in order to", "it is important to note".
  • Concrete: names, paths, numbers, commit hashes. No adjectives that carry no info.
  • Each section earns its place — if a placeholder stays empty, delete the section.
  • Max one short intro line per doc; the structure does the rest.

1 — Pick the category (what is this doc?)

The doc answers…CategoryFolder
WHAT a feature does (user-facing)product specproduct-spec/
HOW it's built (data flow, API contract, lifecycle)technical specspecs/
WHY we chose an approachdecision (ADR)decisions/
HOW to do X / a convention / cheat sheetreferencereferences/
WHAT's planned / status / roadmapplanplans/ (features/, hygiene/, upcoming/)
Current quality / known bugs / auditreviewreviews/ (active/, archive/, bugs/)
WHAT shipped, by monthchangelogchangelog/ — see changelog

One doc, one category. If it spans two, it's two docs that cross-link.


2 — Apply the naming pattern

FolderPatternExample
product-spec/NN-topic.md (stable, reading order)04-jobs.md
specs/(mmm-yy)-topic.md (dated snapshot)(apr-26)-tab-system-workflow.md
references/topic.md (stable)newtable-component.md
decisions/NNNN-title.md (monotonic, never reused)0001-url-as-state.md
plans/features/(mmm-yy)-feature-name.md(apr-26)-create-job-stepper.md
plans/hygiene/(mmm-yy)-topic.md(apr-26)-codebase-cleanup.md
plans/upcoming/rolling roadmap, no datescritical.md, now.md, next.md, later.md
reviews/active/,archive/(mmm-yy)-topic.md(may-26)-tab-system.md
changelog/(mmm-yy).md(may-26).md

Rules:

  • kebab-case always — never camelCase or snake_case.
  • (mmm-yy)- prefix on dated docs: lowercase 3-letter month + 2-digit year — jan feb mar apr may jun jul aug sep oct nov dec.
  • Stable numbers (NN-, NNNN-) for ordered series that are not snapshots — product-spec reading order, ADRs.
  • No redundant suffixes — never -feature.md, -spec.md, -doc.md. Add a qualifier only when a sibling would otherwise collide (tab-system-overview + tab-system-qa-guide).
  • Topic prefix groups siblings so they sort together ((apr-26)-tab-system-*).

Show full SKILL.md (329 more words)Show less

3 — Fill the template (or generate a draft from code)

Don't start specs/plans from blank — generate a draft from the real repo, then verify:

  • Spec: bash scripts/docflow-spec.sh <code-path> → pre-fills files, exports (Architecture), types (Data), paths+verbs (API), hooks (Flow). You group + confirm + write Risks.
  • Plan: bash scripts/docflow-plan.sh --days 30 → backlog candidates from TODO/FIXME + git churn. You triage into horizons.

Both write drafts marked <!-- auto -->; curate before shipping. Then fill manually where heuristics can't reach:

Each category has a skeleton in the plugin's templates/. Key shapes:

ADR (decisions/NNNN-title.md):

markdown
# NNNN — Title

> **Status:** proposed | accepted | superseded by [NNNN](...) | deprecated
> **Date:** YYYY-MM-DD
> **Deciders:** names/handles

## Context        — what forced the decision? constraints, prior pain
## Decision       — what we chose (one sentence, then detail)
## Consequences   — good / bad / what gets harder
## Alternatives considered  — each + why rejected

Write an ADR for: cross-cutting choices, non-obvious trade-offs, reversals (supersede the old one — never edit it). NOT for: version bumps, one-file refactors, taste.

Spec (specs/(mmm-yy)-topic.md): header block (Module: / Route: / Branch:), then numbered sections — architecture, data model, API surface, state, edge cases. Plus a Related: block linking plan + review + ADRs.

Feature plan (plans/features/(mmm-yy)-name.md): Status / Owner / Surface header, then ## What shipped (table w/ commit refs) · ## In flight · ## Queued.

Review (reviews/...): Last updated / Scope header, scorecard table, P0/P1/P2 findings.


Bidirectional. The chain that ties a feature together:

product-spec/NN-feature.md   (WHAT)
   ↕
specs/(mmm-yy)-feature.md     (HOW)  ──► decisions/NNNN-*.md  (WHY)
   ↕
plans/features/(mmm-yy)-feature.md  (STATUS)
   ↕
reviews/active/(mmm-yy)-feature.md  (QUALITY)
  • Every spec ends with a Related: list (plan, review, ADRs).
  • Every ADR links the specs/product-specs it affects.
  • The docs-root README.md indexes everything — add your new doc to it.
  • Filenames with parentheses must be wrapped in angle brackets in links, or the renderer breaks: [text](<specs/(may-26)-file.md>) — not [text](specs/(may-26)-file.md).

5 — After writing

  1. Regenerate the map: bash scripts/docflow-map.sh <DOCS_ROOT> → updates <DOCS_ROOT>/INDEX.md (the compact path — purpose tree every agent reads first). New doc needs a clear H1 — that becomes its one-liner.
  2. Add the doc to the docs-root README.md index + the folder's own README if it has one.
  3. Record the document change in ## Update Log or the feature/changelog table.
  4. Run bash scripts/docflow-validate.sh --target <REPO ROOT> and fix validation errors before reporting completion.
  5. If a decision shipped or a plan item completed, reflect it in changelog/ (see changelog).
  6. On rename: update the file, grep -rn "old-name\.md" every cross-link, fix README entries, re-run the link check.
bash
# link integrity — empty output = all local links resolve
bash scripts/check-links.sh <DOCS_ROOT>

© hashgraph-online, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/MedAdemBHA/docflow/skills/author of hashgraph-online/awesome-codex-plugins.

Open the folder on GitHubat commit 78497e5

Compare with similar skills

Author next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Author compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Author this skillhashgraph-online/awesome-codex-plugins1.2k—~1.7kAutomated safety check: PassApache-2.0
PR Design DocOpenHands/OpenHands90k—~2.4kAutomated safety check: PassMIT
Cto AdvisorIbrahim-3d/orchestrator-supaconductor3804 repos~2.4kAutomated safety check: PassMIT
Improve Codebase Architectureywwynm/EverythingDone14415 repos~1.3kAutomated safety check: PassGPL-3.0
Domain Modelingbrim-borium/spotify_sdk1665 repos~806Automated safety check: PassApache-2.0
Design Doc MermaidSpillwaveSolutions/design-doc-mermaid1751 repos~5.6kAutomated safety check: PassNone

Similar skills

  • PR Design Doc

    OpenHands/OpenHands

    For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…

    90k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed
  • Cto Advisor

    Ibrahim-3d/orchestrator-supaconductor

    Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.

    380 GitHub starsUsed in 4 repos~2.4k tokens
    DevelopmentAuto-check passed
  • Improve Codebase Architecture

    ywwynm/EverythingDone

    Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/.

    144 GitHub starsUsed in 15 repos~1.3k tokens
    DevelopmentAuto-check passed
  • Domain Modeling

    brim-borium/spotify_sdk

    Build and sharpen a project's domain model. An agent skill from brim-borium/spotify_sdk.

    166 GitHub starsUsed in 5 repos~806 tokens
    DevelopmentAuto-check passed
  • Design Doc Mermaid

    SpillwaveSolutions/design-doc-mermaid

    Create Mermaid diagrams (flowchart, sequence, class, ER, state, C4, architecture) from text or source code.

    175 GitHub starsUsed in 1 repo~5.6k tokens
    DevelopmentAuto-check passed
  • Learning Opportunities

    DrCatHicks/learning-opportunities

    Facilitates deliberate skill development during AI-assisted coding.

    2.5k GitHub stars~2.5k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

More from hashgraph-online/awesome-codex-plugins

All 686 skills in this repo
  • Anime Reaction Gif

    hashgraph-online/awesome-codex-plugins

    Create original anime-style reaction stickers as looping GIFs and MP4 previews, using generated character pose sheets and timed key poses.

    1.2k GitHub stars~922 tokensUpdated today
    Auto-check passed
  • Calibredb

    hashgraph-online/awesome-codex-plugins

    Manage and query Calibre libraries with the calibredb CLI (local paths or Calibre Content server URLs).

    1.2k GitHub stars~1k tokensUpdated today
    Auto-check passed
  • Rust API Test Harness

    hashgraph-online/awesome-codex-plugins

    A skill your agent uses when adding, changing, testing, or debugging Rust HTTP APIs and services, especially when Codex needs black-box integration tests, random-port app startup, real database test…

    1.2k GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Art

    hashgraph-online/awesome-codex-plugins

    Make a studio's game look like something at build time — a cover from a real frame of the game (free), painted covers, backdrops, textures and character plates from image models through the…

    1.2k GitHub stars~2.4k tokensUpdated today
    Auto-check passed
  • Game Balance Economy

    hashgraph-online/awesome-codex-plugins

    Balance game difficulty, resources, rewards, probability, progression, economies, and dominant strategies.

    1.2k GitHub stars~618 tokensUpdated today
    Auto-check passed
  • Manuscript Engagement Analytics

    hashgraph-online/awesome-codex-plugins

    Analyze nonfiction manuscripts for reader engagement signals, including heading-level word counts, slow starts, long slogs, weak takeaway titles, value pacing, beta-reader comment dropoff, and…

    1.2k GitHub stars~875 tokensUpdated today
    Auto-check passed

Categories

Questions about Author

What does Author do?

Write a new doc in the right place with the right name. An agent skill from hashgraph-online/awesome-codex-plugins. Author is an agent skill from hashgraph-online/awesome-codex-plugins. Write a new doc in the right place with the right name.

When should I use Author?

Author fits situations like: asked to write a doc; where should this doc go; document this decision; new feature plan.

How do I install Author in Claude Code?

Run `npx skills add hashgraph-online/awesome-codex-plugins --skill author -a claude-code`. Or copy the skill folder (plugins/MedAdemBHA/docflow/skills/author in hashgraph-online/awesome-codex-plugins) into .claude/skills/author in your project. Claude Code loads it when a task matches its description.

How do I install Author in Codex?

Run `npx skills add hashgraph-online/awesome-codex-plugins --skill author -a codex`. Or copy the skill folder (plugins/MedAdemBHA/docflow/skills/author in hashgraph-online/awesome-codex-plugins) into .agents/skills/author in your project. Codex loads it when a task matches its description.

Can I use Author in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hashgraph-online/awesome-codex-plugins --skill author -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/author, .gemini/skills/author, .github/skills/author and .opencode/skills/author in your project.

What does Author need to run?

Going by SKILL.md and its folder, Author needs the command-line tools its instructions call (bash).

Does Author access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Author safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Author use?

Author is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Author use?

About 1.7k tokens (SKILL.md is roughly 6.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Author?

Skills that share tags, products or a category with Author: PR Design Doc (OpenHands/OpenHands, 90k stars), Cto Advisor (Ibrahim-3d/orchestrator-supaconductor, 380 stars), Improve Codebase Architecture (ywwynm/EverythingDone, 144 stars) and Domain Modeling (brim-borium/spotify_sdk, 166 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Author?

hashgraph-online (a GitHub organization) maintains it in hashgraph-online/awesome-codex-plugins, which has 1,242 GitHub stars. The repository holds 686 skills in this directory. The repository was last updated on October 8, 2026.

Source: hashgraph-online/awesome-codex-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.