CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

analyze-performance-revenue-join

Step of the analyze-performance playbook: joins cleaned store or CRM numbers with ad spend to build the business-truth table, MER, new-customer cost and the overclaim ratio. Run analyze-performance instead; not for direct use.

Quality

75%

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-revenue-join/SKILL.md
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.

An exceptionally lean, well-structured atom with concrete formulas, explicit inputs, and a defined output contract. Its main weaknesses are the missing validation checkpoints in the workflow and a Load pointer to a reference file that is not part of this bundle, which leaves one step's detail unresolvable.

Suggestions

Ship the revenue-join.md reference inside this skill's own references/ directory (or inline the like-for-like calculation) so the 'as in the reference' dependency resolves when the atom is used standalone.

Add a light validation step, e.g. sanity-check that store/CRM weeks align with spend weeks and that claimed totals exceed store totals before computing the overclaim ratio.

Clarify where 'the story the marketer picked' is read from (which section of last week's report) so step 5's carry-forward rule is fully executable.

DimensionReasoningScore

Conciseness

The ~20-line body is pure instruction — Load, Inputs, six numbered Do steps, Output — with zero padding and no explanation of concepts Claude already knows. Every line tells the agent something it could not infer, matching 'lean and efficient; every token earns its place'.

5 / 5

Actionability

Concrete guidance throughout: exact formulas ("claimed purchases ÷ store orders", "Δ new-customer revenue ÷ Δ spend"), named metrics with comparison baselines (break-even/allowable/target, last week, 4-week average), and a specified output location. Not 5 because key detail ("like-for-like as in the reference") is deferred to ../analyze-performance/references/revenue-join.md, which is not present in this bundle, leaving that step unresolvable standalone.

4 / 5

Workflow Clarity

Steps 1-6 give a clear, well-ordered sequence (truth table → core metrics → overclaim → marginal → conflicting-story handling → B2B variant) with explicit Inputs and Output sections. Not 5 because there are no validation or sanity-check checkpoints (e.g., confirming the join keys or that store numbers are complete before computing ratios); not 3 since the sequence is complete with no real gaps, and no destructive/batch cap applies.

4 / 5

Progressive Disclosure

Sections (Load/Inputs/Do/Output) are well organized and the single reference is clearly signaled, but the referenced file ../analyze-performance/references/revenue-join.md does not exist in this bundle (no references/, scripts/, or assets/ directories), so the disclosure chain is broken — the deferred detail is unreachable. This sits between 'references present but not clearly signaled' (3) and 'minor organization gaps' (4); the dangling pointer is more than minor.

3 / 5

Total

16

/

20

Passed

Description

62%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.

The description is specific and highly distinctive with concrete metric names, but it completely lacks trigger guidance — it defers invocation to the parent analyze-performance skill and says so. As a standalone description it answers 'what' well but not 'when'.

Suggestions

Add an explicit trigger clause or equivalent guidance (e.g., 'Loaded automatically as part of the analyze-performance playbook revenue-join step') so the when is stated rather than implied by 'not for direct use'.

Broaden natural keyword coverage slightly — terms a marketer would actually say (e.g., 'ad spend vs sales', 'return on ad spend', 'ROAS/MER reporting') — to strengthen trigger matching if this atom is ever surfaced independently.

Optionally mention the marginal-analysis and two-stories outputs in the capability list so the 'what' fully covers what the skill produces.

DimensionReasoningScore

Specificity

"joins cleaned store or CRM numbers with ad spend to build the business-truth table, MER, new-customer cost and the overclaim ratio" lists several concrete actions (join, build table, compute MER/nCAC/overclaim ratio). Not 5 because it omits other things the skill does (marginal analysis, the two-stories output, B2B variant); not 3 because it goes well beyond 1-2 actions. Third person voice is used throughout.

4 / 5

Completeness

The 'what' is clear (joins store/CRM numbers with ad spend to build specific metrics), but there is no 'when' — no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. The 'not for direct use' statement confirms the when is delegated to the parent skill rather than stated.

3 / 5

Trigger Term Quality

Domain terms like "ad spend", "CRM", "MER", "overclaim ratio" are relevant, but there is no natural user-facing trigger phrasing at all — the description actively redirects with "Run analyze-performance instead; not for direct use". This matches 'some relevant keywords but missing common variations or synonyms' rather than the good coverage of anchor 4.

3 / 5

Distinctiveness Conflict Risk

"business-truth table", "overclaim ratio", "MER", "new-customer cost" form a clear niche unlikely to collide with other skills, and "Run analyze-performance instead; not for direct use" explicitly de-scopes it from direct triggering. Overlap risk is minimal, matching anchor 5.

5 / 5

Total

15

/

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-revenue-join/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.