Agent skill

Authoring Roles

by oocx in oocx/tfplan2md

How to write and validate a role definition - required structure, the tier system, and the line budget.

MITAuto-check passedDevelopment

Install Authoring Roles

skills CLI
$ npx skills add oocx/tfplan2md --skill authoring-roles -a claude-code

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

GitHub CLI
$ gh skill install oocx/tfplan2md authoring-roles --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/oocx/tfplan2md.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/authoring-roles .claude/skills/authoring-roles && 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
authoring-roles
GitHub stars
174
Token cost
~686 tokens
SKILL.md length
254 words
Files
1
Skills in repo
28
Repo updated
First seen
Licence
MIT

At a glance

How to write and validate a role definition - required structure, the tier system, and the line budget.

  • Development work in your project
  • SKILL.md covers Frontmatter, Structure, The line budget and Choosing a tier, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Authoring Roles is an agent skill from oocx/tfplan2md. How to write and validate a role definition - required structure, the tier system, and the line budget.

Its SKILL.md is about 690 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. The repository describes itself as: Convert terraform plans (json) into human readable markdown for easier review of changes in pull requests. The licence is MIT.

When your agent uses it

  • Development work in your project

Example prompts

  • “/authoring-roles”

What it can do on your machine

Read from SKILL.md and the folder at commit 88d5240. 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

    No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml, markdown and 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

Authoring Roles loads about 686 tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 254 words of instructions outside code blocks.

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

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 oocx/tfplan2md at commit 88d5240, republished under its MIT licence (© oocx). 254 words, ~686 tokens.

