CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

75

Quality

94%

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

88%

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

A tight, highly actionable skill body with well-organized progressive disclosure pointing to real bundle files. The main gap is the absence of explicit validation/retry checkpoints in the multi-round research workflow, which limits workflow_clarity to the mid-level anchor.

Suggestions

Add explicit validation checkpoints between rounds (e.g., 'After Round 2, confirm at least one authoritative source was found before proceeding') and a retry/feedback loop for failed web_fetch or sparse search results.

Trim the redundant citation guidance — the rule already appears under Best Practices — and consider whether the full Mermaid examples earn their tokens or could be shortened to one representative snippet.

Clarify the Round 1 path: replace the placeholder '/path/to/skill/scripts/github_api.py' with a relative path or note on resolving it, so the command is truly copy-paste ready.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: no filler explaining what GitHub/Mermaid is, tight tables, and code blocks that each earn their place. Minor redundancy in Best Practices and illustrative Mermaid snippets keeps it just at the lean/efficient anchor rather than padding.

3 / 3

Actionability

Provides copy-paste-ready commands ('python /path/to/skill/scripts/github_api.py <owner> <repo> summary'), an enumerated list of available subcommands, concrete query templates per round, and worked citation examples — fully executable guidance.

3 / 3

Workflow Clarity

The four rounds are clearly sequenced, but there are no explicit validation checkpoints or feedback loops (e.g., verify search results before synthesizing, retry on failed web_fetch) for this multi-round research process, which caps clarity at 2 per the workflow-feedback-loop note.

2 / 3

Progressive Disclosure

The SKILL.md is a concise overview that signals one-level-deep references to real bundle files ('scripts/github_api.py' and 'assets/report_template.md'), both verified to exist, with the bulk of API and template detail correctly split out rather than inlined.

3 / 3

Total

11

/

12

Passed

Description

100%

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, specific description that clearly states both capabilities and explicit trigger conditions, with natural keyword coverage and a distinct niche. Minor improvement possible by mirroring everyday phrasing more closely, but it meets the top anchor on every dimension.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: 'comprehensive analysis, timeline reconstruction, competitive analysis, or in-depth investigation' plus 'structured markdown reports with executive summaries, chronological timelines, metrics analysis, and Mermaid diagrams', matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly answers both what ('Conduct multi-round deep research... Produces structured markdown reports') and when ('Use when users request...', 'Triggers on Github repository URL or open source projects'), matching the clear-what-and-when anchor.

3 / 3

Trigger Term Quality

Includes natural triggers users would say ('comprehensive analysis', 'timeline reconstruction', 'competitive analysis', 'in-depth investigation', 'GitHub repository URL', 'open source projects'); phrasing is slightly formal but coverage is good, just above the level-2 bar.

3 / 3

Distinctiveness Conflict Risk

The GitHub-repo deep-research niche with structured reports and Mermaid diagrams is clearly distinct from general skills, and its URL/open-source triggers are unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
bytedance/deer-flow
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.