update-docs
Use when code, config, prompt, schema, or task changes require updating Markdown files directly under docs/, such as architecture, structure, config-sync…
Skill by transparent-pegasus
Chalk Labs
Need help deploying update-docs?
Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/transparent-pegasus-update-docs
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: documents, productivity, agent-building
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/update-docs
What's inside
- Skill name
update-docs- Description
- Use when code, config, prompt, schema, or task changes require updating Markdown files directly under docs/, such as architecture, structure, config-sync, theories, adopted-theories, or todo documents.
- License
- MIT
- Instructions
- 25 lines in SKILL.md · view on GitHub
Files (2)
- ROOT_DOCS.md
- SKILL.md
SKILL.md (first lines)
# Update Docs ## Overview Keep root-level Markdown docs under `docs/` aligned with the current codebase and config. Use `ROOT_DOCS.md` in this directory as the contract for what each root doc should contain. ## Scope - Edit only files matching `docs/*.md` - Do not edit files inside `docs/*/` - Leave generated or output directories alone, including planning directories, generated content directories, and other paths explicitly marked as outputs by the initialized repository. ## Workflow 1. Identify which root docs are affected by the change. 2. Check `ROOT_DOCS.md` to confirm each affected doc's role and boundaries. 3. Check the current source of truth in code, config, prompts, schemas, or git history. 4. Update only the sections that changed. 5. Keep terminology, tone, and structure consistent with the existing file. 6. Keep diffs minimal. Prefer surgical edits over rewrites. 7. If a doc conflicts with the source of truth, fix the doc.
From transparent-pegasus/herdrpowers, MIT.
More from transparent-pegasus/herdrpowers
- 0.639score
executing-plans
transparent-pegasus
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no herdr sibling…
SkillAFreshness: A★ 12Claude Code +9 - 0.639score
using-herdr-sibling-panes
transparent-pegasus
Use when inside herdr (HERDR_ENV=1), the current pane is acting as the orchestrator for the task, and idle sibling agent panes can take delegated work —…
SkillAFreshness: A★ 12Claude Code +9 - 0.633score
herdr
transparent-pegasus
Use when the user explicitly requests Herdr pane, tab, workspace, or agent operations from an existing Herdr session.
SkillAFreshness: A★ 12Claude Code +9 - 0.630score
orchestration
transparent-pegasus
Route every task received directly from the user through the pane that received it (the orchestrator) in herdr unless the user explicitly denies orchestration.
SkillAFreshness: A★ 12Claude Code +9 - 0.611score
brainstorming
transparent-pegasus
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior.
SkillAFreshness: A★ 12Claude Code +9 - 0.608score
requesting-code-review
transparent-pegasus
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
SkillAFreshness: A★ 12Claude Code +9 - 0.608score
systematic-debugging
transparent-pegasus
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
SkillAFreshness: A★ 12Claude Code +9 - 0.608score
writing-plans
transparent-pegasus
Use when you have a spec or requirements for a multi-step task, before touching code
SkillAFreshness: A★ 12Claude Code +9 - 0.604score
pane-driven-development
transparent-pegasus
Use when executing implementation plans with independent tasks by delegating each task to a fresh herdr sibling pane
SkillAFreshness: A★ 12Claude Code +9 - 0.569score
finishing-a-development-branch
transparent-pegasus
Use when implementation is complete, all tests pass, and the user needs to decide how to integrate the work - presents the integration candidates (merge…
SkillBFreshness: B★ 12Claude Code +9 - 0.519score
receiving-code-review
transparent-pegasus
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires…
SkillCFreshness: C★ 12Claude Code +9
Signals
- Stars
- 12
- Forks
- 0
- Open issues
- 1
- Last commit (this folder)
- Jul 25, 2026 (3 months ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from transparent-pegasus
- 0.639score
executing-plans
transparent-pegasus
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no herdr sibling…
SkillAFreshness: A★ 12Claude Code +9 - 0.639score
using-herdr-sibling-panes
transparent-pegasus
Use when inside herdr (HERDR_ENV=1), the current pane is acting as the orchestrator for the task, and idle sibling agent panes can take delegated work —…
SkillAFreshness: A★ 12Claude Code +9 - 0.633score
herdr
transparent-pegasus
Use when the user explicitly requests Herdr pane, tab, workspace, or agent operations from an existing Herdr session.
SkillAFreshness: A★ 12Claude Code +9 - 0.630score
orchestration
transparent-pegasus
Route every task received directly from the user through the pane that received it (the orchestrator) in herdr unless the user explicitly denies orchestration.
SkillAFreshness: A★ 12Claude Code +9 - 0.611score
brainstorming
transparent-pegasus
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior.
SkillAFreshness: A★ 12Claude Code +9 - 0.608score
requesting-code-review
transparent-pegasus
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
SkillAFreshness: A★ 12Claude Code +9
Done for you
Rather not set it up yourself?
Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.
See how we build AI agents →Read the case studies
Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.
- launches shipped
- 50+
- launches shipped
- media placements
- 500+
- media placements
- founders on every account
- 2
- founders on every account
Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block
Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.
Get update-docs running in your business
Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.
Cite this page
update-docs skill. Agent Mart. https://agentmart.dev/skills/transparent-pegasus-update-docs (last updated 2026-10-24)