CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

surge-recon

Growth state reconnaissance — scan existing onboarding flows, acquisition channels, conversion funnels, and growth experiment logs to understand current growth state. Use when asked to "what's our growth state", "audit the funnel", "what growth experiments have we run", "acquisition channel inventory", or before designing new growth experiments.

Quality

80%

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 ./plugins/ai-agency/tonone/bundle/revenue-team/skills/surge-recon/SKILL.md
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.

A well-structured, actionable recon workflow with executable scan commands and clear sequencing. Its main defects are duplicated funnel-stage content across steps, no validation checkpoints for the analysis fields, and — most significantly — critical references (docs/output-kit.md, /atlas-report) that are missing from the bundle, breaking the mandated output-format path.

Suggestions

Bundle docs/output-kit.md (or inline its output-format rules) — the body instructs Claude to follow it, but the file does not exist in the skill bundle, so the required output format is unreachable.

Clarify or provide fallback instructions for the /atlas-report delivery path (e.g., what to do when that skill is unavailable and output exceeds the 40-line CLI budget).

Add concrete detection commands for instrumentation (e.g., grep patterns for analytics/event-tracking calls) so fields like "Tracked?" and "Instrumented" can be answered with evidence rather than guesswork.

Deduplicate the funnel-stage table between Step 1 and the Step 5 output template to reduce token cost.

DimensionReasoningScore

Conciseness

The body is lean — terse scan commands, tables, and bullet checklists with no explanations of concepts Claude already knows. Minor tightening is possible: the funnel-stage table in Step 1 is largely repeated in the Step 5 output template, Step 4's health table overlaps it, and the persona line ("You are Surge — the growth engineer on the Product Team") adds little — matching anchor 4 ("efficient; minor instances that could be trimmed") rather than the every-token-earns-its-place anchor 5.

4 / 5

Actionability

Step 0 provides copy-paste-ready bash find/grep commands, and Steps 1-5 supply concrete fill-in table templates and an output skeleton with explicit placeholders. It falls short of anchor 5 because the analysis steps (1-4) give no concrete detection method for key fields like "Tracked?" / "Instrumented" (e.g., no commands for finding analytics/event instrumentation), leaving minor execution gaps.

4 / 5

Workflow Clarity

A clear, well-sequenced six-step process (Step 0 detect environment → Step 5 present assessment) with a defined output contract. Operations are read-only reconnaissance, so the destructive/batch validation cap does not apply, but there are still no explicit validation checkpoints or feedback loops (e.g., verifying a stage's "Tracked?" answer before filling the assessment), which keeps it at anchor 4 rather than 5.

4 / 5

Progressive Disclosure

Sections are well organized and the skill is largely self-contained, but the body depends on two references that do not exist in the bundle: "Follow the output format defined in docs/output-kit.md" (no docs/ directory exists) and "invoke /atlas-report" (not part of this skill). References that are broken rather than clearly signaled, plus a >50-line body that inlines the full output template, match anchor 3 ("references present but not clearly signaled; content that should be separate is inline").

3 / 5

Total

15

/

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 strong description: it clearly states what the skill does and when to use it, with natural quoted trigger phrases and a distinct growth-recon niche. The only weaknesses are single-verb action phrasing and a couple of missing trigger synonyms plus one generically-worded trigger ("audit the funnel").

DimensionReasoningScore

Specificity

"scan existing onboarding flows, acquisition channels, conversion funnels, and growth experiment logs" names four concrete scan targets, but all actions are variations of a single verb (scan) rather than the multiple distinct operations of the anchor-5 example, leaving minor coverage gaps (e.g., no mention of assessing instrumentation or producing an assessment). Fits anchor 4 ("lists several specific actions; minor gaps") and not 3, since coverage goes well beyond 1-2 actions.

4 / 5

Completeness

Explicitly answers both: what ("Growth state reconnaissance — scan existing onboarding flows, acquisition channels, conversion funnels, and growth experiment logs to understand current growth state") and when ("Use when asked to 'what's our growth state', 'audit the funnel'...") with concrete trigger phrases. This is a direct match for the anchor-5 example pattern; it is clearly above anchor 4, where the 'when' is only loosely specified.

5 / 5

Trigger Term Quality

Includes natural quoted phrases users would actually say — "what's our growth state", "audit the funnel", "what growth experiments have we run", "acquisition channel inventory" — plus a proactive trigger "before designing new growth experiments". A few common synonyms are missing (e.g., "growth audit", "funnel analysis", "onboarding review"), which matches anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The growth-reconnaissance niche (onboarding flows, funnels, growth experiment logs) is distinct with dedicated triggers, but "audit the funnel" is generic enough to overlap with funnel-analytics or data-audit skills — minor overlap risk with closely related skills, matching anchor 4 rather than the minimal-conflict anchor 5.

4 / 5

Total

17

/

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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

jeremylongshore/tons-of-skills-marketplace

Path

plugins/ai-agency/tonone/bundle/revenue-team/skills/surge-recon/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.