CtrlK
BlogDocsLog inGet started
Tessl Logo

research-agent

Authoring playbook for building agents that search, read, and synthesize information into a report. Use this when the user wants an agent to research a topic, summarize sources, compare options, do competitive analysis, monitor news, generate briefs, or pull together a citation-backed report from the web or internal documents.

66

Quality

78%

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 ./packages/editor/src/ee/workspace/skills/research-agent/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.

A highly actionable playbook whose copy-paste system prompt template and worked examples are its main strength. Its weaknesses are redundancy — freshness and citation rules are repeated three times across sections and the final worked example restates completion criteria — and the absence of an explicit, validated step sequence for the authoring workflow itself.

Suggestions

State the freshness/citation rules once inside the system prompt template and reduce the 'Freshness policy' and 'Required behavioral rules' sections to a short enforcement checklist, cutting the repeated statements of the same rules.

Add an explicit numbered authoring workflow (pick identity → check available capabilities → fill template → verify) ending with a verification step that checks the produced prompt against the completion criteria.

Explain or remove the undefined 'from the form snapshot' reference in the worked example's model-selection line, since no form or model snapshot is defined anywhere in the skill.

DimensionReasoningScore

Conciseness

The 60-line system prompt template is the core deliverable and earns its place, but the freshness/citation rules are stated three times ('Freshness policy' section, the template's 'Freshness and source policy', and 'Required behavioral rules'), and the closing worked example restates the completion criteria again. Roughly a quarter of the body is redundant restatement, fitting 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the minor-trim 4 anchor.

3 / 5

Actionability

The body provides a complete, fill-in-the-placeholder system prompt template with an embedded worked example, concrete identity naming patterns, a prioritized capability list, and an end-to-end worked example ('Build me an agent that researches AI startups' → named agent with description, model, tools, and prompt excerpt). For an instruction-only skill this is copy-paste-ready guidance covering the common case, matching the 5 anchor; it is not the 4 anchor because there are no material gaps in the guidance (the undefined 'form snapshot' phrase is peripheral to the main flow).

5 / 5

Workflow Clarity

The components a builder needs are all present and ordered sensibly (identity → freshness policy → template → enforcement rules → capabilities → anti-patterns → example), but the authoring process itself is never sequenced as steps and has no explicit validation checkpoint for the produced prompt — the 'enforce these rules' checklist is implied rather than a verify step. This matches 'steps listed but validation gaps; checkpoints missing or implicit' rather than the 4 anchor's mostly-present checkpoints.

3 / 5

Progressive Disclosure

The body has well-organized sections and no buried or nested references, and the prompt template legitimately belongs inline. However at ~130 lines with no bundle files, the full template and worked example could live in a references/ file to keep SKILL.md lean, a minor organization gap consistent with the 4 anchor; it is not the 5 anchor, which requires content appropriately split across well-signaled files (and the >50-line simple-skill exception does not apply).

4 / 5

Total

15

/

20

Passed

Description

88%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: third-person, concise, with an explicit and concrete 'Use this when...' trigger clause and a rich set of natural trigger phrases. Its only weaknesses are a handful of missing natural synonyms and some breadth in trigger vocabulary that could overlap with directly research-performing skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'search, read, and synthesize information into a report' plus 'research a topic, summarize sources, compare options, do competitive analysis, monitor news, generate briefs' — covering both what the skill produces (agent authoring) and what the output looks like (citation-backed report). Coverage is comprehensive with no significant gaps; it does not fall to 4, which requires minor gaps in coverage.

5 / 5

Completeness

Both parts are explicit and concrete: what — 'Authoring playbook for building agents that search, read, and synthesize information into a report'; when — 'Use this when the user wants an agent to research a topic, summarize sources, compare options...'. This clearly matches the 5 anchor (explicit what AND when with concrete trigger phrases), not the 4 anchor where the when-clause is only adequately specific.

5 / 5

Trigger Term Quality

Good natural-phrase coverage: 'research a topic', 'summarize sources', 'compare options', 'competitive analysis', 'monitor news', 'generate briefs', 'citation-backed report', 'web or internal documents'. A few natural variations users would say are missing (e.g. 'investigate', 'literature review', 'brief me on'), so it fits the 'good keyword coverage; a few natural terms missing' anchor rather than the comprehensive 5.

4 / 5

Distinctiveness Conflict Risk

The 'authoring playbook for building agents' framing carves a clear niche distinct from skills that perform research directly, and trigger phrases like 'competitive analysis, monitor news, citation-backed report' are specific. Minor overlap risk remains with generic research/summarization skills since trigger terms are broad research vocabulary, so it does not reach the minimal-conflict 5 anchor.

4 / 5

Total

18

/

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
mastra-ai/mastra
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.