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.
62
72%
Does it follow best practices?
Impact
—
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 occupies a distinct niche around EmblemAI prompt examples, which are strong points. However, the 'what' portion reads more like a topic list than concrete actions, and some terminology is jargon-heavy rather than using natural user language. The description would benefit from more action-oriented phrasing and broader trigger term coverage.
Suggestions
Rephrase the capability list using concrete action verbs (e.g., 'Provides ready-to-use prompt templates for EmblemAI tasks' instead of 'Curated prompt and usage examples').
Add more natural trigger term variations a user might say, such as 'how to phrase', 'what to ask EmblemAI', 'prompt template', or 'example request'.
| 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 answers both 'what' (curated prompt and usage examples for various EmblemAI tasks, with review-first and trust-boundary-aware principles) and 'when' explicitly ('Use when the user wants example prompts, phrasing guidance, or sample requests for end-user EmblemAI tasks'). The explicit 'Use when...' clause with clear trigger conditions is present. | 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 domain-specific jargon rather than natural terms a user would say. A user might say 'how do I ask EmblemAI to...' or 'show me a prompt for...' which are partially covered but not comprehensively. | 2 / 3 |
Distinctiveness Conflict Risk | The skill is clearly scoped to EmblemAI prompt examples and phrasing guidance, which is a very specific niche. The combination of 'EmblemAI', 'example prompts', 'phrasing guidance', and the specific task domains (NFT discovery, prediction-market analysis) makes it highly 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 functions well as a navigational index to prompt example reference files, with excellent progressive disclosure and clear organization. Its main weakness is that the SKILL.md body itself contains no actual prompt examples — all concrete content is delegated to reference files that weren't provided for evaluation. The Security & Trust Model section and install instructions add some unnecessary verbosity for what is essentially a read-only reference skill.
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 skill is immediately actionable without needing to open reference files.
Remove or significantly shorten the Security & Trust Model section — the key points (read-only reference, confirmation-gated examples) could be conveyed in one sentence in the intro.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary sections like the Security & Trust Model explanation and the Quick Start install step, which add bulk without much value for a prompt-examples reference skill. The Guidance section is lean and useful, but the overall document could be tighter. | 2 / 3 |
Actionability | The skill provides clear pointers to prompt categories and useful guidance rules, but the actual prompt examples are entirely delegated to reference files (which are not provided in the bundle). The SKILL.md itself contains no concrete example prompts — only descriptions of what the reference files contain and general phrasing advice. | 2 / 3 |
Workflow Clarity | This is a simple reference/lookup skill with no multi-step destructive operations. The single workflow (identify task area → consult the relevant reference file → apply guidance rules) is unambiguous. The Guidance section provides clear constraints like 'quote only' and 'request a draft plus explicit confirmation before execution,' which serve as validation checkpoints for the prompt patterns. | 3 / 3 |
Progressive Disclosure | The skill is well-structured as an overview/index pointing to 11 clearly labeled, one-level-deep reference files organized by topic. Each reference is clearly signaled with a descriptive summary and a direct file path. Related skills are also linked. This is textbook progressive disclosure. | 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.
2652244
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.