taasim-doc-sync
Syncs technical documentation and READMEs with actual implementation to prevent knowledge drift.
Install
mkdir -p .claude/skills/taasim-doc-sync && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16597" && unzip -o skill.zip -d .claude/skills/taasim-doc-sync && rm skill.zipInstalls to .claude/skills/taasim-doc-sync
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use this skill when docs and implementation may have drift and you need to align README, documents, notebook descriptions, and actual code behavior.Key capabilities
- →Compare README API routes against api/main.py handlers and models
- →Compare README container/service list against docker-compose.yml
- →Validate docs claims against Flink and producer code behavior
- →Reconcile old week documents with documents/00_master_status.md
- →Compare connector documentation claims with config/kafka-connect/ files
- →Produce a drift matrix and priority-ordered doc update list
How it works
This skill identifies discrepancies between documentation and code by comparing README, API handlers, Docker Compose configurations, Flink/producer code, and connector documentation. It generates a drift matrix and a prioritized list of necessary documentation updates.
Inputs & outputs
When to use taasim-doc-sync
- →Auditing documentation for conflicting claims
- →Syncing README routes with API handlers
- →Verifying container list against docker-compose
- →Reconciling project status reports
About this skill
CasaMotion Doc Sync
Trigger
Use this skill when updating docs after code changes, preparing delivery evidence, or auditing conflicting technical claims.
Workflow
- Compare README API routes against api/main.py handlers and models.
- Compare README container/service list against docker-compose.yml.
- Validate docs claims against Flink and producer code behavior.
- Reconcile old week documents with documents/00_master_status.md.
- Compare connector documentation claims with config/kafka-connect/ current files.
- Produce a drift matrix and exact edits needed per document.
Required Comparisons
- README routes vs api/main.py
- README container list vs docker-compose.yml
- docs claims vs Flink/producers code
- old Week docs vs current master status
- connector docs vs config/kafka-connect/
Validation Commands
rg -n "/api/|GET|POST|PUT|DELETE" README.MD
rg -n "@app\\.(get|post|put|delete)\\(" api/main.py
docker compose config --services
rg -n "raw\\.|processed\\.|watermark|dedup|H3|zone" documents README.MD flink/jobs producers
rg -n "Week|Task|DONE|Upcoming|Status" documents/00_master_status.md documents
dir config/kafka-connect
rg -n "connector|kafka-connect|S3 Sink|DEPRECATED" README.MD documents config/kafka-connect
Output Contract
Return:
- Drift matrix: claim, source_doc, source_code, status(match/mismatch), fix.
- Priority-ordered doc update list.
- Any unresolved ambiguity requiring maintainer decision.
When not to use it
- →When documentation and implementation are already known to be in sync
- →When the task is not related to identifying or resolving documentation drift
- →When the task does not involve comparing specific code artifacts with documentation
Limitations
- →The skill is specific to the CasaMotion project's documentation and code structure
- →The skill's output requires interpretation for unresolved ambiguities
How it compares
This skill provides a structured workflow for identifying and prioritizing documentation drift by comparing specific code artifacts with documentation, which is more systematic than a manual review.
Compared to similar skills
taasim-doc-sync side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| taasim-doc-sync (this skill) | 0 | 2mo | Review | Intermediate |
| mlops-collaboration | 1 | 6mo | No flags | Intermediate |
| add-provider-doc | 6 | 3mo | Review | Beginner |
| documentation-review | 11 | 5mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
mlops-collaboration
fmind
Guide to prepare MLOps projects for sharing, collaboration, and community engagement.
add-provider-doc
lobehub
Guide for adding new AI provider documentation. Use when adding documentation for a new AI provider (like OpenAI, Anthropic, etc.), including usage docs, environment variables, Docker config, and image resources. Triggers on provider documentation tasks.
documentation-review
stacklok
Reviews documentation for factual accuracy
docs-review
metabase
Review documentation changes for compliance with the Metabase writing style guide. Use when reviewing pull requests, files, or diffs containing documentation markdown files.
workthrough
bear2u
Automatically document all development work and code modifications in a structured workthrough format. Use this skill after completing any development task, bug fix, feature implementation, or code refactoring to create comprehensive documentation.
claude-md-improver
anthropics
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project memory optimization".