CtrlK
BlogDocsLog inGet started
Tessl Logo

report-pipeline

Use when summarizing pipeline counts, supplied movements, risks, and review priorities from an offline snapshot or comparison period.

71

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

90%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 tight, self-contained instruction-only skill with concrete labels, an exact output template, explicit guardrails, and a verification checklist. Its main limitation is the absence of embedded validation feedback loops in the workflow.

Suggestions

Insert an explicit mid-workflow verification step (e.g., after reconciling counts, confirm each classification ties to the total before moving to movements) to add a validate-fix-retry checkpoint.

Consider splitting the output-format template and guardrails into a short reference file so the SKILL.md body stays a lean overview pointing one level deep.

DimensionReasoningScore

Conciseness

The body is lean and free of padding or explanations of concepts Claude already knows; every section (inputs, workflow, output template, guardrails, quality check) earns its place.

5 / 5

Actionability

Although it is instruction-only with no code (appropriate for a read-only report), the guidance is highly actionable: exact labels ('Unknown', 'Derived arithmetic', 'DRAFT ONLY — READ-ONLY REPORT'), a copy-paste output template, and precise per-step rules.

5 / 5

Workflow Clarity

A clearly sequenced 7-step workflow with an explicit 'Quality check' verification checklist and per-step Unknown-marking; it lacks embedded validate-fix-retry feedback loops, though read-only scope makes those less critical.

4 / 5

Progressive Disclosure

The skill is self-contained with no bundle files and is organized into clear, well-signaled sections; it sits just over the simple-skill line and keeps all content inline, so it falls short of the ideal split/overview pattern.

4 / 5

Total

18

/

20

Passed

Description

83%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 clear, well-structured description that explicitly pairs a concrete 'what' with an explicit 'Use when' trigger. It is lean and uses the conventional imperative voice rather than first/second person.

DimensionReasoningScore

Specificity

The description lists several concrete reporting objects ('pipeline counts, supplied movements, risks, and review priorities') under one action verb, giving good coverage with only minor gaps versus the comprehensive anchor.

4 / 5

Completeness

It explicitly answers both 'what' (summarizing counts, movements, risks, priorities) and 'when' via a concrete 'Use when ... from an offline snapshot or comparison period' trigger clause.

5 / 5

Trigger Term Quality

Natural domain terms like 'pipeline counts', 'movements', 'risks', 'review priorities', 'offline snapshot', and 'comparison period' give good keyword coverage, though a few common user phrasings are missing.

4 / 5

Distinctiveness Conflict Risk

The offline-snapshot/comparison-period reporting niche is mostly distinct, but 'summarizing pipeline counts and risks' could overlap with general analysis or reporting skills.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
llaskin/AI-SDR-Skill-Pack
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.