audit-content
Skill24 starsChanged 19 days agoMITView on GitHub
Audit academy materials for outdated references, deprecated patterns, and stale content
1 other project uses a version of this.
Adopted by
Most recently taken up by
- onvoyage-ai/gtm-engineer-skillstheir own version, first seen Mar 30, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- onvoyage-ai/gtm-engineer-skills★ 1.3ksame name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository23 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
If the user specifies a scope (e.g., /audit-content embeddings or /audit-content module 3), audit only that area.
- Very specific: line 35
Use WebSearch to check the MTEB leaderboard and model provider documentation for current recommendations.
- Very specific: line 50
Use WebSearch to check changelogs and migration guides.
- Distinctive: line 61
Check if major new RAG techniques have emerged that aren't covered
- Very specific: line 63
Use WebSearch to check paper citation counts and newer follow-up work.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Audit Content: Keep the Academy Current
Purpose: Systematically check all academy materials for outdated information — deprecated models, changed APIs, superseded techniques, and stale references. Produces an actionable update report.
Step 1: Determine Audit Scope
If the user specifies a scope (e.g., /audit-content embeddings or /audit-content module 3), audit only that area. Otherwise, run a full audit across all content.
Full audit covers:
- Curriculum modules (
.claude/docs/curriculum/) - Agent definitions (
.claude/agents/) - Reference docs (
.claude/docs/reference/) - Code rules (
.claude/rules/) - Sample data (
data/raw/) - Templates (
.claude/docs/templates/)
Step 2: Check Model References
Scan all content files for embedding and LLM model references. Verify each against current state:
| Model Reference | What to Check |
text-embedding-3-small | Still recommended? Check OpenAI docs and MTEB leaderboard |
all-MiniLM-L6-v2 | Still a good free default? Check Sentence Transformers releases |
nomic-embed-text | Still maintained and competitive? |
bge-base-en-v1.5 | Check if newer BGE versions exist |
| Claude model IDs | Verify against current Anthropic model IDs |
| GPT model IDs | Verify against current OpenAI model IDs |
Use WebSearch to check the MTEB leaderboard and model provider documentation for current recommendations.
Step 3: Check Library and Framework References
Scan for library references and verify versions and API patterns:
| Library | What to Check |
langchain | Import patterns — should use langchain-core, langchain-community, or langgraph |
chromadb | API compatibility — check for breaking changes |
ragas | Current version and metric names |
sentence-transformers | Current version and API |
llama-index | Package rename or API changes |
pydantic | v1 vs v2 patterns |
Use WebSearch to check changelogs and migration guides.
Step 4: Check Paper and Technique References
Scan for research paper citations. Flag:
- Papers described as "recent" or "new" that are 2+ years old
- Techniques that have been superseded by newer approaches
- Benchmarks that have been replaced
Key papers to verify:
- Self-RAG, CRAG, HyDE, ColBERT, RAPTOR, GraphRAG
- Check if major new RAG techniques have emerged that aren't covered
Use WebSearch to check paper citation counts and newer follow-up work.
Step 5: Check for Deprecated Patterns
Scan code examples and rules for deprecated patterns:
- Old-style LangChain imports (
from langchain importinstead offrom langchain_core) - Deprecated API parameters or function signatures
- Outdated best practices
Step 6: Check Content Age
For each content file, check the git log to find when it was last updated. Flag files older than 90 days. Categorize by staleness risk:
| Risk Level | Review Cycle | Content Types |
| High | Monthly | Model recommendations, library versions, MTEB references |
| Medium | Quarterly | Framework patterns, API examples, production tooling |
| Low | Semi-annually | Foundational concepts, algorithms, evaluation theory |
Step 7: Generate Audit Report
Produce a structured report:
# Content Audit Report — [Date]
## Summary
- Files audited: N
- Issues found: N (X critical, Y warnings, Z info)
## Critical (requires immediate update)
- [ ] Issue description — file path — suggested fix
## Warnings (review within 30 days)
- [ ] Issue description — file path — suggested fix
## Informational (consider updating)
- [ ] Issue description — file path — suggested fix
## Verified Current
- List of items confirmed as up-to-date
## Recommendations
- Prioritized list of updates to makeSave the report to progress/audit-report-[date].md if the user wants to track it.
Suggest 2-3 relevant next steps:
/lesson— to update specific curriculum content based on findings/explain— to deep-dive into any new techniques discovered during the audit/roadmap— to see if the learning path needs adjustment based on ecosystem changes
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

