addsearch
AddSearch integration. Manage data, records, and automate workflows. Use when the user wants to interact with AddSearch data.
52
58%
Does it follow best practices?
Impact
—
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 is present but circular, and the action verbs are too generic to help Claude distinguish this skill from other data management integrations.
Suggestions
Replace generic actions with AddSearch-specific capabilities (e.g., 'Configure site search indexes, manage crawled pages, retrieve search analytics, customize search result rankings').
Expand trigger terms to include natural phrases users would say, such as 'site search', 'search index', 'search results', 'search widget', or 'search analytics'.
Make the 'Use when' clause more specific, e.g., 'Use when the user wants to configure or manage AddSearch site search, update search indexes, view search analytics, or customize search result behavior.'
| 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 circular and vague. The 'what' portion is also weak, listing only generic actions rather than specific capabilities. | 2 / 3 |
Trigger Term Quality | It includes 'AddSearch' as a keyword which is useful for brand-specific queries, but 'data', 'records', and 'workflows' are overly generic terms. It misses natural terms users might say like 'search index', 'site search', 'search results', or 'search configuration'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'AddSearch' as a specific product name provides some distinctiveness, but 'manage data, records, and automate workflows' is a boilerplate pattern that could apply to dozens of integration skills, making it hard to distinguish from other data management or workflow automation skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid integration skill with excellent actionability and workflow clarity—the connection state machine handling is particularly well done with explicit feedback loops. The main weaknesses are minor verbosity (explaining what AddSearch is, a skeletal overview section that adds no value) and a lack of progressive disclosure structure for what is a moderately long document. The content is functional and would guide Claude effectively through AddSearch integration tasks.
Suggestions
Remove the introductory sentence explaining what AddSearch is and the shallow Overview section (Search/Result/Index/etc.) that provides no actionable detail—Claude can infer this from context.
Consider splitting the proxy request reference table and connection state handling details into separate referenced files to improve progressive disclosure for this medium-length skill.
| 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 little value without elaboration. However, the CLI commands and workflow steps are reasonably efficient. | 2 / 3 |
Actionability | The skill provides concrete, copy-paste-ready CLI commands for every step: installation, authentication, connection setup, action discovery, action execution, and proxy requests. The flag reference table for proxy requests is specific and useful. Input/output patterns are clearly shown. | 3 / 3 |
Workflow Clarity | The multi-step connection workflow is clearly sequenced with explicit state checks (READY, BUILDING, CLIENT_ACTION_REQUIRED, error states) and feedback loops (poll until ready, handle client actions, re-check state). The progression from installation → authentication → connection → action discovery → action execution is logical and well-structured with validation checkpoints. | 3 / 3 |
Progressive Disclosure | The content is structured with clear sections and headers, but it's somewhat monolithic for its length. The overview section (Search/Result/Index/Configuration/Account) hints at a structure that is never elaborated on or linked to separate files. No bundle files are provided, and the content could benefit from splitting the proxy reference table and connection state handling into separate references. | 2 / 3 |
Total | 10 / 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
f484c82
- 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.