CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

jev-opportunity-scout

Busca oportunidades de produto e crescimento a partir do projeto. Trigger em: "onde eu poderia usar o jev", "faz sentido usar typesafe aqui", "classificação está frágil", "if/else de categoria", "onde usar judgment tipado", "oportunidade de ia semântica", "roteamento por regex está ruim", "analisa esse código pra ver onde IA ajudaria", "jev opportunity", "system one typesafe".

Quality

79%

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/80-jev-opportunity-scout/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

73%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-engineered, highly actionable read-only scouting workflow with a clear protocol, real validation checkpoints, and a genuine reference bundle — the strongest dimensions are workflow clarity and actionability. Its weaknesses are rhetorical redundancy (the assertiveness mantra and install command repeated multiple times, handoff content stated in three places) and small structural sloppiness (dangling kit-file references and PoC details duplicated between body and reference).

Suggestions

State the assertiveness expectation once (in the intro or as a single global rule) and cut the repetitions in "Governanca Global", the report template, and "Quando Nao Usar" — the same install command and handoff target appear three times and could be consolidated into the Handoff section.

Turn the signal table's prose descriptions into one or two ready-to-run Grep patterns (e.g. a regex for `.includes(` chains or `TODO.*detect` style comments) so step 1 is copy-paste executable like the rest of the protocol.

Remove the inlined jev-ultrafast performance numbers from the body and keep them only in references/jev-ultrafast-local.md (a one-line pointer suffices), and either include the referenced policies/ files in the bundle or mark them as external kit dependencies.

DimensionReasoningScore

Conciseness

The body is mostly dense and substantive (signal table, cost formula, report template), but the assertiveness framing repeats roughly four times ("Ser assertiva é o ponto desta skill", "munição completa, não uma sugestão frouxa", "não um resumo vago", "não terceirizado por preguiça"), the install command appears three times, and handoff content is duplicated across the intro, "Quando Nao Usar", the report template, and the Handoff section. That is more than the "minor instances" of anchor 4 but well above anchor 2's heavy padding.

3 / 5

Actionability

Guidance is largely executable: a concrete signal-pattern table, target directories ("services/", "handlers/", "routes/", "lib/"), a real-API call format with documented fields ("type", "instructions", "criteria"), exact cost math ("$0.042 / 1.000.000"), and a copy-paste report template. The gaps keeping it from anchor 5 are that the Grep signals are described in prose rather than as ready-to-run patterns ("Usar Grep com os padrões acima" requires translation) and the call example is a placeholder template rather than a worked example.

4 / 5

Workflow Clarity

The five-step protocol (varredura → classificar → montar exemplo → calcular custo → relatório) is clearly sequenced with explicit validation: the determinism guard ("Nunca reportar como candidato um if/else que já é 100% determinístico e correto") filters findings before reporting, the "Evidencia de Conclusao" checklist verifies the deliverable, and the "Nenhum candidato encontrado em" section forces explicit negative confirmation. The skill is read-only by design (allowed-tools excludes Bash/Write/Edit), so the destructive/batch validation cap and error-recovery loops do not apply.

5 / 5

Progressive Disclosure

The body works as an overview with four real, one-level-deep, clearly signaled references ("ver references/pricing.md", "references/decision-shapes.md", "references/o-que-e-jev.md", "references/jev-ultrafast-local.md"), all verified to exist and hold the promised detail. It falls short of anchor 5 because "GLOBAL.md" and "policies/execution.md"/"policies/handoffs.md"/"policies/tool-safety.md" are referenced but absent from the bundle, and the PoC numbers (~9.4s → ~7.1s) are inlined in the body, duplicating content in references/jev-ultrafast-local.md.

4 / 5

Total

16

/

20

Passed

Description

77%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 distinctive description with excellent, natural trigger coverage and correct third-person voice, undermined by a vague capability sentence that says only "Busca oportunidades" without naming the concrete actions (scanning for fragile heuristics, mapping to Choice/Noul/Score, calculating cost). The trigger list does the heavy lifting that the "what" statement should share.

Suggestions

Rewrite the opening sentence to state the concrete actions, e.g. "Escaneia o projeto em busca de decisão semântica implementada com heurística frágil (substring match, lista de palavras-chave, prompt-and-parse), classifica cada candidato em Choice/Noul/Score, monta a chamada equivalente e calcula o custo real por chamada."

State the deliverable explicitly in the description (a report with arquivo + linha, primitivo, exemplo de chamada e custo) so the "what" answers what the user receives, not just what the skill searches for.

Consider trimming the trigger list slightly and reallocating characters to capability specifics — ten triggers is comprehensive but two or three broader ones ("analisa esse código pra ver onde IA ajudaria") carry overlap risk with generic AI-integration skills.

DimensionReasoningScore

Specificity

"Busca oportunidades de produto e crescimento a partir do projeto" names the domain with one generic action; the concrete capability territory (fragile classification, if/else routing, typed judgment) surfaces only through trigger phrases, not stated actions. It sits between anchor 2 (generic actions) and anchor 3 (1-2 concrete actions), but the trigger list prevents it from dropping to pure domain-naming.

3 / 5

Completeness

Both parts are present: a "what" ("Busca oportunidades de produto e crescimento a partir do projeto") and an explicit "when" ("Trigger em: ...") with concrete phrases, so the missing-trigger cap of 3 does not apply. It falls short of anchor 5 because the "what" is generic — it never states that the skill scans code for fragile semantic-decision heuristics and delivers candidate reports with cost.

4 / 5

Trigger Term Quality

Ten natural trigger phrases with good synonym coverage — "onde eu poderia usar o jev", "classificação está frágil", "if/else de categoria", "roteamento por regex está ruim", "analisa esse código pra ver onde IA ajudaria", "jev opportunity" — phrasings a user would genuinely say. This matches the comprehensive-coverage anchor; nothing meaningful is missing for the domain.

5 / 5

Distinctiveness Conflict Risk

Brand-specific triggers ("jev", "faz sentido usar typesafe aqui", "system one typesafe", "onde usar judgment tipado") create a clear niche, but broader phrases like "analisa esse código pra ver onde IA ajudaria" and "oportunidade de ia semântica" overlap with closely related AI-integration skills — the body itself has to delineate a boundary against skill 25. This matches "mostly distinct; minor overlap risk" rather than the minimal-conflict anchor.

4 / 5

Total

16

/

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

metadata_version

'metadata.version' is missing

Warning

Total

14

/

16

Passed

Repository

felvieira/claude-skills-fv

Path

skills/80-jev-opportunity-scout/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.