Curated prompt and usage examples for research, portfolio review, quote requests, approval-gated drafts, NFT discovery, prediction-market analysis, and assistant workflows. Emphasis is review-first, trust-boundary-aware use of external data, and explicit confirmation before any value-moving action. Use when the user wants example prompts, phrasing guidance, or sample requests for end-user EmblemAI tasks.
78
72%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/emblem-ai-prompt-examples/SKILL.mdQuality
Discovery
75%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description has a clear 'Use when' clause and is well-scoped to a specific niche (EmblemAI prompt examples), making it complete and distinctive. However, the 'what' portion reads more like a topic list than concrete actions, and the trigger terms, while present, lean toward domain jargon rather than natural user language. The description could benefit from more action-oriented phrasing and broader natural-language trigger coverage.
Suggestions
Rephrase the capability list to use concrete action verbs, e.g., 'Provides ready-to-use prompt templates for researching tokens, reviewing portfolios, requesting quotes, discovering NFTs, and analyzing prediction markets via EmblemAI.'
Add more natural trigger term variations in the 'Use when' clause, such as 'how to ask EmblemAI', 'EmblemAI prompt templates', 'what to say to EmblemAI', or 'EmblemAI usage examples'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names several domains (research, portfolio review, quote requests, NFT discovery, prediction-market analysis) and mentions some actions (approval-gated drafts, confirmation before value-moving action), but these read more like a list of topics than concrete actions the skill performs. It's not as vague as 'helps with documents' but doesn't list specific executable actions like 'extract text, fill forms, merge documents.' | 2 / 3 |
Completeness | The description clearly answers both 'what' (curated prompt and usage examples for various EmblemAI tasks with review-first, trust-boundary-aware approach) and 'when' (explicitly states 'Use when the user wants example prompts, phrasing guidance, or sample requests for end-user EmblemAI tasks'). | 3 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'example prompts', 'phrasing guidance', 'sample requests', 'EmblemAI', 'NFT discovery', 'prediction-market analysis', and 'portfolio review'. However, many of these are fairly niche/technical terms, and common user phrasings are partially covered but not comprehensively — a user might say 'how do I ask EmblemAI to...' or 'show me how to use EmblemAI' which aren't explicitly captured. | 2 / 3 |
Distinctiveness Conflict Risk | The description is highly specific to EmblemAI prompt examples and usage patterns, with a clear niche around providing sample prompts for that particular platform. The combination of 'EmblemAI', 'example prompts', 'phrasing guidance', and the specific task domains makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is well-structured as a reference index with strong progressive disclosure and clear navigation to categorized prompt sets. Its main weakness is that the SKILL.md itself contains no concrete prompt examples — all actionable content is deferred to reference files, making the top-level file more of a table of contents than a standalone resource. The security/trust model section and some framing text could be trimmed for better token efficiency.
Suggestions
Include 2-3 concrete example prompts inline in the SKILL.md (e.g., one quote-only swap prompt, one portfolio review prompt) so the file is immediately useful without navigating to references.
Trim the Security & Trust Model section — the fact that this is read-only reference material can be stated in one sentence rather than a multi-paragraph explanation with bullet points.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The security & trust model section is somewhat verbose for what is essentially a read-only reference skill — explaining that it doesn't execute transactions or fetch data is partially redundant. The install step and 'Step 2: Use' examples add some value but the overall content could be tighter. | 2 / 3 |
Actionability | The skill provides guidance on phrasing patterns and links to reference files, but the SKILL.md itself contains no concrete prompt examples — all actual content is deferred to reference files. The 'Guidance' section offers useful but somewhat generic tips without specific before/after examples. | 2 / 3 |
Workflow Clarity | This is a simple reference/lookup skill with no multi-step destructive operations. The structure is clear: install, then ask by task area. The guidance section provides clear constraints (quote-only, review-only, confirmation before execution). For a single-purpose reference skill, this is sufficient. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure — the SKILL.md serves as a clear overview/index with well-labeled, one-level-deep references to specific prompt category files. Each category has a descriptive link and brief summary of what it contains. Navigation is straightforward. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
2e138ef
Table of Contents
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.