CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

research-brief

Prepare a dated, source-backed research brief that preserves conflicting findings and uncertainty.

Quality

69%

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 ./test/fixtures/collective-learning/research-brief/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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.

The body is a lean, expert-facing instruction set with no wasted tokens and a sensible file split across scripts and a one-level-deep reference. Its weaknesses are executability gaps — a referenced template that does not exist, an undocumented citations.py invocation, and a vague timezone check — and an implicit rather than explicit step ordering.

Suggestions

Add the missing templates/brief.md to the bundle (or inline the brief structure) so the referenced deliverable template actually resolves.

Number the workflow steps in execution order (read sources → normalize with normalize_sources.py → assemble with citations.py → build with build_brief.py → verify against sources → return outputs), and document citations.py's invocation arguments the way build_brief.py's are documented.

Replace "Check timezone applicability before choosing it" with a concrete check, e.g., which timezone field or condition to inspect in the source records before selecting the Node alternative.

DimensionReasoningScore

Conciseness

The ~250-word body is all task-specific instruction with zero padding: it never explains what a research brief is or why citation matters, and assumes Claude's competence throughout (e.g., "Keep publication date, observation date and retrieval date distinct when they differ"). Every sentence carries a rule or a tool pointer, matching the "lean and efficient; every token earns its place" anchor; nothing qualifies as the trimmable over-explanation of anchor 4.

5 / 5

Actionability

There is concrete guidance — "Run scripts/build_brief.py with the input JSON, output JSON and output Markdown paths", plus named scripts for normalization and citation assembly — but key details are missing: "Use templates/brief.md for the deliverable" points to a file that does not exist in the bundle, citations.py is invoked with no argument pattern, and "Check timezone applicability before choosing it" gives no concrete check. This matches anchor 3 (some concrete guidance but incomplete, missing key details) rather than anchor 4's "minor gaps".

3 / 5

Workflow Clarity

A full sequence exists (read sources → normalize dates → assemble citations → draft/build → verify against sources → return brief.json and brief.md) with a real validation checkpoint ("Check the generated brief against the sources", "Keep a generated brief in draft until reviewed"), but the order must be inferred: build_brief.py is introduced in the first paragraph before the normalization and citation-assembly steps it logically follows, and no numbered ordering or section structure makes the actual execution order explicit. This lands on anchor 3 (sequence present but implicit) rather than anchor 4's "clear sequence".

3 / 5

Progressive Disclosure

Scored against the actual bundle: all four scripts in scripts/ are referenced in the body with a stated purpose each, references/source-rules.md is a real, one-level-deep reference clearly signaled for its specific cases ("Consult references/source-rules.md for these cases"), and no reference chains further. Minor organization gaps keep it from anchor 5: the body is flat prose with no section headers, and the referenced templates/brief.md is absent from the bundle, but content is otherwise appropriately split between SKILL.md, scripts, and the reference file.

4 / 5

Total

15

/

20

Passed

Description

53%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 communicates a clear, distinctive deliverable in one tight sentence, but it omits any "when to use this" trigger guidance, which caps completeness and weakens trigger-term quality. Adding a "Use when..." clause with the natural phrases users would say (e.g., summarizing research, comparing sources, conflicting findings) would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g., "Use when asked to summarize research or multiple sources into a brief, or when findings conflict or evidence is uncertain."

Include natural user-facing synonyms such as "literature summary", "source comparison", or "cite sources" alongside "research brief" to improve trigger-term coverage.

Name one or two more concrete actions (e.g., normalizing publication dates, citing every quantitative finding) to raise specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

The description names the domain and one concrete deliverable — "Prepare a dated, source-backed research brief" — with meaningful qualifiers ("preserves conflicting findings and uncertainty"), matching the anchor for 1-2 concrete actions that are not comprehensive. It does not list several specific actions (e.g., normalizing dates, citing quantitative findings, flagging contradictions), so it falls short of anchor 4, while being far more concrete than the generic single-action examples at anchor 2.

3 / 5

Completeness

The "what" is clear (prepare a dated, source-backed research brief preserving conflicts and uncertainty), but there is no "Use when..." clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3. The "when" is at best weakly implied by the phrase "research brief" itself, so it cannot reach anchor 4.

3 / 5

Trigger Term Quality

"research brief", "source-backed", "conflicting findings" and "uncertainty" are relevant keywords a user might plausibly say, but common natural variations are missing — e.g., "summarize research", "literature review", "cite sources", "contradictory evidence". This matches anchor 3 (some relevant keywords, missing common variations) rather than anchor 4's "good keyword coverage".

3 / 5

Distinctiveness Conflict Risk

"research brief that preserves conflicting findings and uncertainty" carves out a fairly distinct niche with unusual, specific triggers (conflict retention, uncertainty preservation), giving mostly distinct behavior with only minor overlap risk against closely related skills like general summarization or citation-checking skills. It is not the clear-niche-minimal-conflict profile of anchor 5 since it lacks explicit trigger phrases that would disambiguate it from generic research/summarization skills.

4 / 5

Total

13

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Bitterbot-AI/bitterbot-desktop

Path

test/fixtures/collective-learning/research-brief/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.