researcher

Multi-repository analysis and research specialist

Quality

14%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/researcher/SKILL.md

Quality

Content

22%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill reads more like a portfolio of example research outputs than actionable instructions for Claude. It shows what research reports might look like but fails to provide concrete guidance on how to actually conduct multi-repository analysis, what tools or APIs to use, or how to validate research findings. The persona framing and inspirational quote add no value.

Suggestions

Replace example outputs with executable instructions: specify actual GitHub API calls, search queries, or MCP tools Claude should use to perform repository analysis

Add a concrete workflow with validation steps: e.g., '1. Search using X tool, 2. Filter results by Y criteria, 3. Validate findings by Z method'

Remove the persona introduction and closing quote - they consume tokens without adding actionable value

Include actual code snippets or commands rather than placeholders like '[Code snippet with best practices]'

Dimension	Reasoning	Score
Conciseness	The skill contains some unnecessary framing (persona introduction, closing quote) and the examples are illustrative rather than instructional. However, it's not excessively verbose and the content is reasonably organized.	2 / 3
Actionability	The content describes what research outputs look like rather than providing executable guidance. There are no actual commands, code snippets, or concrete steps Claude can follow - just example report formats and placeholder text like '[Code snippet with best practices]'.	1 / 3
Workflow Clarity	While there's a brief 'Search Strategy' list, there are no clear multi-step workflows with validation checkpoints. The skill shows example outputs but doesn't explain how to actually perform the research, what tools to use, or how to validate findings.	1 / 3
Progressive Disclosure	The content is organized into sections (Research Capabilities, Multi-Repo Analysis, etc.) but everything is inline with no references to external files. For a research skill that could benefit from detailed methodology guides, this is a missed opportunity.	2 / 3
	Total	6 / 12 Passed

Description

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is too vague to be useful for skill selection. It fails to specify concrete actions (what kind of analysis? what research outputs?), lacks natural trigger terms users would say, and provides no guidance on when Claude should select this skill. The only distinguishing element is 'multi-repository' but even this isn't paired with actionable context.

Suggestions

Add specific concrete actions like 'Compare code patterns across repositories, identify shared dependencies, analyze cross-repo API usage, find duplicate implementations'

Include a 'Use when...' clause with natural triggers like 'Use when the user asks about multiple repos, wants to compare codebases, needs cross-repository search, or mentions analyzing several projects together'

Add natural keywords users would say: 'multiple repos', 'compare repositories', 'cross-repo', 'codebase comparison', 'monorepo analysis'

Dimension	Reasoning	Score
Specificity	The description uses vague language ('analysis and research specialist') without listing any concrete actions. It doesn't specify what kind of analysis, what research activities, or what outputs are produced.	1 / 3
Completeness	The description only vaguely hints at 'what' (analysis/research across repos) and completely lacks any 'when' guidance or 'Use when...' clause. Both components are very weak.	1 / 3
Trigger Term Quality	The only potentially useful trigger term is 'multi-repository' which is somewhat technical. Missing natural terms users would say like 'compare repos', 'cross-repo search', 'multiple codebases', or specific actions.	1 / 3
Distinctiveness Conflict Risk	'Multi-repository' provides some distinctiveness from single-repo skills, but 'analysis and research' is generic enough to potentially conflict with code analysis, documentation, or general research skills.	2 / 3
	Total	5 / 12 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: TurnaboutHero/oh-my-antigravity
Commit: fab464f

Reviewed: 4 months ago

Table of Contents

Discovery Implementation Validation

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.