tracking-token-launches
Track new token launches across DEXes with risk analysis and contract verification. Use when discovering new token launches, monitoring IDOs, or analyzing token contracts. Trigger with phrases like "track launches", "find new tokens", "new pairs on uniswap", "token risk analysis", or "monitor IDOs".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill tracking-token-launches95
Does it follow best practices?
Validation for skill structure
Discovery
89%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 with strong trigger term coverage and explicit usage guidance. The main weakness is that the capabilities could be more specific about what concrete actions are performed (e.g., what risk factors are checked, what contract verification entails). Overall, it effectively communicates when to use this skill and distinguishes itself from related crypto skills.
Suggestions
Expand specificity by listing concrete actions like 'checks liquidity locks, honeypot detection, ownership renouncement' or similar specific risk analysis steps
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (DEX token launches) and mentions some actions (track, risk analysis, contract verification), but doesn't list comprehensive concrete actions like what specific risk factors are analyzed or what verification steps are performed. | 2 / 3 |
Completeness | Clearly answers both what (track token launches, risk analysis, contract verification) and when (explicit 'Use when...' clause with triggers, plus 'Trigger with phrases like...' providing additional guidance). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'track launches', 'find new tokens', 'new pairs on uniswap', 'token risk analysis', 'monitor IDOs' - these are realistic phrases crypto users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche focused on new token launches on DEXes with distinct triggers like 'IDOs', 'new pairs on uniswap', 'token risk analysis' - unlikely to conflict with general crypto or trading skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
100%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-crafted skill that efficiently documents a token launch tracking tool. It excels at providing concrete, executable commands with clear options, maintains excellent structure through tables and organized sections, and appropriately delegates detailed examples and error handling to reference files. The workflow guides users through a logical progression from discovery to risk analysis.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting commands, options, and tables without explaining basic concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides fully executable bash commands with concrete examples, specific addresses, and clear option flags. Commands are copy-paste ready with real-world usage patterns demonstrated. | 3 / 3 |
Workflow Clarity | The Instructions section provides a clear numbered sequence for the typical workflow: check launches → get details → analyze risk → view summary → export. The risk analysis step is appropriately positioned before interaction. | 3 / 3 |
Progressive Disclosure | Well-structured with clear overview, then commands, then detailed instructions. Appropriately references external files (errors.md, examples.md) for comprehensive details while keeping the main skill focused. One-level-deep references are clearly signaled. | 3 / 3 |
Total | 12 / 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 — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 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.