CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

social-quality-auditor

Use when the user asks to "audit our social presence" or "is this batch safe to publish"; runs either the typed ECHO asset gate or a separate program-maturity profile, with channel-truth, claim, disclosure, manipulation, UGC-rights, and denominator checks. Not for creator deliverables — use creator-content-auditor; not for launch readiness — use launch-readiness-auditor. 社媒资产门/运营成熟度/发布前放行

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

A dense, disciplined auditor skill body: lean prose, concrete anchors (env var, path patterns, validator script, veto IDs, worked examples), explicit validation checkpoints and a fail-closed path. Its main weaknesses are the broken reference graph in the standalone bundle — five of six runtime/reference paths don't resolve — plus duplicated reference listings and a procedure spread across oddly numbered sections rather than one ordered flow.

Suggestions

Make the reference graph resolve in the standalone bundle: either bundle the root references (auditor-runbook.md, scoring-semantics.md, echo-benchmark.md, runtime-invocation.md, measurement-protocol.md) under references/ or rewrite all runtime reads to point at the bundled references/auditor-runtime.md, which is the only file that currently exists.

Consolidate the 'Runtime Reads' list and the 'Reference Materials' section into a single reference section to remove the duplicated file listings (auditor-runbook, scoring-semantics, echo-benchmark appear in both).

Present the procedure as one ordered sequence (declare target/profile → read runtime → collect observations → verify vetoes → run scorer → report → persist) and renumber or rename the §2/§3/§5 section headers, which currently appear out of order with no §1 or §4.

DimensionReasoningScore

Conciseness

The body is dense and lean with no explanations of concepts Claude already knows, and every section carries operational content. Not 5 because "Runtime Reads" and "Reference Materials" list overlapping files (auditor-runbook.md, scoring-semantics.md, echo-benchmark.md appear in both), and the dense compressed noun-phrases ("channel-truth, claim, disclosure, manipulation, UGC-rights, and denominator checks") duplicate ideas already unpacked elsewhere; not 3 since there is no real padding or over-explanation.

4 / 5

Actionability

Concrete anchors abound: the exact env-var resolution `AARON_SKILLS_ROOT="${CLAUDE_PLUGIN_ROOT:-$(git rev-parse --show-toplevel 2>/dev/null || true)}"`, the persistence path pattern `memory/audits/social/YYYY-MM-DD-<topic>.md`, the named validator `validate-audit-artifact.py`, exact item/veto IDs, and worked examples with exact scores. Not 5 because the core instruction "Run the typed scorer" has no inline invocation detail and defers entirely to `runtime-invocation.md`, which does not exist in this bundle; not 3 since most guidance is executable or precisely specified.

4 / 5

Workflow Clarity

Explicit validation is present: a five-item "Validation Checkpoints" section, a fail-closed `score_state: NOT_SCORED` path when the scorer is unavailable, and a validate → single Write → revalidate persistence loop. Not 5 because the procedure is scattered across sections rather than one ordered sequence, and the oddly numbered "§2 ECHO Worked Examples", "§3 ECHO Guardrails", "§5 ECHO Translation" headers (with no §1/§4) disrupt flow; not 3 since checkpoints and error-recovery paths are explicit, not merely implied.

4 / 5

Progressive Disclosure

The body is well-sectioned and references are clearly signaled by name, but scored against the actual bundle, most referenced paths dangle: `../../../references/auditor-runbook.md`, `scoring-semantics.md`, `echo-benchmark.md`, `runtime-invocation.md`, and `measurement-protocol.md` do not exist in this bundle — only `references/auditor-runtime.md` resolves, alongside cross-skill links (`../engagement-inbox-manager/SKILL.md`, etc.) that also don't resolve. Not 4 because one-level-deep navigation is broken for the majority of reads in the standalone install; not 2 because the body itself is well structured and the one bundled runtime file is clearly signaled and used.

3 / 5

Total

15

/

20

Passed

Description

87%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: it states what the skill does, gives concrete quoted trigger phrases, uses third person, and explicitly routes away from two sibling auditors. The main weakness is reliance on internal framework vocabulary (typed ECHO asset gate, program-maturity, denominator checks) that a user would not naturally say, which slightly limits trigger coverage and plain-language specificity.

DimensionReasoningScore

Specificity

"runs either the typed ECHO asset gate or a separate program-maturity profile, with channel-truth, claim, disclosure, manipulation, UGC-rights, and denominator checks" names several concrete check types, but leans on unexplained internal jargon ("typed ECHO asset gate") rather than plain action verbs. Not 5 because the concrete actions are partly obscured by framework nouns; not 3 since six distinct check categories plus two profile modes exceed '1-2 concrete actions'.

4 / 5

Completeness

Explicitly answers both what ("runs either the typed ECHO asset gate or a separate program-maturity profile, with channel-truth, claim, disclosure, manipulation, UGC-rights, and denominator checks") and when ("Use when the user asks to 'audit our social presence' or 'is this batch safe to publish'") with concrete trigger phrases. Not 4 because neither the what nor the when could reasonably be more explicit, and it adds explicit not-for boundaries.

5 / 5

Trigger Term Quality

Quoted natural triggers "audit our social presence" and "is this batch safe to publish" are phrases a user would genuinely say, and negative boundary phrases help routing. Not 5 because common variations ("social media audit", "safe to post", "pre-publish review") are missing and much of the vocabulary (ECHO, asset gate, denominator) is internal jargon; not 3 since real natural trigger phrases are present.

4 / 5

Distinctiveness Conflict Risk

A clear pre-publish social-asset/program-maturity niche with explicit disambiguation: "Not for creator deliverables — use creator-content-auditor; not for launch readiness — use launch-readiness-auditor". Minimal conflict risk; this matches the anchor-5 example's pattern of distinct triggers and a well-bounded domain.

5 / 5

Total

18

/

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: 8 suspicious

Warning

Total

13

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

social/host/social-quality-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.