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 this terminology, though this may be intentional for a specialized workflow. The mode-scoping information ('REX mode only — skipped automatically in Concept mode') adds useful operational context.
| 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 for REX talks, explicitly scoped to 'REX mode only — skipped automatically in Concept mode'. The combination of git archaeology + REX talk context makes it very unlikely to conflict with general git or changelog 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 concrete git commands, explicit output formats, and strong validation/safety guardrails. Its main weakness is verbosity — the inline output templates are extensive and the introductory sections have some redundancy. The workflow is clear with good safety constraints (read-only emphasis, cross-referencing, conflict flagging).
Suggestions
Move the three detailed output format templates to a separate FORMATS.md or TEMPLATES.md file and reference it from the main skill to reduce inline bulk.
Consolidate the 'When to Use This Skill' and 'What This Skill Does' sections into the intro paragraph to reduce redundancy.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary sections like 'When to Use This Skill' which largely repeats the intro, and the output format templates are quite verbose with placeholder-heavy markdown that could be more compact. The 'What This Skill Does' numbered list also partially duplicates the workflow described elsewhere. | 2 / 3 |
Actionability | Provides fully executable, copy-paste-ready git commands with proper parameterization. Output formats are concrete with exact markdown table structures. The validation checklist, anti-patterns, and key rules give specific, actionable constraints rather than vague guidance. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced (read summary → git archaeology → changelog analysis → cross-reference → build timeline → write 3 files). Validation is explicit with a checklist, read-only safety constraints are emphasized, and cross-referencing includes a dedicated conflicts/inconsistencies section for error detection. Anti-patterns provide clear guardrails. | 3 / 3 |
Progressive Disclosure | The skill has good structure with clear sections and links to related stages. However, the three large output format templates inline could arguably be split into a separate reference file — they dominate the skill and make it long. The related links at the bottom are well-signaled and one level deep. | 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
4ef3dec
- 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.