Search markdown knowledge bases, notes, and documentation using QMD. Use when users ask to search notes, find documents, or look up information.
87
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
82%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 solid description with good completeness due to the explicit 'Use when' clause and natural trigger terms. The main weaknesses are limited specificity in describing concrete capabilities beyond 'search' and moderate overlap risk with other search-related skills due to generic trigger phrases.
Suggestions
Add more specific actions like 'query by tags, filter by date, search within specific folders' to improve specificity
Include distinctive terms like 'QMD queries', 'markdown files', or '.md' to reduce conflict risk with generic search skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (markdown knowledge bases, notes, documentation) and one action (search using QMD), but doesn't list multiple concrete actions like indexing, filtering, or specific query capabilities. | 2 / 3 |
Completeness | Clearly answers both what (search markdown knowledge bases, notes, and documentation using QMD) and when (explicit 'Use when' clause with trigger scenarios: search notes, find documents, look up information). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'search notes', 'find documents', 'look up information'. These are common phrases users naturally use when seeking this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | While 'QMD' and 'markdown knowledge bases' provide some specificity, terms like 'search notes' and 'find documents' are generic enough to potentially overlap with other search or document management skills. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that efficiently documents a search tool with excellent actionability through concrete JSON schemas, CLI examples, and query syntax tables. The content is well-structured and appropriately concise. Minor weakness is the lack of guidance on interpreting results or handling edge cases like no matches found.
Suggestions
Add a brief note on interpreting search results (e.g., what score thresholds indicate good matches)
Consider adding a troubleshooting tip for when searches return no results (e.g., broaden query, check collection name)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what markdown is or how search works. Every section delivers actionable information with minimal prose. | 3 / 3 |
Actionability | Provides complete, executable JSON examples for MCP queries, CLI commands, and HTTP API calls. Query syntax tables are copy-paste ready with concrete examples like `"rate limiter"` and `performance -sports`. | 3 / 3 |
Workflow Clarity | The 'Combining Types' table provides good guidance on when to use each approach, but lacks explicit validation steps. No feedback loop for verifying search results or handling empty results. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from status check to MCP tools to CLI to HTTP API to setup. Tables effectively summarize options without requiring external references for this scope. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
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.