CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

domain-authority-auditor

Use when auditing domain authority, trust, or citation credibility; runs a peer-relative 40-item CITE profile with evidence coverage and verified manipulation/penalty veto checks. Not for page-level content quality — use content-quality-auditor; not for backlink profiling alone — use offsite-signal-analyzer. 域名权威/网站可信度

Quality

85%

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

81%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 well-engineered instruction-only skill: terse, contract-driven, with executable commands, an explicit validation checklist, and well-signaled one-level references. The main gaps are the unshown schema input shape, an orphaned bundle file (example-report.md), and repo-relative paths that break in standalone installs.

DimensionReasoningScore

Conciseness

The body is dense and imperative with tables and numbered lists, and never explains concepts Claude already knows; minor overlap between the 'Runtime Reads' list and the generated 'Runtime Contract' block, and between the generated report header and its following prose, could be trimmed. Fits 'efficient; minor instances of over-explanation' rather than score 5's every-token-earns-its-place.

4 / 5

Actionability

Concrete executable commands are given ('python3 "$AARON_SKILLS_ROOT/scripts/rubric-score.py" score <run.json>', validate-audit-artifact.py with --relative-path, env-var resolution) plus a numbered 6-step evidence procedure. Not 5 because the audit-run.schema.json input shape is never shown and the referenced scripts/paths resolve only in the monorepo layout, not the standalone bundle; not 3 because the guidance is genuinely executable, not pseudocode.

4 / 5

Workflow Clarity

The sequence (Required Setup → Data Sources → Evidence Procedure → score → Report → Verdict Rules → Persistence) is clear, with an explicit 'Validation Checkpoints' checklist, error-recovery paths (runtime unavailable → NOT_SCORED without a gate verdict; persist → revalidate), and rerun conditions. All three elements of the top anchor are present, so it exceeds score 4's 'minor validation gaps'.

5 / 5

Progressive Disclosure

The body is an overview that clearly signals one-level-deep references in 'Runtime Reads' and 'Reference Materials' sections, with detail pushed to the runbook and runtime file. Not 5 because references/example-report.md exists in the bundle but is never linked from the body, and many '../../../references/...' paths resolve only in the monorepo layout rather than the standalone install.

4 / 5

Total

17

/

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 with explicit what/when structure, concrete capability statements, natural trigger terms, and explicit boundary disambiguation against sibling skills. Minor room to broaden trigger synonyms, but it clearly matches the good-example pattern.

DimensionReasoningScore

Specificity

Concrete capabilities are stated ('runs a peer-relative 40-item CITE profile with evidence coverage and verified manipulation/penalty veto checks'), going beyond naming the domain. Not 5 because it does not comprehensively enumerate the skill's actions (e.g., the report/artifact output is absent); not 3 because several specific actions, not just 1-2, are given.

4 / 5

Completeness

Both questions are explicitly answered: what ('runs a peer-relative 40-item CITE profile with evidence coverage and verified manipulation/penalty veto checks') and when ('Use when auditing domain authority, trust, or citation credibility') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Natural phrases users would say appear verbatim ('domain authority', 'trust', 'citation credibility', 'auditing'), giving good keyword coverage. Not 5 because common synonyms such as 'site authority', 'website credibility', or 'is this site trustworthy' are missing; clearly above score 3's 'missing common variations'.

4 / 5

Distinctiveness Conflict Risk

The description explicitly disambiguates from siblings ('Not for page-level content quality — use content-quality-auditor; not for backlink profiling alone — use offsite-signal-analyzer'), establishing a clear niche with distinct triggers and minimal conflict risk.

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

seo-geo/evaluate/domain-authority-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.