Download SKILL.mdSave it as .claude/skills/authoring-roles/SKILL.md (or your agent's skills folder).
name
authoring-roles
description
How to write and validate a role definition - required structure, the tier system, and the line budget.

Authoring Roles

Role definitions live in .agents/roles/*.md and are generated into .claude/agents/ by scripts/sync-agent-config.sh. Edit the canonical files; never the generated ones.

Frontmatter

yaml
---
name: Code Reviewer          # display name, used in work-protocol entries
description: ...             # <= 100 chars, one line
tier: deep                   # deep | standard | cheap
---

That is the whole schema. A role must not declare:

  • model — the tier resolves to a model through .agents/tiers.json. Naming a model in a role file puts the mapping in thirteen places instead of one, and the generator rejects it.
  • tools — roles run with the harness default toolset. Per-role tool lists were the single largest source of drift in the previous corpus, because a tool ID renamed upstream broke a role silently.
  • handoffs or target — sequencing lives in state.json and .agents/workflow.json.

Structure

markdown
# Role Name

Read [AGENTS.md](../../AGENTS.md) and the `agent-runtime` skill first.

## Goal            <!-- one sentence: the outcome, not the process -->
## Boundaries      <!-- Always / Never; Ask first only where it is real -->
## Inputs          <!-- what to read, and in what order -->
## Steps           <!-- numbered, with exact commands -->
## Output          <!-- artifact paths and their shape -->
## Definition of Done

scripts/validate-agents.py enforces ## Goal, ## Boundaries, ## Definition of Done, and a reference to AGENTS.md.

The line budget

160 lines, enforced. A role that outgrows it is doing more than one job, or is repeating something that belongs in AGENTS.md (project-wide rules) or the agent-runtime skill (how roles operate). The previous corpus averaged 378 lines per agent, and almost all of the excess was duplicated boilerplate.

Write only what is true of this role and no other.

Choosing a tier

TierUse for
deepWork whose errors propagate — requirements, architecture, review, the workflow itself
standardWork constrained by an approved spec, where mistakes surface in review or CI
cheapTranscription and mechanical work against a fixed input

Cost is a consideration, but the deciding question is what an error costs to unwind. A role escalates one tier automatically on rework, so the tier is the starting point, not a ceiling.

Before committing

bash
scripts/sync-agent-config.sh     # regenerate .claude/
scripts/validate-agents.py       # structure, tier, budget, links, adapter drift

© oocx, MIT. 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 .agents/skills/authoring-roles of oocx/tfplan2md.

Open the folder on GitHubat commit 88d5240

Compare with similar skills

Authoring Roles 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.

Authoring Roles compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Authoring Roles this skilloocx/tfplan2md174—~686Automated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Design Rationale Investigatorcursor/plugins10k9 repos~2.6kAutomated safety check: PassNone
Simple Englishmoeru-ai/airi50k2 repos~4.6kAutomated safety check: PassMIT
Mole CLI Release Flowtw93/Mole70k—~2.6kAutomated safety check: PassGPL-3.0
Babysit PR To Pass CIsgl-project/sglang37k2 repos~3kAutomated safety check: PassApache-2.0

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Official

    Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.

    10k GitHub starsUsed in 9 repos~2.6k tokens
    DevelopmentAuto-check passed
  • Simple English

    moeru-ai/airi

    Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop.

    50k GitHub starsUsed in 2 repos~4.6k tokens
    DevelopmentAuto-check passed
  • Runbook for assessing and executing a Mole CLI release: distribution channels, pre-flight checks, capital-V tags, build artifacts and the handoff to curated release notes.

    70k GitHub stars~2.6k tokensUpdated today
    DevelopmentAuto-check passed
  • Babysit PR To Pass CI

    sgl-project/sglang

    Start and persistently pursue a goal to babysit an SGLang pull request until selected GitHub Actions workflows pass on the latest PR head.

    37k GitHub starsUsed in 2 repos~3k tokens
    DevelopmentAuto-check passed
  • Load Ansible project development guidelines, testing conventions, PR review processes, and code structure reference into context

    71k GitHub stars~427 tokensUpdated yesterday
    DevelopmentAuto-check passed

More from oocx/tfplan2md

All 28 skills in this repo
  • Create Agent Skill

    oocx/tfplan2md

    Create a new Agent Skill following project standards and templates.

    174 GitHub stars~1.5k tokensUpdated 2 days ago
    Auto-check passed
  • Detect and analyze edge crossings and overlaps in SVG workflow diagrams using geometric intersection algorithms and visual analysis.

    174 GitHub stars~4.3k tokensUpdated 2 days ago
    Auto-check passed
  • Generate PNG screenshots for release notes using the repository's HtmlRenderer and ScreenshotGenerator tools.

    174 GitHub stars~3.7k tokensUpdated 2 days ago
    Auto-check passed
  • Git Rebase Main

    oocx/tfplan2md

    Safely rebase the current feature branch on top of the latest origin/main.

    174 GitHub stars~456 tokensUpdated 2 days ago
    Auto-check passed
  • Next Issue Number

    oocx/tfplan2md

    Determine the next available issue number across all change types (feature, fix, workflow, website) by checking both local docs and remote branches, then reserve it by pushing an empty branch.

    174 GitHub stars~1.5k tokensUpdated 2 days ago
    Auto-check passed
  • Run Uat

    oocx/tfplan2md

    Run User Acceptance Testing by creating a PR with rendered markdown on GitHub or Azure DevOps.

    174 GitHub stars~1.2k tokensUpdated 2 days ago
    Auto-check passed

Questions about Authoring Roles

What does Authoring Roles do?

How to write and validate a role definition - required structure, the tier system, and the line budget. Authoring Roles is an agent skill from oocx/tfplan2md. How to write and validate a role definition - required structure, the tier system, and the line budget.

When should I use Authoring Roles?

Authoring Roles fits situations like: development work in your project.

How do I install Authoring Roles in Claude Code?

Run `npx skills add oocx/tfplan2md --skill authoring-roles -a claude-code`. Or copy the skill folder (.agents/skills/authoring-roles in oocx/tfplan2md) into .claude/skills/authoring-roles in your project. Claude Code loads it when a task matches its description.

How do I install Authoring Roles in Codex?

Run `npx skills add oocx/tfplan2md --skill authoring-roles -a codex`. Or copy the skill folder (.agents/skills/authoring-roles in oocx/tfplan2md) into .agents/skills/authoring-roles in your project. Codex loads it when a task matches its description.

Can I use Authoring Roles 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 oocx/tfplan2md --skill authoring-roles -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/authoring-roles, .gemini/skills/authoring-roles, .github/skills/authoring-roles and .opencode/skills/authoring-roles in your project.

What does Authoring Roles need to run?

SKILL.md names no scripts, command-line tools or credentials: Authoring Roles is instructions for the agent only.

Does Authoring Roles 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 Authoring Roles 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 Authoring Roles use?

Authoring Roles is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Authoring Roles use?

About 686 tokens (SKILL.md is roughly 2.7k 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 Authoring Roles?

Skills that share tags, products or a category with Authoring Roles: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Code Design Rationale Investigator (cursor/plugins, 10k stars), Simple English (moeru-ai/airi, 50k stars) and Mole CLI Release Flow (tw93/Mole, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Authoring Roles?

oocx (a GitHub user) maintains it in oocx/tfplan2md, which has 174 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on October 7, 2026.

Source: oocx/tfplan2md on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.