CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

offer-claims-registry

Use when the user asks to "register this claim", "log our current offers", or "where is the proof for this figure"; curates claim wording, evidence, disclosures, terms, review dates, and live offers through the append-only claims event stream. Not for scoring claim vetoes — use the relevant auditor; not for writing ad copy — use ad-creative-builder. 广告声明台账/优惠信息登记/证据溯源

Quality

86%

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

78%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 terse, well-structured protocol skill with concrete commands and a clearly sequenced procedure including validation checkpoints. Its main weakness is progressive disclosure: most referenced files resolve outside the shipped skill folder, so a standalone consumer cannot follow the required protocol references.

Suggestions

Vendor or inline the essential content of the external protocol references (registry-event-protocol.md, runtime-invocation.md) into the skill's own references/ directory, or inline a minimal request-schema example in SKILL.md, so the procedure is executable from the bundle alone.

Add an explicit failure-handling step after `verify claims` and after revision-check rejection (e.g., re-read projection, re-propose with corrected expected_revision, or surface the gap in the handoff summary) to close the workflow feedback loop.

Fix or qualify the non-resolving links (`../../references/*`, `../../SECURITY.md`, cross-skill Next Best Skill links) — either ship them in the bundle, use paths relative to the skill root, or mark them as repo-level dependencies that a standalone install should not rely on.

DimensionReasoningScore

Conciseness

Lean and dense throughout — e.g., 'Missing proof stays `none-on-file` in a proposal or open loop. Never turn `[needs source]` into Approved from the assertion itself.' No padding and no explanation of concepts Claude already knows; every token earns its place.

5 / 5

Actionability

Provides mostly executable guidance: the concrete append command `python3 "$AARON_SKILLS_ROOT/scripts/registry-events.py" append claims <proposal.json>`, the AARON_SKILLS_ROOT resolution expression, `verify claims`, and explicit NEEDS_INPUT behavior. Not a 5 because the proposal request schema and the registry/event-protocol details critical to execution live in reference files, several of which are not present in the bundle.

4 / 5

Workflow Clarity

The 8-step procedure is clearly sequenced with real checkpoints (read-only empty-projection check, revision inheritance on acceptance, `verify claims` after regenerating views), satisfying the validation requirement for append-only/batch writes. Not a 5 because there is no feedback loop specifying what to do when `verify claims` or a revision check fails.

4 / 5

Progressive Disclosure

Section structure is clean and references are clearly signaled one level deep, but scored against the actual bundle, 4 of the 5 reference links (`../../references/registry-event-protocol.md`, `../../references/runtime-invocation.md`, `../../references/measurement-protocol.md`, `../../SECURITY.md`) point outside the skill folder and do not exist in the shipped bundle — only `references/claims-ledger-schema.md` resolves. That is a genuine navigation failure rather than the 'minor organization gaps' of anchor 4.

3 / 5

Total

16

/

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: third-person, concrete, with explicit trigger phrases and unusually good negative boundary routing to adjacent skills. The only gap is modest synonym coverage in trigger terms.

DimensionReasoningScore

Specificity

Lists multiple concrete, comprehensive actions in third person — 'curates claim wording, evidence, disclosures, terms, review dates, and live offers through the append-only claims event stream' — with no vague filler. Coverage is complete for the domain rather than having minor gaps, so it exceeds the anchor-4 example.

5 / 5

Completeness

Explicitly answers both questions: the 'what' (curates wording, evidence, disclosures, terms, review dates, live offers) and the 'when' (an explicit 'Use when...' clause with three concrete quoted trigger phrases). This directly matches the anchor-5 example pattern.

5 / 5

Trigger Term Quality

Quotes natural trigger phrases users would actually say: 'register this claim', 'log our current offers', 'where is the proof for this figure'. Falls short of anchor 5 because common synonyms such as 'claims ledger', 'substantiation', or 'offer registry' are absent.

4 / 5

Distinctiveness Conflict Risk

Has a clear niche (claims/offer registry) with explicit negative boundary guidance — 'Not for scoring claim vetoes — use the relevant auditor; not for writing ad copy — use ad-creative-builder' — minimizing conflict with neighboring skills.

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

protocol/offer-claims-registry/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.