CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

github-deep-research

Conduct multi-round deep research on any GitHub Repo. Use when users request comprehensive analysis, timeline reconstruction, competitive analysis, or in-depth investigation of GitHub. Produces structured markdown reports with executive summaries, chronological timelines, metrics analysis, and Mermaid diagrams. Triggers on Github repository URL or open source projects.

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-structured, actionable skill body: commands are verified against the real script, references are genuine and one level deep, and research methodology is concrete. It falls short of excellent on redundancy (rounds listed twice, template content duplicated inline) and on formalizing verification steps into explicit workflow checkpoints.

Suggestions

Collapse the 'Research Workflow' round list into the 'Research Rounds' section to remove the duplicated four-round enumeration.

Replace the three full Mermaid code blocks with a one-line note pointing to diagram templates in assets/report_template.md, since the template already drives report structure.

Embed validation as explicit steps in the workflow (e.g., 'If tree output is truncated, re-run tree on affected subdirectories before continuing') instead of listing them as footnotes under the command table.

DimensionReasoningScore

Conciseness

The body is dense with no explanations of concepts Claude already knows, but the four research rounds are listed twice (the terse 'Research Workflow' list followed by the detailed 'Research Rounds' section) and three full Mermaid syntax blocks add length that could be trimmed. Not 5 because of this redundancy; not 3 because padding is minor.

4 / 5

Actionability

Provides copy-paste-ready script commands that exactly match the actual CLI (verified against scripts/github_api.py), concrete query templates per round, a confidence rubric, and good/bad citation examples. Not 5 because rounds 2-4 remain high-level bullet directives without concrete example queries or web_fetch invocation patterns.

4 / 5

Workflow Clarity

The four-round sequence is clearly ordered with verification guidance present (truncated-tree recovery instructions, 'Verify dates from commits/PRs', 'Triangulate claims - 2+ independent sources'). Not 5 because these checkpoints are scattered across sections rather than embedded as explicit validate-and-branch steps in the workflow itself.

4 / 5

Progressive Disclosure

Both bundle references (scripts/github_api.py, assets/report_template.md) are real, one level deep, and clearly signaled, and the script's behavior notes match the actual code. Not 5 because the nine-item Report Structure section duplicates the template asset and full Mermaid syntax examples are inlined where the template/asset could carry them.

4 / 5

Total

16

/

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 that clearly states capabilities, output artifacts, and explicit 'Use when' triggers in third person. Keyword coverage is good but lacks synonyms and variations, and the broad 'open source projects' trigger slightly raises conflict risk with general research skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions on both the research side ('timeline reconstruction', 'competitive analysis', 'in-depth investigation') and the output side ('executive summaries, chronological timelines, metrics analysis, and Mermaid diagrams'), giving comprehensive coverage rather than minor gaps.

5 / 5

Completeness

Explicitly answers both what ('Conduct multi-round deep research... Produces structured markdown reports...') and when ('Use when users request comprehensive analysis, timeline reconstruction, competitive analysis, or in-depth investigation') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Includes natural phrases users would say like 'comprehensive analysis', 'timeline reconstruction', 'competitive analysis', and 'GitHub repository URL', but misses common variations such as 'deep dive', 'repo analysis', or 'investigate this repository'. Not 3 because the terms present are relevant and natural rather than generic.

4 / 5

Distinctiveness Conflict Risk

The GitHub-repo deep-research niche is mostly distinct with clear triggers, but 'Triggers on Github repository URL or open source projects' is broad and creates minor overlap risk with general web-research or code-analysis skills.

4 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

bytedance/deer-flow

Path

skills/public/github-deep-research/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.