Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
actionbook avatar

Core Fix Skill Docs

  • 742 installs
  • 1.4k repo stars
  • Updated May 24, 2026
  • actionbook/rust-skills

core-fix-skill-docs is a Rust skill maintenance agent skill that scans generated crate SKILL.md files for missing references/ markdown, fetches docs.rs content, or removes invalid links for developers curating actionbook

About

core-fix-skill-docs version 2.1.0 from actionbook/rust-skills is an internal maintenance skill invoked via /fix-skill-docs to keep Rust crate skills accurate. It scans ~/.claude/skills/{crate} directories, parses Documentation sections for ./references/*.md links, reports OK versus MISSING files, and either launches background agents or uses inline agent-browser CLI and WebFetch against docs.rs to backfill missing modules. Flags include --check-only for reporting only and --remove-invalid to strip references that cannot be fetched. The skill disables automatic model invocation and expects explicit /fix-skill-docs calls. Reach for core-fix-skill-docs when dynamic Rust skills drift from docs.rs after crate updates and reference trees contain broken or absent markdown files.

  • Rust skill doc repair
  • Consistency across skill files
  • Authoring-quality documentation
  • Agent instruction accuracy
  • Maintenance-focused workflow

Core Fix Skill Docs by the numbers

  • 742 all-time installs (skills.sh)
  • Ranked #321 of 1,879 Documentation skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/actionbook/rust-skills --skill core-fix-skill-docs

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs742
repo stars1.4k
Last updatedMay 24, 2026
Repositoryactionbook/rust-skills

How do you fix broken references in Rust agent skills?

Repair, normalize, and improve Rust-focused agent skill documentation so instructions stay accurate, consistent, and usable during skill maintenance and authoring.

Who is it for?

Maintainers of generated Rust crate agent skills who need automated docs.rs backfills and reference integrity checks across ~/.claude/skills libraries.

Skip if: Greenfield skill authoring, non-Rust skills, or casual users without an installed rust-skills tree who never invoke /fix-skill-docs explicitly.

When should I use this skill?

The user explicitly runs /fix-skill-docs or asks to check and repair missing reference files in Rust crate SKILL.md documentation.

What you get

Updated references/*.md files fetched from docs.rs, status reports per crate, and edited SKILL.md files with invalid links removed when requested.

  • references/*.md backfills
  • per-crate MISSING/OK reports
  • edited SKILL.md files

By the numbers

  • Skill metadata version 2.1.0 last updated 2025-01-27
  • Supports --check-only and --remove-invalid maintenance flags
  • Targets ~/.claude/skills crate directories with ./references/*.md links

Files

SKILL.mdMarkdownGitHub ↗

Fix Skill Documentation

Version: 2.1.0 | Last Updated: 2025-01-27

Check and fix missing reference files in dynamic skills.

Usage

/fix-skill-docs [crate_name] [--check-only] [--remove-invalid]

Arguments:

  • crate_name: Specific crate to check (optional, defaults to all)
  • --check-only: Only report issues, don't fix
  • --remove-invalid: Remove invalid references instead of creating files

Execution Mode Detection

CRITICAL: Check if agent infrastructure is available.

This skill can run in two modes:

  • Agent Mode: Uses background agents for documentation fetching
  • Inline Mode: Executes directly using agent-browser CLI or WebFetch

---

Agent Mode (Plugin Install)

When agent infrastructure is available, use background agents for fetching:

Instructions

1. Scan Skills Directory
# If crate_name provided
skill_dir=~/.claude/skills/{crate_name}

# Otherwise scan all
for dir in ~/.claude/skills/*/; do
    # Process each skill
done
2. Parse SKILL.md for References

Extract referenced files from Documentation section:

## Documentation
- `./references/file1.md` - Description
3. Check File Existence
if [ ! -f "{skill_dir}/references/{filename}" ]; then
    echo "MISSING: {filename}"
fi
4. Report Status
=== {crate_name} ===
SKILL.md: OK
references/:
  - sync.md: OK
  - runtime.md: MISSING

Action needed: 1 file missing
5. Fix Missing Files (Agent Mode)

Launch background agent to fetch documentation:

Task(
  subagent_type: "general-purpose",
  run_in_background: true,
  prompt: "Fetch documentation for {crate_name}/{module} from docs.rs.
           Use agent-browser CLI to navigate to https://docs.rs/{crate_name}/latest/{crate_name}/{module}/
           Extract the main documentation and save to ~/.claude/skills/{crate_name}/references/{module}.md"
)

