CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

analyze-performance-call-and-learn

Step of the analyze-performance playbook: calls ended tests, scores last week's calls, writes this week's kill/scale/hold calls and drafts learnings for the brand brain. 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-call-and-learn/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.

This is a tightly written procedural atom: a numbered 7-step workflow with concrete formats, named artifacts, and explicit human-in-the-loop gates plus a read-back verification loop. The main gaps are deferred details in external references and a few implicit validation steps, but as an instruction-only skill it is strongly actionable.

DimensionReasoningScore

Conciseness

The body is lean and directive — "Draft ≤ 3 learnings as one-line rules", "first look → 'watch'", "one idea per learning" — with zero explanation of concepts Claude already knows and no padding. Every token is an instruction, matching the 'every token earns its place' anchor.

5 / 5

Actionability

Guidance is highly concrete: exact formats ("kind 23 `experiment_readout.<campaign-slug>-t<n>`", "[learning YYYY-MM-DD] (+ ` A-NN`)"), named tools and paths, and precise gates ("only with the marketer present", "Without their words, write nothing"). Not a 5 because several key details (test n floors, the learning template, the outcome-check mechanics) are deferred to reference files outside this skill's own bundle, leaving minor gaps a reader must resolve elsewhere.

4 / 5

Workflow Clarity

A clearly sequenced 7-step procedure with explicit checkpoints: step 7 has a full feedback loop ("read back, compare, report which landed") and step 2 defines the outcome check against concrete artifacts (decisions.md blocks, the paid run's verdict). Not a 5 because some checkpoints are implicit — e.g., step 3's calls and step 6's readout writes have no stated verification step.

4 / 5

Progressive Disclosure

The ~26-line body is well organized with bold Load/Inputs/Do/Output sections and one-level-deep, clearly signaled references ("../analyze-performance/references/tests-and-learnings.md", "../save-learning/SKILL.md"). Not a 5 because those referenced files live in sibling skills' bundles rather than this skill's own directory, so navigation depends on the parent playbook's layout; within this bundle there are no reference files to organize.

4 / 5

Total

17

/

20

Passed

Description

58%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 concrete about its four actions and cleanly defers to the parent skill, keeping conflict risk low. Its main weakness is the absence of any positive "when to use" guidance, which caps completeness, and it offers no natural trigger phrases users would say. Overall a solid but not exemplary sub-skill description.

Suggestions

Add an explicit conditional clause stating when this atom runs (e.g., 'Use only when the analyze-performance playbook instructs it'), which would raise completeness without inviting direct invocation.

Include one or two natural trigger phrases users or the parent playbook would say (e.g., 'test verdicts', 'weekly kill/scale/hold calls') so the description reads naturally rather than purely as an internal routing note.

Briefly mention the readout-writing step in the action list so the description's coverage matches the body's scope.

DimensionReasoningScore

Specificity

Quotes several concrete actions — "calls ended tests, scores last week's calls, writes this week's kill/scale/hold calls and drafts learnings" — which clearly exceed the 1-2-action anchor. Not a 5 because coverage is incomplete: the body's readout writes and replan-trigger checks are absent from the description.

4 / 5

Completeness

The "what" is clear (four concrete actions), but there is no "Use when..." clause or equivalent positive trigger guidance — only the negative directive "Run analyze-performance instead; not for direct use". Per the judging guidelines, a missing explicit when-clause caps completeness at 3.

3 / 5

Trigger Term Quality

Some relevant domain keywords are present ("calls ended tests", "scores last week's calls", "learnings", "analyze-performance") but natural user-facing variations are missing, and the directive "not for direct use" means it offers no positive trigger phrases. Not a 4 because a user needing this skill would more likely say "analyze performance" or "score my calls", which are only weakly covered.

3 / 5

Distinctiveness Conflict Risk

Scoping to "Step of the analyze-performance playbook" plus the explicit redirect "Run analyze-performance instead; not for direct use" makes it mostly distinct and actively defers to the parent skill, avoiding wrong-skill triggering. Not a 5 because it has no distinct positive triggers of its own, only the negative redirect.

4 / 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-call-and-learn/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.