addsearch
AddSearch integration. Manage data, records, and automate workflows. Use when the user wants to interact with AddSearch data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill addsearch72
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
67%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 follows the correct structure with a 'Use when...' clause but relies heavily on the product name 'AddSearch' for distinctiveness. The capability descriptions are generic boilerplate ('manage data, records, automate workflows') that don't convey AddSearch-specific functionality like search indexing, query analytics, or search result customization.
Suggestions
Replace generic actions with AddSearch-specific capabilities like 'configure search indexes, manage crawling rules, analyze search queries, customize search results ranking'
Add natural trigger terms users might say: 'site search', 'search indexing', 'search API', 'search configuration', 'search analytics'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (AddSearch) and mentions general actions ('Manage data, records, and automate workflows'), but these actions are generic and not specific to AddSearch's actual capabilities like indexing, search configuration, or analytics. | 2 / 3 |
Completeness | Has explicit 'Use when...' clause that answers when to use it ('when the user wants to interact with AddSearch data'), and describes what it does (manage data, records, automate workflows), meeting the structural requirements. | 3 / 3 |
Trigger Term Quality | Includes 'AddSearch' as a trigger term which users would say, but lacks natural variations or related terms users might use like 'site search', 'search indexing', 'search API', or 'search analytics'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Manage data, records, and automate workflows' is generic language that could apply to many integration skills. Only the 'AddSearch' name provides distinctiveness; the actions described could conflict with other data management or workflow automation skills. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable CLI commands for AddSearch integration via Membrane, with good coverage of common operations. However, it includes some unnecessary explanatory content, lacks validation checkpoints in workflows, and the overview section adds no value. The proxy request documentation is well-structured with a useful options table.
Suggestions
Remove the 'AddSearch Overview' bullet list and opening explanation - Claude already knows what AddSearch is
Add validation steps after connection creation and action runs (e.g., 'Verify connection with: membrane connection list --json | grep CONNECTION_ID')
Clarify the workflow decision tree: check for existing connection first, then create if needed, rather than presenting both options separately
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary explanation (e.g., 'AddSearch is a hosted search solution for websites' is something Claude already knows). The overview section with bullet points adds little value. | 2 / 3 |
Actionability | Provides fully executable CLI commands throughout with clear syntax examples. Commands are copy-paste ready with proper flags and JSON output options documented. | 3 / 3 |
Workflow Clarity | Steps are listed for setup and connection but lack validation checkpoints. No explicit error handling or verification steps after running actions. The workflow for checking existing connections vs creating new ones could be clearer. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the 'AddSearch Overview' bullet list serves no purpose and could be removed. References to external docs exist but the structure could better separate quick-start from advanced proxy usage. | 2 / 3 |
Total | 9 / 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 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.