---

Inline Mode (Skills-only Install)

When agent infrastructure is NOT available, execute directly:

Step 1: Scan Skills Directory

# List all skills
ls ~/.claude/skills/

# Or check specific skill
ls ~/.claude/skills/{crate_name}/

Step 2: Parse SKILL.md for References

Read SKILL.md and extract all ./references/*.md patterns:

# Using Read tool
Read("~/.claude/skills/{crate_name}/SKILL.md")

# Look for lines like:
# - `./references/sync.md` - Sync primitives
# - `./references/runtime.md` - Runtime configuration

Step 3: Check File Existence

# Check each referenced file
for ref in references; do
  if [ ! -f "~/.claude/skills/{crate_name}/references/${ref}.md" ]; then
    echo "MISSING: ${ref}.md"
  fi
done

Step 4: Report Status

Output format:

=== {crate_name} ===
SKILL.md: OK
references/:
  - sync.md: OK
  - runtime.md: MISSING

Action needed: 1 file missing

Step 5: Fix Missing Files (Inline)

For each missing file:

Using agent-browser CLI:

agent-browser open "https://docs.rs/{crate_name}/latest/{crate_name}/{module}/"
agent-browser get text ".docblock"
# Save output to ~/.claude/skills/{crate_name}/references/{module}.md
agent-browser close

Using WebFetch fallback:

WebFetch("https://docs.rs/{crate_name}/latest/{crate_name}/{module}/",
         "Extract the main documentation content for this module")

Then write the content:

Write("~/.claude/skills/{crate_name}/references/{module}.md", <fetched_content>)

Step 6: Update SKILL.md (if --remove-invalid)

If --remove-invalid flag is set and file cannot be fetched:

# Read current SKILL.md
Read("~/.claude/skills/{crate_name}/SKILL.md")

# Remove the invalid reference line
Edit("~/.claude/skills/{crate_name}/SKILL.md",
     old_string="- `./references/{invalid_file}.md` - Description",
     new_string="")

---

Tool Priority

1. agent-browser CLI - Primary tool for fetching documentation 2. WebFetch - Fallback if agent-browser unavailable 3. Edit SKILL.md - For removing invalid references (--remove-invalid only)

---

Examples

Check All Skills (--check-only)

/fix-skill-docs --check-only

# Output:
=== tokio ===
SKILL.md: OK
references/:
  - sync.md: OK
  - runtime.md: MISSING
  - task.md: OK

=== serde ===
SKILL.md: OK
references/:
  - derive.md: OK

Summary: 1 file missing in 1 skill

Fix Specific Crate

/fix-skill-docs tokio

# Fetches missing runtime.md from docs.rs
# Reports success

Remove Invalid References

/fix-skill-docs tokio --remove-invalid

# If runtime.md cannot be fetched:
# Removes reference from SKILL.md instead

---

Error Handling

ErrorCauseSolution
Agent not availableSkills-only installUse inline mode
Skills directory emptyNo skills installedRun /sync-crate-skills first
docs.rs unavailableNetwork issueRetry or use --remove-invalid
Permission deniedDirectory issueCheck ~/.claude/skills/ permissions
Invalid SKILL.md formatCorrupted skillRe-generate skill

Related skills

How it compares

Use core-fix-skill-docs to repair existing Rust skill reference trees; use crate sync generators when bootstrapping new skills from scratch.

FAQ

How do you invoke core-fix-skill-docs?

core-fix-skill-docs is invoked only through /fix-skill-docs with optional crate_name plus --check-only or --remove-invalid flags. The skill sets disable-model-invocation true so agents do not auto-run it during normal coding.

Where does core-fix-skill-docs look for skills?

core-fix-skill-docs scans ~/.claude/skills/{crate_name} or every subdirectory when no crate is specified. It parses SKILL.md Documentation sections for ./references/file.md paths and checks filesystem existence.

How does core-fix-skill-docs fetch missing docs?

core-fix-skill-docs prefers agent-browser CLI against docs.rs URLs such as https://docs.rs/{crate}/latest/{crate}/{module}/ and falls back to WebFetch when browser automation is unavailable, writing results into references/{module}.md.

Documentationdocsbackend

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.