CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

research-prep

Pesquisa fontes tecnicas, evidencia e alternativas antes de implementar. Trigger em: "pesquisa tecnica", "levanta informacao", "coleta docs", "busca referencias", "preciso de fontes", "research antes de escrever", "levanta o que existe sobre", "benchmark de solucoes", "o que existe sobre X", "quero entender o estado da arte", "compara abordagens", "levanta referencias", "faz um research de", "coleta fontes sobre", "pesquisa sobre", "quero saber o que existe de", "monta um dossie tecnico", "background tecnico", "due diligence tecnica", "levantamento de alternativas".

Quality

79%

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/48-research-prep/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.

This is a strong, execution-ready protocol: every phase has concrete commands, quantified thresholds, and genuine validation feedback loops (cache check, pre-flight gate, source-count checkpoint, citation-verification gate). The main structural weakness is that a ~290-line monolithic SKILL.md keeps everything inline — the output template and scoring rubrics are natural candidates for one-level-deep reference files — plus a dangling `--update` flag reference.

Suggestions

Move the Fase 4 output template (and optionally the two scoring tables) to references/output-template.md and references/scoring.md, keeping SKILL.md a phase-by-phase overview with clearly signaled links — this shortens the always-loaded context while keeping the details one level deep.

Define or remove the `--update` flag: the output template says "Re-pesquisar com `--update` após 7 dias" but neither the argument-hint nor Fase 0 describes it; either add it to the argument-hint and Fase 0 behavior, or drop the mention.

Give an executable age check for the cache (e.g. `find memory/research -name '<slug>.md' -mtime -7`) so the <7-day rule in Fase 0 is machine-checkable rather than implied.

DimensionReasoningScore

Conciseness

The body is dense operational protocol — commands, scoring tables, ledger schema, output template — with almost no explanation of concepts Claude already knows. Minor trimmable material exists: the multi-repository attribution paragraph in the intro quote, and the Anti-padrões section which restates rules already given in Fases 0, 3 and 3.5 (e.g. "Guardar fontes com score < 4.0" and "Re-pesquisar sem checar cache"). This lands on anchor 4 (efficient, minor instances that could be trimmed) rather than 5 because of that redundancy.

4 / 5

Actionability

Guidance is largely copy-paste ready: concrete `gh search repos/issues` commands with --json field lists, `site:` query templates, an explicit weighted formula "(oficial×0.4) + (recência×0.3) + (profundidade×0.2) + (comunidade×0.1)" with a 4.0 cutoff, a jsonl ledger example, and a complete output template. It stops short of anchor 5 due to small gaps: the output template references a `--update` flag that the argument-hint and protocol never define, and the <7-day cache check gives `ls memory/research/` but no command for checking file age.

4 / 5

Workflow Clarity

Phases 0→1→1.5→2→3→3.5→4 are clearly sequenced with explicit validation checkpoints and feedback loops: the cache check (Fase 0), the pre-flight query-quality gate before spending search budget (Fase 1.5), the checkpoint "se restarem menos de 3 fontes acima de 4.0 ... voltar e ampliar a busca", and the Fase 3.5 citation-verification gate that routes unsupported claims to "Gaps Identificados". This matches anchor 5 (clear sequence, explicit validation, error-recovery loops); the only blemish — two sections both numbered "Fase 3" — is labeling, not sequencing.

5 / 5

Progressive Disclosure

The bundle contains no references/, scripts/ or assets/ — everything (~290 lines) is inlined in SKILL.md, including a ~60-line output template and two full scoring-rubric tables that could live in one-level-deep reference files. Structure within the file is good (clear headers per phase), which puts it above anchor 2, but there is no overview-to-detail layering at all, matching anchor 3 ("some structure ... content that should be separate is inline"); it is not 4 because nothing is split out despite the length.

3 / 5

Total

16

/

20

Passed

Description

73%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 pairs a concise, concrete what-statement with an unusually rich and natural trigger list, giving excellent discoverability. Its weaknesses are a thin what-statement that hides the skill's distinctive outputs (ranked sources, evidence ledger, dossier file) and several overly broad triggers that risk overlap with adjacent research skills in the same suite.

Suggestions

Expand the what-statement to name the deliverable, e.g. "Pesquisa, pontua e ranqueia fontes tecnicas (docs, repos, SO, papers) e salva um dossie com ledger de evidencias em memory/research/<slug>.md antes de implementar" — this raises specificity and completeness without adding bulk.

Narrow the most generic triggers ("pesquisa sobre", "background tecnico", "coleta docs") or qualify them with the technical/external-sources scope to reduce conflict with sibling research skills like 18 (repo-auditor) and 29 (design-intelligence).

DimensionReasoningScore

Specificity

"Pesquisa fontes tecnicas, evidencia e alternativas antes de implementar" names the domain and 2-3 related actions (research sources, evidence, alternatives) but omits the skill's distinctive mechanics — ranking/scoring sources, the evidence ledger, and the structured dossier output in memory/research/. This matches anchor 3 ("names domain and 1-2 concrete actions, but not comprehensive"); it is not 4 because several specific actions from the body are missing, and not below 3 because the actions stated are concrete rather than generic.

3 / 5

Completeness

Both parts are present: the "what" ("Pesquisa fontes tecnicas, evidencia e alternativas antes de implementar") and an explicit "when" (the "Trigger em:" clause with concrete trigger phrases). It falls between anchors 4 and 5: the when-clause is as explicit as anchor 5 requires, but the what is a single thin sentence that does not convey the output artifact or ranking behavior, so it does not "clearly and explicitly" answer what as fully as the anchor-5 example.

4 / 5

Trigger Term Quality

The Trigger clause lists ~20 natural user phrasings with synonym coverage: "pesquisa tecnica", "levanta informacao", "coleta docs", "busca referencias", "preciso de fontes", "research antes de escrever", "benchmark de solucoes", "o que existe sobre X", "compara abordagens", "monta um dossie tecnico", "due diligence tecnica". This comprehensively covers natural terms including colloquial variations ("faz um research de"), matching anchor 5; a user would naturally say many of these phrases.

5 / 5

Distinctiveness Conflict Risk

The description is somewhat specific (external technical sources) but broad triggers like "pesquisa sobre", "background tecnico", "coleta docs" and "benchmark de solucoes" overlap with other research/documentation skills — indeed the body itself notes skill 29 (design-intelligence) and skill 18 (repo-auditor) cover adjacent research territory, and nothing in the description alone disambiguates. This matches anchor 3 ("somewhat specific but could still overlap with similar skills"); it is not 4 because several listed triggers would plausibly fire for sibling research skills.

3 / 5

Total

15

/

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/48-research-prep/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.