content-qa
Skill0 starsChanged 48 days agoMITView on GitHub
Review a draft for evidence, privacy, tone and release risks without silently rewriting disputed statements.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- casoon/ai-agent-configtheir own version, first seen Sep 27, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- casoon/ai-agent-config★ 1same 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 repository9 other files it gives its agents.
- eval-engineering-liteSkill
- evidence-contentSkill
- failure-analyzerSkill
- faq-builderSkill
- meeting-to-actionsSkill
- project-handoffSkill
- requirement-clarifierSkill
- research-synthesizerSkill
- workflow-plannerSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Use before publishing a claim-heavy article, landing page, FAQ or generated answer.
- Distinctive: line 28
Check personally identifying information, confidential material, links and channel rules.
- Very specific: line 34
If sources are incomplete, report UNKNOWN_SUPPORT rather than approving.
- Very specific: line 42
Run python3 tests/validate.py from the repository root to check this skill's contract and example provenance.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Content QA
Purpose
Produce an actionable release gate for draft content.
When to Use
Use before publishing a claim-heavy article, landing page, FAQ or generated answer.
Inputs
draft, source_docs[], style_rules[], forbidden_claims[], optional audience.
Outputs
findings: [{severity,excerpt,reason,source_id,fix}], release_state, required_review[].
Workflow
- Extract all quantitative, comparative, customer and compliance claims.
- Trace each claim to the provided source and flag mismatches or missing citations.
- Check personally identifying information, confidential material, links and channel rules.
- Score findings as critical, major or minor with exact excerpt and proposed fix.
- Set
release_state=BLOCKEDon unresolved critical findings; do not publish.
Failure Handling
If sources are incomplete, report UNKNOWN_SUPPORT rather than approving. Disputed language is flagged, never silently softened into apparent approval.
Example
synthetic_unverified: “10,000 customers” without source triggers a critical finding and blocked release.
Tests
Run python3 tests/validate.py from the repository root to check this skill's contract and example provenance. This is a structural test, not model-quality evidence.
Limitations
This is a review aid, not legal clearance, source authenticity verification or human editorial approval.
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.