addsearch
AddSearch integration. Manage data, records, and automate workflows. Use when the user wants to interact with AddSearch data.
61
52%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/addsearch/SKILL.mdQuality
Discovery
40%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 description follows a generic integration template pattern without providing meaningful detail about what AddSearch is or what specific capabilities the skill offers. The 'Use when' clause exists but is too vague to be useful for skill selection. The description would benefit greatly from explaining AddSearch's domain (site search) and listing concrete actions.
Suggestions
Replace generic phrases like 'manage data, records, and automate workflows' with specific AddSearch actions such as 'index web pages, configure search settings, manage search results, view search analytics'.
Expand the 'Use when' clause with natural trigger terms like 'site search', 'search index', 'search configuration', 'AddSearch API', or 'website search functionality'.
Add a brief explanation of what AddSearch is (e.g., 'a site search service') so Claude can distinguish it from other data management integrations.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without specifying any concrete actions. It doesn't explain what AddSearch is or what specific operations can be performed (e.g., indexing pages, configuring search, managing crawlers). | 1 / 3 |
Completeness | It has a 'Use when' clause, but the trigger condition ('interact with AddSearch data') is essentially just restating the what. The 'what' is also weak—'manage data, records, and automate workflows' is generic and could apply to dozens of integrations. | 2 / 3 |
Trigger Term Quality | It includes 'AddSearch' as a keyword which is useful for direct mentions, but lacks natural terms users might say like 'site search', 'search index', 'search configuration', or 'search analytics'. The generic terms 'data', 'records', and 'workflows' are too broad to serve as effective triggers. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'AddSearch' provides some distinctiveness as a named integration, but 'manage data, records, and automate workflows' is a boilerplate pattern that could conflict with many other integration skills. Without specific AddSearch capabilities, it's hard to distinguish from other data management tools. | 2 / 3 |
Total | 7 / 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.
The skill provides solid, actionable CLI commands for integrating with AddSearch via Membrane, covering the full lifecycle from installation to running actions. Its main weaknesses are some unnecessary introductory text, a hollow overview section that adds no value, and a workflow that could be more explicitly sequenced with validation checkpoints. The content is functional but could be tightened and better structured.
Suggestions
Remove the introductory paragraph explaining what AddSearch is and the empty overview bullet list (Search/Result/Index/etc.) — these waste tokens without adding actionable guidance.
Add a consolidated numbered workflow at the top showing the full sequence (install → auth → connect → discover → run) with explicit validation checkpoints, especially error handling after `action run`.
Either flesh out the Overview section with links to specific sub-sections or action categories, or remove it entirely to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content includes some unnecessary explanation (e.g., 'AddSearch is a hosted search solution for websites. It allows website owners to provide a better search experience for their users.' is something Claude already knows). The overview section listing Search/Result/Index/Configuration/Account adds no actionable value. However, the CLI commands themselves are reasonably lean. | 2 / 3 |
Actionability | The skill provides concrete, copy-paste-ready CLI commands for every step: installation, authentication, connecting, searching actions, creating actions, polling, and running actions with input parameters. Each command is specific and executable. | 3 / 3 |
Workflow Clarity | The workflow steps are present and sequenced (install → authenticate → connect → discover actions → create if needed → run), and the action creation flow includes polling with state checking. However, there's no explicit validation or error recovery for the run step, and the overall flow isn't presented as a numbered sequence with clear checkpoints — it's spread across separate sections. | 2 / 3 |
Progressive Disclosure | The content is structured with headers and sections, but the 'AddSearch Overview' section with bullet points (Search/Result/Index/Configuration/Account) provides no useful navigation or links. The content is somewhat monolithic — the best practices and action creation/running details could benefit from clearer separation or cross-references. The link to official docs is good but underutilized. | 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 | |
- Repository
- membranedev/application-skills
- Commit
56d7336
- 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.