.claude/skills/anthropic-docs-updater/SKILL.md
Automated documentation update mechanism for anthropic-expert skill. Five-step workflow from update detection through documentation fetching and processing to skill integration and validation. Use when updating Anthropic documentation, checking for new releases, fetching latest docs, keeping anthropic-expert current, or synchronizing with Anthropic product changes.
npx skillsauth add adaptationio/skrillz anthropic-docs-updaterInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
anthropic-docs-updater automatically keeps the anthropic-expert skill current by detecting, fetching, and integrating Anthropic documentation updates.
Purpose: Automated documentation maintenance for anthropic-expert
Update Workflow (5 steps):
Automation: 80% automated (manual review for breaking changes)
Update Sources:
Purpose: Detect new releases, documentation changes, feature announcements
Process:
Check GitHub Releases
python scripts/check-updates.py --github
Check Release Notes
python scripts/check-updates.py --docs
Check Claude Code Changelog
python scripts/check-updates.py --claude-code
Generate Update Report
python scripts/check-updates.py --all
Validation:
Outputs:
Time Estimate: 10-15 minutes (automated)
Example Output:
Anthropic Documentation Update Check
=====================================
Date: 2025-11-15
GitHub Releases:
✅ anthropic-sdk-python: v0.45.0 (current: v0.42.0) - UPDATE AVAILABLE
✅ claude-agent-sdk-python: v1.12.0 (current: v1.10.0) - UPDATE AVAILABLE
Release Notes (docs.claude.com):
✅ New feature: Batch API cost reduction increased to 60%
✅ New model: Claude Sonnet 4.6 announced
Claude Code Changelog:
- No new updates since last check
Recommendation: UPDATE AVAILABLE
- 2 SDK updates
- 2 API feature updates
- Proceed to Step 2 (Fetch Documentation)
Purpose: Download updated content from official sources
Process:
Fetch SDK Documentation
python scripts/fetch-docs.py --github-readmes
Fetch API Documentation
python scripts/fetch-docs.py --api-docs
Fetch Claude Code Documentation
python scripts/fetch-docs.py --claude-code-docs
Verify Downloads
Validation:
Outputs:
Time Estimate: 15-30 minutes (automated, depends on amount of content)
Purpose: Convert fetched content to skill reference format
Process:
Parse Fetched Documentation
python scripts/process-docs.py --input temp/ --output processed/
Convert to Reference Format
Merge with Existing Content
Validate Processed Content
Validation:
Outputs:
Time Estimate: 20-40 minutes (automated with manual review of diff)
Purpose: Integrate new content into anthropic-expert skill safely
Process:
Backup Current Skill
python scripts/update-skill.py --backup
Integrate New Content
python scripts/update-skill.py --integrate processed/
Update Version
Review Changes
Validation:
Outputs:
Time Estimate: 15-30 minutes (automated, quick review)
Purpose: Ensure updates maintain quality and don't introduce regressions
Process:
Run Structure Validation
python ../../review-multi/scripts/validate-structure.py ../anthropic-expert
Test Search Functionality
python ../anthropic-expert/scripts/search-docs.py "test query"
Manual Spot Check
Validation Decision
Rollback if Failed (if validation fails)
python scripts/update-skill.py --rollback
Validation:
Outputs:
Time Estimate: 20-30 minutes
If Successful:
If Failed:
Next Check: Weekly or when Anthropic announces updates
Practice: Weekly automated check for updates
Implementation: Cron job or scheduled task
# Weekly check (Mondays at 9am)
0 9 * * 1 cd /path/to/skills && python anthropic-docs-updater/scripts/check-updates.py --all
Practice: For major version updates, review changes before applying
Why: Breaking changes may require manual updates to examples
Practice: Always backup (Step 4 does this automatically)
Why: Can rollback if updates cause issues
Practice: Always run Step 5 (validation)
Why: Ensures updates don't break skill quality
Practice: Maintain detailed changelog
Why: Understand what changed when, aids troubleshooting
| Step | Focus | Time | Automation | Output | |------|-------|------|------------|--------| | 1. Check Updates | Detect changes | 10-15m | 100% | update-report.txt | | 2. Fetch Docs | Download content | 15-30m | 100% | temp/docs/ | | 3. Process Content | Convert format | 20-40m | 90% | processed/docs/ | | 4. Update Skill | Integrate content | 15-30m | 95% | Updated skill | | 5. Validate | Ensure quality | 20-30m | 70% | Validation report |
Total Time: 1.5-2.5 hours (mostly automated)
| Source | What It Tracks | Check Method | |--------|----------------|--------------| | GitHub Releases | SDK versions | GitHub API | | Release Notes | API features | Web scraping | | Claude Code Changelog | CLI updates | Web scraping | | Anthropic News | Model announcements | Manual/RSS |
# Check for updates
python scripts/check-updates.py --all
# Fetch new documentation
python scripts/fetch-docs.py --all
# Process fetched docs
python scripts/process-docs.py --input temp/ --output processed/
# Apply updates
python scripts/update-skill.py --integrate processed/
# Validate
python scripts/update-skill.py --validate
# Rollback if needed
python scripts/update-skill.py --rollback
Recommended: Weekly checks, monthly comprehensive updates
Cron Example (check weekly, update monthly):
# Check for updates every Monday
0 9 * * 1 python check-updates.py --all > /tmp/anthropic-updates.log
# Full update first Monday of month
0 10 1-7 * 1 bash run-full-update.sh
anthropic-docs-updater ensures anthropic-expert stays current with the latest Anthropic products, features, and documentation through automated update detection, fetching, processing, and integration.
development
Setup secure web-based terminal access to WSL2 from mobile/tablet via ttyd + ngrok/Cloudflare/Tailscale. One-command install, start, stop, status. Use when you need remote terminal access, web terminal, browser-based shell, or mobile access to WSL2 environment.
development
Complete development workflows where Claude writes the code while Gemini and Codex provide research, planning, reviews, and different perspectives. Claude remains the main developer. Use for complex projects requiring expert planning and multi-perspective reviews.
development
Systematic progress tracking for skill development. Manages task states (pending/in_progress/completed), updates in real-time, reports progress, identifies blockers, and maintains momentum. Use when tracking skill development, coordinating work, or reporting progress.
testing
Comprehensive testing workflow orchestrating functional testing, example validation, integration testing, and usability assessment. Sequential workflow for complete skill testing from examples through scenarios to integration validation. Use when conducting thorough testing, pre-deployment validation, ensuring skill functionality, or comprehensive quality checks.