Article Audit
This skill should be used when the user asks to "检查这篇文章是否齐全", "审计这篇文章", "article audit", "publish ready", or wants to verify that one article's brief, draft, cover, and inline images exist and follow the artifact-family naming convention. It audits a single article slug across the package output directories.
Install
$ agentstack add skill-giantclam-auto-viral-article-writer-article-audit ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-giantclam-auto-viral-article-writer-article-audit) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Article Audit
Use this skill to inspect whether one article's artifact family is complete, coherent, and named consistently.
Use This For
- checking whether an article is publish-ready
- verifying that brief, draft, cover, and inline images belong to the same slug family
- identifying missing or misnamed artifacts for a specific article
Do Not Use This For
- repository-wide documentation sync
- generating content from scratch
- replacing normal article writing or research steps
Inputs
- article slug
- optional article path
- optional expectation about whether inline images should exist
Outputs
- artifact presence summary
- naming consistency summary
- missing-file warnings
- publish-readiness decision for the article family
Workflow
- Determine the target slug.
- Check for the expected brief file.
- Check for the expected draft file.
- Check for the expected cover image.
- Check for inline image files if the article should already be illustrated.
- Compare naming consistency across all discovered files.
- Report gaps, mismatches, and overall readiness.
If a naming mismatch exists, prefer the slug established by the earliest durable artifact, usually the brief file.
Expected Artifact Family
output/briefs/{slug}-brief.yamloutput/wechat/{slug}-article.mdoutput/images/wechat/{slug}-cover-final.pngoutput/images/wechat/{slug}-01.png,output/images/wechat/{slug}-02.png,output/images/wechat/{slug}-03.png
References
references/audit-checklist.md- what to verify for one article familyreferences/status-levels.md- how to classify article readiness../../docs/overview/article-artifact-family.md- canonical artifact-family naming convention../../docs/overview/slug-rules.md- slug generation and stability rules
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: GiantClam
- Source: GiantClam/auto-viral-article-writer
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.