talk-stage2-research
Performs git archaeology, changelog analysis, and builds a verified factual timeline by cross-referencing git history with source material. REX mode only — skipped automatically in Concept mode. Use when building a REX talk and you need verified commit metrics, release timelines, and contributor data from a git repository.
83
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
85%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 is a well-crafted description that clearly defines its scope, lists concrete actions, and includes explicit trigger guidance with a 'Use when...' clause. Its main weakness is that the trigger terms are somewhat niche ('REX talk', 'REX mode') which limits discoverability for users unfamiliar with that terminology, though this may be intentional for a specialized workflow. The mode-specific guard ('REX mode only — skipped automatically in Concept mode') is a nice operational detail that aids in correct skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'git archaeology', 'changelog analysis', 'builds a verified factual timeline', 'cross-referencing git history with source material', 'verified commit metrics, release timelines, and contributor data'. | 3 / 3 |
Completeness | Clearly answers both what ('performs git archaeology, changelog analysis, builds verified factual timeline by cross-referencing git history') and when ('Use when building a REX talk and you need verified commit metrics, release timelines, and contributor data from a git repository'). Includes explicit 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'git', 'changelog', 'commit metrics', 'release timelines', 'contributor data', and 'git repository', but the primary trigger terms are domain-specific ('REX talk', 'REX mode') which most users wouldn't naturally say. Missing common variations like 'git log', 'git blame', 'commit history'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically scoped to REX mode talks, git archaeology for timeline building, and explicitly states it's skipped in Concept mode. The combination of REX-specific context and git history analysis makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill with clear workflows and concrete executable commands. Its main weakness is verbosity — the extensive output format templates inflate the token cost significantly and could be extracted to a reference file. The validation checklist and anti-patterns sections are strong additions that ensure safe, verified execution.
Suggestions
Move the three detailed output format templates to a separate FORMATS.md reference file and link to it, keeping only a brief summary of the three output files in the main skill
Remove the 'When to Use This Skill' and 'What This Skill Does' sections — the intro paragraph and the workflow already convey this information more efficiently
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary sections like 'When to Use This Skill' and 'What This Skill Does' that largely repeat the intro and description. The output format templates are quite verbose with placeholder-heavy markdown tables that could be more compact. However, the git commands section and rules are lean and useful. | 2 / 3 |
Actionability | Provides fully executable, copy-paste-ready git commands with proper parameterization. Output formats are concrete with exact markdown table structures. Input/output file naming conventions are specific. The validation checklist and anti-patterns give clear, actionable constraints. | 3 / 3 |
Workflow Clarity | The 6-step workflow is clearly sequenced (read summary → git archaeology → changelog analysis → cross-reference → build timeline → write files). Validation is explicit with a checklist including read-only verification, source attribution, and conflict flagging. The anti-patterns section serves as an error-prevention mechanism, and the cross-reference conflicts section in the timeline output provides a feedback loop for inconsistencies. | 3 / 3 |
Progressive Disclosure | The skill has clear references to related stages (Stage 1, Stage 3, Orchestrator) with relative links, which is good. However, the three full output format templates are quite lengthy and could be split into a separate reference file. The skill is over 150 lines with most of it being output templates that could be progressively disclosed. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
746adc8
- 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.