CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

analyze-performance-intake

Step of the analyze-performance playbook: gathers the week's numbers from tools, exports and pastes, cleans them, and writes the coverage line or switches to claims-only mode. Run analyze-performance instead; not for direct use.

Quality

74%

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 ./skills/marketing/analyze-performance-intake/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 exemplarily terse, high-signal atom: concrete tool commands, explicit edge-case rules, and a well-sequenced workflow with a conditional fallback mode. Its main gaps are heavy dependence on an external measurement contract for key mechanics and a reference layout that lives outside the skill's own bundle.

DimensionReasoningScore

Conciseness

Lean and efficient throughout: the body assumes competence, explains nothing Claude already knows, and packs concrete rules ("never totalled by eye", "de-duplicate by ad id", "no mid-run asks") into ~16 lines with no padding.

5 / 5

Actionability

Mostly executable guidance: named tool reads (`meta_read performance`, `social_analytics_get`, `ads_creative_read`, `video_read`, `campaign_read`), a concrete save path (`reports/performance/inputs/<YYYY-MM-DD>.md`), and explicit decision rules. Not a 5 because key mechanics (minimum read, totalling rules) are deferred to 'contract §4' in an external file that cannot be verified from this bundle.

4 / 5

Workflow Clarity

A clear numbered sequence (1–5, with 3b) covering intake, hygiene, maturity comparison, persistence and coverage, plus an explicit conditional branch to claims-only mode when the referee is missing. Checkpoints like the coverage line and 'mark the referee not measured until it arrives' are present but some validation is implicit rather than an explicit verify step, keeping it below anchor 5.

4 / 5

Progressive Disclosure

Good structure: a clearly signaled one-level-deep reference up front ("Load: `../analyze-performance/references/measurement-contract.md`") with the body kept as a lean overview. Not a 5 because the reference points into a sibling skill's directory rather than a local bundle (no references/, scripts/ or assets/ exist here), so navigation and placement have a minor organizational gap.

4 / 5

Total

17

/

20

Passed

Description

55%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 specific, well-scoped atom description that clearly defers to its parent playbook, making conflict risk minimal. Its weaknesses are the absent 'Use when' trigger guidance and reliance on internal jargon rather than natural user phrases, though both are partly inherent to a not-for-direct-use sub-skill.

Suggestions

Add an explicit trigger clause (e.g. 'Loaded automatically by analyze-performance during intake') so the activation condition is stated, not just the deactivation condition.

Replace or supplement internal jargon like 'coverage line' and 'claims-only mode' with at least one natural phrase a user might say, so the description remains informative out of its playbook context.

DimensionReasoningScore

Specificity

Lists several concrete actions — "gathers the week's numbers from tools, exports and pastes", "cleans them", "writes the coverage line", "switches to claims-only mode" — though "cleans them" is generic and mechanism detail is thin, keeping it below the comprehensive anchor 5.

4 / 5

Completeness

The "what" is clear (gather, clean, write coverage line / switch to claims-only mode), but there is no 'Use when...' clause — only "Run analyze-performance instead; not for direct use", which states when NOT to use it. Per the rubric guideline, a missing explicit trigger caps completeness at 3.

3 / 5

Trigger Term Quality

Terms like "coverage line", "claims-only mode" and "exports and pastes" are internal playbook jargon; no natural phrases a user would say when needing this skill appear. Not a 1 because "numbers", "tools" and "exports" give minimal generic anchoring, but common variations users would actually utter are missing.

2 / 5

Distinctiveness Conflict Risk

It names its parent playbook ("Step of the analyze-performance playbook") and explicitly redirects ("Run analyze-performance instead; not for direct use"), giving it a clear niche with minimal risk of triggering for the wrong skill.

5 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

gooseworks-ai/goose-skills

Path

skills/marketing/analyze-performance-intake/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.