narrate-project

narrate-project is a skill for Claude Code from RadOrigin-LLC/RAD-Claude-Skills. It costs 175 tokens per session (2,357 once invoked), scanned A, original, Apache-2.0.

A skill for writing a plain-English description of a software project from its files and documentation.

In plain words
What is it for?
Use it to prepare a project overview, onboarding explanation, or narrative for people who are not familiar with the repository.
Why use it?
It helps collaborators understand what a codebase does without reading the code, while checking that the description is supported by the project and does not make unsupported promises.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions CLAUDE.md; mentions AGENTS.md.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the rad-explain plugin — 5 skills shipped together

Good fit Use it to prepare a project overview, onboarding explanation, or narrative for people who are not familiar with the repository.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add RadOrigin-LLC/RAD-Claude-Skills
Claude Code
/plugin install rad-explain

Made for: Claude Code.

Or install rad-explain, the plugin that ships this one along with the rest of its 5 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for narrate-project

README.md
[![agentmods](https://agentmods.dev/badge/skills/radorigin-llc/rad-claude-skills/narrate-project/github.svg)](https://agentmods.dev/skills/radorigin-llc/rad-claude-skills/narrate-project)
Your own site
<a href="https://agentmods.dev/skills/radorigin-llc/rad-claude-skills/narrate-project"><img src="https://agentmods.dev/badge/skills/radorigin-llc/rad-claude-skills/narrate-project/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for narrate-project

Your own site · 80×15
<a href="https://agentmods.dev/skills/radorigin-llc/rad-claude-skills/narrate-project"><img src="https://agentmods.dev/badge/skills/radorigin-llc/rad-claude-skills/narrate-project.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 175 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,357 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00175 $0.02357
Opus 5 $0.00088 $0.01179
Sonnet 5 $0.00035 $0.00471
Haiku 4.5 $0.00017 $0.00236

Measured 11d ago against content hash 9abc0d7a012e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

narrate-project scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

archive/plugins/rad-explain/skills/narrate-project/SKILL.md · 215 lines

How it starts

The opening of the file, as written. The whole thing — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Narrate Project — Plain-English description from repo source

You are synthesizing a plain-language description of a project from whatever artifacts the repo actually has. The deliverable is prose for a human reader: someone who needs to understand what the project is, who it's for, and what it does, without reading the code.

This skill is the cross-project default in rad-explain. It works on any repo whether or not rad-planner is in use. It reads a docs/ directory if present (a PRD, plan, decision log) and falls back to README + manifest + source structure otherwise.

Foundational rules

Both rules are enforced by validators at the end of generation. If either fails, surface the findings to the user and offer to revise before writing.

  1. Grounded. Every substantive claim must trace to repo source. The check-grounding.py validator runs against the output before it's finalized.
  2. Not overpromising. No superlatives, marketing fluff, vague-quantity claims without enumeration, or sensational framing. The check-overpromise.py validator runs against the output.

If you find yourself wanting to write something that's NOT in the source, surface it to the user as a gap rather than inventing it.

Input — adaptive to what the repo has

Try these in order. Stop reading once you have enough material for the chosen audience.

Priority Source Why
1 docs/vision.md / docs/architecture.md / docs/planning/current.md / docs/status.md / docs/decisions/*.md (rad-planner canonical structure) Highest-signal — these were authored for synthesis use
2 README.md at repo root Almost always present; primary user-facing description
3 package.json description field, pyproject.toml description, similar manifests One-line product summary
4 AGENTS.md / CLAUDE.md Operating-manual content; secondary signal
5 CHANGELOG.md / docs/roadmap.md What's been built and what's next
6 Source structure: top-level directories, file names What the codebase is shaped to do
7 Source content: imports, exports, public APIs What the codebase actually exposes
8 tests/ or __tests__/ directories What's verified to work

Read the full file on GitHub · 215 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 215 lines · 175 tokens per session scan A 9abc0d7a012e

Subscribe to this mod's changes

narrate-project is a skill published in the GitHub repository RadOrigin-LLC/RAD-Claude-Skills (5 stars, last pushed 24d ago), licensed Apache-2.0. It adds 175 tokens to every session and 2,357 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

bug-reporting

Load this skill whenever you are filing, reviewing, or generating accessibility bug reports — whether from automated tool output, manual testing, user reports, or testing with disabled people. The purpose of this skill is to make accessibility findings easier to report accurately, connect them to real people and…

mgifford/accessibility-skills · 122 tokens

audio-video

Load this skill whenever the project contains audio or video content, media players, podcasts, video embeds, or any / elements. Under no circumstances publish audio or video without captions, transcripts, and audio descriptions where required. Absolutely always apply WCAG 1.2 criteria for time-based media.

mgifford/accessibility-skills · 65 tokens

charts-graphs

Load this skill whenever the project contains charts, graphs, data visualizations, infographics, or any visual representation of data (bar charts, line charts, pie charts, scatter plots, dashboards). Under no circumstances render a chart without a text alternative, data table, or summary. Prioritize conveying the same…

mgifford/accessibility-skills · 72 tokens

light-dark-mode

Load this skill whenever the project supports light/dark mode, colour theme switching, high-contrast mode, or responds to prefers-color-scheme. Under no circumstances hard-code colours that break in alternative themes. Absolutely always test colour contrast in both light and dark themes, and respect user OS-level…

mgifford/accessibility-skills · 69 tokens

maps

Load this skill whenever the project contains static or interactive maps, embedded map widgets (Google Maps, Leaflet, Mapbox, OpenStreetMap), or any geographic visualizations. Under no circumstances embed a map without a text-based alternative conveying the same information. Absolutely always ensure map controls are…

mgifford/accessibility-skills · 75 tokens

mermaid

Load this skill whenever the project uses Mermaid diagrams — flowcharts, sequence diagrams, class diagrams, Gantt charts, or any Mermaid-rendered visualization. Under no circumstances render a Mermaid diagram without an accessible title, description, and text-based alternative. Absolutely always add accTitle: and…

mgifford/accessibility-skills · 82 tokens