CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

creator-content-auditor

Use when the user asks to "review this influencer content" or "check if this post meets brand guidelines"; runs the typed STAR pre-publish gate, scores Trust and Appeal on the deliverable, folds in the creator Suitability read, computes the profile-weighted SQS, checks the disclosure/claim/brand-safety and fraud/fake-engagement vetoes, and writes constructive revision feedback. Not for drafting the brief — use brief-generator; not for partnership terms — use contract-helper. 达人内容审核/发布前质检

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

70%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a mature, operationally precise gate procedure with excellent workflow sequencing, explicit validation checkpoints, and fail-closed error handling, and it avoids teaching known concepts. Its weaknesses are repetition of the same policy statements across sections and a reference graph that mostly points outside the bundle, leaving a standalone reader with unresolvable paths. Tightening the duplicated passages and clarifying which references resolve in a standalone install would lift both weaker dimensions.

Suggestions

State the typed-header rule and the complete veto set once and reference them from the other section instead of repeating them nearly verbatim in 'Evidence and Scoring' and 'Creator Feedback'.

Distinguish bundle-local references from repository-root references in 'Runtime Reads' and 'Reference Materials' (e.g., mark which are only available in repo/plugin installs and point standalone installs to the bundled auditor-runtime.md equivalents), since five referenced paths do not exist in this bundle.

Inline or bundle the minimal run.json shape and the typed conversation header template so the scorer and report steps are executable without the non-bundled auditor-runbook.md.

DimensionReasoningScore

Conciseness

The body never explains concepts Claude already knows and is information-dense, but it is noticeably repetitive: the typed-conversation-header instruction appears twice (Evidence and Scoring, then again nearly verbatim in Creator Feedback), the complete veto set is stated twice in the same section, and the reference-only identity boundary is repeated across Skill Contract, Creator Feedback, and Persistence. It fits the 3 anchor ('mostly efficient but... could be tightened') rather than 2, since there is no padded or tutorial-style content.

3 / 5

Actionability

Guidance is mostly executable: exact scorer invocation ('python3 "$AARON_SKILLS_ROOT/scripts/rubric-score.py" score <run.json>'), environment resolution, typed item IDs (S1..S10, T1..T10, A1..A10, R1..R10), a persistence path pattern, and concrete worked examples with scores and verdicts. Minor gaps keep it below 5: the run.json shape, the 'typed conversation header' format, and the validation invocation details live in runbooks not present in this bundle, so a standalone reader cannot fully execute the workflow.

4 / 5

Workflow Clarity

The sequence is clear and ordered (runtime setup → declare typed context → collect evidence → score items → verify vetoes → run scorer → report → creator feedback → persistence) with an explicit 'Validation Checkpoints' checklist and genuine error-recovery feedback loops: a fail-closed 'score_state: NOT_SCORED' path when the scorer is unavailable, unknown-vs-N/A state discipline, revalidation after persistence, and traceable reruns for revised assets. This matches the 5 anchor (explicit validation steps, feedback loops, checklists).

5 / 5

Progressive Disclosure

The SKILL.md is a well-sectioned overview and its three local references (auditor-runtime.md, review-templates.md, quality-review-aids.md) exist and are substantive, but scored against the actual bundle most referenced paths are dangling: star-benchmark.md, auditor-runbook.md, scoring-semantics.md, runtime-invocation.md, and humanizer-slop.md are not in the bundle, and quality-review-aids.md itself chains to a further humanizer-slop.md/expert-panel.md (two levels deep). This fits the 3 anchor ('references present but not clearly signaled; content that should be separate is inline/organization could be better') rather than 4, since more than a minor share of navigation targets are unresolvable.

3 / 5

Total

15

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete multi-action capability statement, explicit verbatim trigger phrases in two languages, clear what/when coverage, and explicit disambiguation against sibling skills. Third-person voice is used throughout. Only minor synonym coverage is missing, keeping trigger term quality at 4 rather than 5.

DimensionReasoningScore

Specificity

The description lists multiple concrete, distinct actions — 'runs the typed STAR pre-publish gate, scores Trust and Appeal on the deliverable, folds in the creator Suitability read, computes the profile-weighted SQS, checks the disclosure/claim/brand-safety and fraud/fake-engagement vetoes, and writes constructive revision feedback' — covering the skill's full operation set comprehensively. It exceeds the 4 anchor ('several specific actions; minor gaps') because no capability area is left out.

5 / 5

Completeness

Both 'what' (the enumerated gate/scoring/veto/feedback actions) and 'when' (an explicit 'Use when the user asks...' clause with concrete trigger phrases) are clearly and explicitly stated. This matches the 5 anchor directly; the 4 anchor's 'when could be more explicit' does not apply since trigger phrases are quoted verbatim.

5 / 5

Trigger Term Quality

It includes natural user phrasings quoted verbatim ('review this influencer content', 'check if this post meets brand guidelines') plus bilingual trigger terms ('达人内容审核/发布前质检'), which is good keyword coverage. It falls short of the 5 anchor because common variations like 'content approval', 'creator post review', or 'sponsorship disclosure check' are missing.

4 / 5

Distinctiveness Conflict Risk

The niche is distinct (influencer pre-publish content gate) and it adds explicit negative boundaries — 'Not for drafting the brief — use brief-generator; not for partnership terms — use contract-helper' — routing adjacent intents away. Minimal conflict risk, matching the 5 anchor.

5 / 5

Total

19

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 9 suspicious

Warning

Total

13

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

influencer/activate/creator-content-auditor/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.