CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

business-discovery

Conduz discovery de negocio e converte respostas em requisitos. Trigger em: "mapear minhas ferramentas", "o que eu deveria automatizar primeiro", "meu negócio usa planilha e whatsapp", "entrevista com o dono", "mapa de dados do meu negócio", "por onde eu começo a automatizar", "auditoria de ferramentas", "dono de negócio sem programador", "arquétipo de negócio", "pantry prep plate", "plano de 30 dias pra automatizar".

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/78-business-discovery/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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 exemplary interview protocol: verbatim dialogue, exact commands, a JSON skeleton, explicit branching, confirm-edit loops, and a real one-level-deep bundle where every referenced file exists and carries its weight. The one real weakness is redundancy — the core rules and the four-file output listing are each repeated across 2-3 sections, which inflates the body without adding information.

Suggestions

Collapse the rule statements into one canonical section: 'Regras rígidas', 'Regras de Voz', and 'Anti-Padroes' repeat the same 5-6 rules (no 'Ótima pergunta!', no schema-format questions, audit before asking, draft-only, confirm-edit). Keep one section and let the stages reference it.

Describe the output anatomy once: 'Saidas Esperadas', the Estágio 10 confirmation screen, and 'Anatomia da Saída' all enumerate the same four files in business_discovery_output/ — the confirmation dialogue could just name them without re-describing each.

Add a short concrete template or 5-10 line example for prompt_handoff.txt (and a sample OPORTUNIDADES.md entry), since those are the only deliverables whose exact shape is left to inference.

DimensionReasoningScore

Conciseness

Almost all content is skill-specific and load-bearing (verbatim dialogue, branch tables, glossary mappings — nothing explains concepts Claude already knows), but the same rules are restated in 'Regras rígidas', 'Regras de Voz', and 'Anti-Padroes' (e.g. 'Sem "Ótima pergunta!"' and 'nunca perguntar em formato de schema' each appear in all three), and the four output files are listed three times ('Saidas Esperadas', Estágio 10, 'Anatomia da Saída'). Matches anchor 3 ('could be tightened'); not 2 because the padding is duplication of real rules rather than generic filler, not 4 because the redundancy is more than minor instances.

3 / 5

Actionability

Highly executable for an instruction-only skill: copy-paste bash commands ('python3 scripts/audit_pasta_existente.py', 'renderizar_mapa.py --input ... --output ...'), ~15 verbatim dialogue blocks, a full JSON skeleton for mapa_dados.json, and explicit three-way branch tables. Falls short of anchor 5 only on the two text deliverables: prompt_handoff.txt has no template (only 'pré-preenchido com o mapa completo') and OPORTUNIDADES.md gets grouping order but no format example. Not 3 because nothing is pseudocode or vague.

4 / 5

Workflow Clarity

Stages 0-10 (with 6.5/6.6/6.7/9.5) are clearly sequenced, each with explicit inputs and branching (greenfield vs auditoria-existente, three Estágio 9.5 responses with distinct routings), plus confirm-edit feedback loops (Estágios 2 and 6.5: 'Sim: confirmar / Não: pular / Ajustar: perguntar') and a completion checklist ('Evidencia de Conclusao' including 'mapa_dados.html gerado e abre sem erro'). The skill is read-only plus writes to its own output folder, so the destructive/batch cap does not apply; matches anchor 5 (explicit validation, feedback loops, checklist).

5 / 5

Progressive Disclosure

All 9 bundle files exist and each is referenced at its point of use with a stated purpose ('Abrir references/recipe_templates.md e puxar as 4-7 receitas de partida'; 'Consultar references/tool_defaults.md ... usar esses valores em silêncio'), one level deep — question chains, tool-default tables, templates, and engineering tips are offloaded while the interview protocol itself stays in SKILL.md. Spot-checks confirm the referenced files are real and substantive. Matches anchor 5 (well-signaled one-level-deep references, appropriate split); the inline archetype summary duplicating arquetipos.md is a table-of-contents pattern, not a nesting violation.

5 / 5

Total

17

/

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 strong trigger list — eleven natural PT-BR phrases with synonym variation — makes the 'when' unambiguous and the skill easy to route to. The weakness is the 'what': one circular action plus 'converte respostas em requisitos', which omits every concrete deliverable and slightly mischaracterizes the body's actual output (a map and opportunities list, explicitly not specs).

Suggestions

State the concrete deliverables in the description, e.g. 'Entrevista um dono de negócio não-técnico e entrega um mapa de dados em HTML, uma lista priorizada de oportunidades (OPORTUNIDADES.md) e um prompt de handoff' — this would raise specificity from naming 1-2 abstract actions to listing what the skill actually produces.

Replace 'converte respostas em requisitos' with the real output framing: the body explicitly says 'a saída é um mapa e uma lista de oportunidades' and 'esta skill entrega, não implementa', so 'requisitos' both over-claims and conflicts with the skill's own boundary.

Consider one boundary clause in the description (e.g. 'não é discovery de usuário de produto nem auditoria de código') to reduce overlap with the 51-ux-research and 18-repo-auditor triggers.

DimensionReasoningScore

Specificity

The description names the domain ('Conduz discovery de negocio') and 1-2 actions ('converte respostas em requisitos'), but 'conduz discovery' is near-circular with the domain itself and the actual deliverables (mapa_dados.html, OPORTUNIDADES.md, prompt_handoff.txt) are never mentioned. This matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive); not 4 because coverage gaps are major rather than minor, not 2 because a second concrete action is explicitly stated.

3 / 5

Completeness

Both parts are present: a 'what' ('Conduz discovery de negocio e converte respostas em requisitos') and a fully explicit 'when' ('Trigger em:' followed by 11 concrete trigger phrases). Falls between anchors 4 and 5: the 'when' exceeds anchor 4's standard, but the 'what' is high-level, omits the deliverables, and says 'requisitos' where the body itself states the output is 'um mapa e uma lista de oportunidades' — so anchor 5's 'clearly and explicitly answers both' is not fully met.

4 / 5

Trigger Term Quality

Eleven natural first-person phrases a Portuguese business owner would actually say, with synonym-level variation ('o que eu deveria automatizar primeiro' / 'por onde eu começo a automatizar'; 'mapear minhas ferramentas' / 'mapa de dados do meu negócio'). Matches anchor 5's comprehensive natural-term coverage; anchor 4's 'a few natural terms missing' fits less well given the breadth and repetition of core intents.

5 / 5

Distinctiveness Conflict Risk

Niche-specific triggers like 'dono de negócio sem programador' and 'pantry prep plate' carve a clear niche, but 'entrevista com o dono' and 'auditoria de ferramentas' carry minor overlap risk with sibling skills the body itself names (51-ux-research interviews, 18-repo-auditor audits), and the description carries no boundary statement. Matches anchor 4 (mostly distinct, minor overlap with closely related skills); not 5 for that unstated boundary.

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/78-business-discovery/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.