What is skillshare-update-docs?

A documentation workflow for updating Skillshare’s website documentation after code changes.

Use it to document new commands or flags, fix stale documentation, and update affected pages in the website/docs directory.

It helps keep command descriptions, flags, reference pages, and concept guides aligned with the actual source code.

skillshare-update-docs — Skill by runkids

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/runkids/skillshare/skillshare-update-docs

Any agent

npx skills add runkids/skillshare --skill skillshare-update-docs

Clone the repo

git clone --depth 1 https://github.com/runkids/skillshare

Made for: Claude Code, Codex.

Per session 123 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,243 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00123	$0.01243
Opus 5	$0.00062	$0.00622
Sonnet 5	$0.00025	$0.00249
Haiku 4.5	$0.00012	$0.00124

Measured 3d ago against content hash 99376df55ede, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

skillshare-update-docs 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 3d 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.

.skillshare/skills/skillshare-update-docs/SKILL.md · 142 lines

How it starts

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

Sync website documentation with recent code changes. $ARGUMENTS specifies scope: a command name (e.g., install), commit range, or omit to auto-detect from git diff HEAD~1.

Scope: This skill only updates website/docs/. It does NOT write Go code (use implement-feature) or CHANGELOG (use changelog).

Workflow

Step 1: Detect Changes

# Auto-detect recently changed code
git diff HEAD~1 --stat -- cmd/skillshare/ internal/

# Also check for structural changes that affect concept/reference docs
git diff HEAD~1 --stat -- internal/config/targets.yaml internal/audit/rules.yaml

Map changed files to affected documentation using this guide:

Command docs (website/docs/reference/commands/):

cmd/skillshare/<cmd>.go → website/docs/reference/commands/<cmd>.md
Flag changes, new subcommands, output format changes

Concept docs (website/docs/understand/):

internal/audit/ → understand/audit-engine.md
internal/sync/ → understand/sync-modes.md, understand/source-and-targets.md
internal/install/tracked.go → understand/tracked-repositories.md
internal/config/ → understand/declarative-manifest.md
.skillshare/ project config changes → understand/project-skills.md
skills/skillshare/SKILL.md format → understand/skill-format.md

Reference docs (website/docs/reference/):

internal/config/targets.yaml → reference/targets/
internal/audit/rules.yaml → reference/commands/audit-rules.md
reference/appendix/ for CLI quick-reference tables

How-to guides (website/docs/how-to/):

New workflow patterns → how-to/daily-tasks/, how-to/advanced/, how-to/recipes/
Sharing/org features → how-to/sharing/

Troubleshooting (website/docs/troubleshooting/):

New error messages → troubleshooting/common-errors.md
FAQ additions → troubleshooting/faq.md

Getting started (website/docs/getting-started/):

Breaking changes to init/install flow → getting-started/first-sync.md
Quick reference updates → getting-started/quick-reference.md

Read the full file on GitHub · 142 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.

3d ago First seen · 142 lines · 123 tokens per session scan A 99376df55ede

Subscribe to this mod's changes

skillshare-update-docs is a skill published in the GitHub repository runkids/skillshare (2,607 stars, last pushed 6d ago), licensed MIT. It adds 123 tokens to every session and 1,243 once invoked, about $0.0006 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-30.

Writing and docs ai cli codex cursor skills team-management

git-workflow-and-versioning

Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…

addyosmani/agent-skills · 74 tokens

spec-driven-development

Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea. Use when a single requirement spans several independently testable capabilities and needs decomposing into a…

addyosmani/agent-skills · 67 tokens

idea-refine

Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on "ideate", "refine this idea", or…

addyosmani/agent-skills · 75 tokens

skillshare-update-docs