github-issue-dedupe
Detect duplicate GitHub issues using semantic search and keyword matching. Use when asked to find duplicates, check for similar issues, or set up automated duplicate detection.
Install with Tessl CLI
npx tessl i github:warpdotdev/oz-skills --skill github-issue-dedupe88
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
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.
This is a well-crafted skill description that excels across all dimensions. It provides specific capabilities (semantic search, keyword matching), includes natural trigger terms users would actually say, explicitly states both what it does and when to use it, and carves out a distinct niche around GitHub issue duplicate detection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'semantic search', 'keyword matching', 'find duplicates', 'check for similar issues', 'set up automated duplicate detection'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Detect duplicate GitHub issues using semantic search and keyword matching') and when ('Use when asked to find duplicates, check for similar issues, or set up automated duplicate detection') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'duplicates', 'find duplicates', 'similar issues', 'duplicate detection', 'GitHub issues'. These are terms users naturally use when dealing with this problem. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on GitHub issue duplicate detection. The combination of 'GitHub issues' + 'duplicates' + 'semantic search' creates a distinct trigger profile unlikely to conflict with general search or issue management skills. | 3 / 3 |
Total | 12 / 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 solid, actionable skill with clear workflow steps and excellent concrete examples. The decision criteria for duplicate detection are well-defined with explicit confidence thresholds. Minor improvements could be made in conciseness (trimming example verbosity) and potentially splitting examples into a separate file for better progressive disclosure.
Suggestions
Trim the examples section - the three examples could be condensed by removing redundant formatting patterns already established in the workflow section
Consider moving detailed examples to a separate EXAMPLES.md file and keeping only one brief example inline
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some redundancy. The workflow steps and examples are clear but could be tightened - the examples section is somewhat verbose with formatting that repeats patterns already established. | 2 / 3 |
Actionability | Provides concrete, executable gh commands throughout. The search strategies, comparison criteria, and comment formatting are all specific and copy-paste ready. Examples show exact command sequences. | 3 / 3 |
Workflow Clarity | Clear 4-step sequence with explicit decision criteria. High/low confidence indicators provide validation checkpoints. The 'only comment if high confidence' rule prevents false positives. Examples reinforce the decision-making process. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is inline in a single file. The examples section is extensive and could potentially be split out. For a skill of this length (~100 lines), the structure is acceptable but not optimal. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
87%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 14 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 14 / 16 Passed | |
- 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.