CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

claims-gate

Checks every claim in a piece of copy (ads, emails, posts, pages, scripts, briefs) against the claims the brand has approved. Keeps, rewrites or cuts each line, and lists the proof that would bring a cut line back. When a line the copy needs has no approval, it asks for a short sign-off on the 3 or 4 lines that matter and records the answer. Use alone when you already have the copy and a brand set up; otherwise run the playbook for the job (e.g. make-static-ads, make-content, write-outreach).

Quality

84%

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

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.

An unusually lean and actionable instruction-only skill: exact tool calls, verbatim templates, and a validation read-back loop make it largely executable as written. The main weaknesses are a missing set of referenced bundle files (claim-types.md, local-claims.md, record-skeleton.md) that parts of the workflow depend on, and a dense cross-reference style that makes the multi-path workflow harder to follow than it needs to be.

Suggestions

Ship the referenced bundle files (claim-types.md, local-claims.md, record-skeleton.md) with the skill — §2.2's type-and-risk classification and the local-mode contract cannot be executed without them — or inline their essential content into SKILL.md.

Consolidate the brain-path caveat stated in §1, §4.6 and §5 into a single place and reference it, trimming the repeated explanation of the older-path/brain-path distinction.

Replace dense inline cross-references (§4.2, §5's status rule, marketing-guide §1.4) with a short labeled subsection or summary of the status/approver rules so the sequence can be followed without jumping between sections.

DimensionReasoningScore

Conciseness

The body is extremely dense with zero concept-explanation padding — every section is operational (tool calls, formats, status rules), assuming Claude's competence. Not 5: the brain-path caveat (a chat yes is not yet usable) is repeated across §1, §4.6 and §5, and the older/brain path distinction is explained twice, so a modest trim is possible.

4 / 5

Actionability

Highly concrete for an instruction-only skill: exact tool invocations (`gooseworks:brand_read` with `sections: ["learnings"]`), verbatim marker and fact-format templates, per-category review-date rules, and worked examples of output lines. Not 5: the claim type/risk taxonomy is delegated to `claim-types.md` which is not present in the bundle, and the multi-select sign-off question is described but never exemplified.

4 / 5

Workflow Clarity

Clear §1→§5 sequence (load contract, check spans, act, sign-off, record) with an explicit validation feedback loop ("Read back the learnings … If the call failed, retry it before any line is used") and ordering constraints ("Record the answer before any line is used"). Not 5: the dense web of cross-references (§4.2, §5's status rule, brain path §4.6, external marketing-guide sections) forces the reader to jump around to follow the flow.

4 / 5

Progressive Disclosure

References are clearly signaled, purpose-stated, and one level deep (`claim-types.md`, `local-claims.md`, `record-skeleton.md` "next to this file"), but none of these files exist in the bundle being evaluated — no references/, scripts/, or assets/ directories and no such files at the skill root. Not 4: the split between inline body and bundle files cannot be verified, and the inline body carries substantial detail (local-mode procedure, record layout) that the missing files were meant to hold; not 2 because the references that do exist are well-signaled rather than buried.

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: third-person, concrete, and comprehensive, with an explicit use-when clause that also carves out boundaries against sibling playbooks. The only gap is a few missing natural trigger synonyms (compliance, substantiation, marketing copy).

DimensionReasoningScore

Specificity

Lists multiple concrete actions covering the full workflow: "Checks every claim in a piece of copy … against the claims the brand has approved", "Keeps, rewrites or cuts each line", "lists the proof that would bring a cut line back", "asks for a short sign-off … and records the answer". Not 4: coverage spans check, act, sign-off, and record with no notable gaps.

5 / 5

Completeness

Explicitly answers both: the "what" (check claims against approved list, keep/rewrite/cut, list needed proof, get sign-off, record) and the "when" ("Use alone when you already have the copy and a brand set up; otherwise run the playbook for the job"). The when-clause is concrete and even includes negative guidance.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "claims", "copy", "ads", "emails", "posts", "pages", "scripts", "briefs", "approved", "sign-off". Not 5: common synonyms a user might say — "compliance", "substantiation", "marketing copy", "legal review" — are absent; not 3 because many natural, user-sayable terms are present.

4 / 5

Distinctiveness Conflict Risk

Clear niche — a claim-approval gate for brand copy — with explicit boundaries against sibling playbooks ("make-static-ads, make-content, write-outreach") and when to run it alone. Minimal overlap risk with generic copywriting or brand skills.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 1 possibly missing (local-claims.md), 1 suspicious

Warning

Total

14

/

16

Passed

Repository

gooseworks-ai/goose-skills

Path

skills/marketing/claims-gate/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.