CtrlK
BlogDocsLog inGet started
Tessl Logo

domain-authority-auditor

40-item CITE domain audit: citation, impact, trust, entity scoring with veto checks. 域名权威/网站可信度

56

Quality

65%

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

Fix and improve this skill with Tessl

tessl review fix ./.cursor/skills/domain-authority-auditor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

62%

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

The body has strong workflow sequencing with validation checkpoints, but is padded with promotional boilerplate and leans on an external unbundled reference for its core scoring criteria, capping conciseness, actionability, and progressive disclosure at 2.

Suggestions

Bundle the canonical cite-domain-rating.md locally (or inline the 40-item criteria) so the core scoring guidance does not depend on an external URL.

Trim promotional headers and library/marketplace links and deduplicate the veto-item explanations that recur in Step 1, Tips, and Validation Checkpoints.

Replace the external GitHub links to references with relative bundle paths where the files exist locally.

DimensionReasoningScore

Conciseness

The body is mostly instructional but padded with marketing boilerplate (library/ClawHub/skills.sh links), repeated veto explanations across Steps, Tips, and Validation, and decorative headers; it could be tightened and is not the lean 3.

2 / 3

Actionability

Concrete report templates, weight tables, and scoring formulas are provided, but the actual 40-item scoring criteria are deferred to an external cite-domain-rating.md reference that is not bundled locally, leaving the core guidance incomplete.

2 / 3

Workflow Clarity

Steps 1-4 are clearly sequenced with a veto-first ordering and explicit Input/Output Validation Checklists, matching the anchor for a clear sequence with validation steps and checklists.

3 / 3

Progressive Disclosure

The bundled example-report.md is correctly linked one level deep, but the canonical 40-item reference (cite-domain-rating.md) is repeatedly pointed to an external GitHub URL and is absent from the bundle, so a key reference is not locally progressive.

2 / 3

Total

9

/

12

Passed

Description

67%

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

The description is specific and distinct but lacks an explicit 'Use when...' trigger clause and relies on terminology more than natural user phrasings, capping completeness and trigger quality at 2.

Suggestions

Add an explicit 'Use when...' clause naming natural user phrasings such as 'Use when the user asks how trustworthy or credible a domain is, or before a GEO campaign.'

Fold one or two natural English trigger phrases (e.g. 'domain authority', 'is my site trustworthy') directly into the description string rather than only into metadata triggers.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — '40-item CITE domain audit', 'citation, impact, trust, entity scoring', and 'veto checks' — matching the anchor for naming several specific concrete actions.

3 / 3

Completeness

It clearly states what the skill does but contains no explicit 'Use when...' trigger clause in the description; per the guidelines a missing Use-when clause caps completeness at 2.

2 / 3

Trigger Term Quality

Terms like 'domain audit', 'citation', 'trust', and '域名权威/网站可信度' are relevant but the description string itself lacks the most natural English user phrasings (e.g. 'how trustworthy is my site'), which live in metadata triggers rather than the description.

2 / 3

Distinctiveness Conflict Risk

'40-item CITE domain audit' with veto checks carves a clear niche unlikely to conflict with generic skills; not below 2 because it is clearly distinguishable.

3 / 3

Total

10

/

12

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.

Validation13 / 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

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

13

/

16

Passed

Repository
MODSetter/SurfSense
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.