advanced-web-ranking
Advanced Web Ranking integration. Manage data, records, and automate workflows. Use when the user wants to interact with Advanced Web Ranking data.
61
52%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/advanced-web-ranking/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 is a generic integration template that fails to convey what Advanced Web Ranking actually does or what specific capabilities the skill provides. The 'what' and 'when' clauses are nearly circular, and the description lacks any domain-specific terminology (SEO, keyword rankings, SERP) that would help Claude correctly select this skill.
Suggestions
Replace generic phrases like 'manage data, records, and automate workflows' with specific AWR capabilities such as 'track keyword rankings, pull SERP data, generate SEO ranking reports, monitor search engine positions'.
Expand the 'Use when...' clause with natural trigger terms like 'SEO rankings', 'keyword tracking', 'rank monitoring', 'SERP positions', 'AWR', or 'search engine ranking data'.
Add domain context so Claude understands this is an SEO tool, e.g., 'Integrates with Advanced Web Ranking (AWR) to retrieve keyword ranking data, monitor SERP positions, and generate SEO performance reports.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without listing any concrete actions specific to Advanced Web Ranking. There are no specific capabilities mentioned such as tracking keyword rankings, generating SEO reports, or monitoring SERP positions. | 1 / 3 |
Completeness | It has a weak 'what' (manage data, records, automate workflows) and a 'when' clause ('Use when the user wants to interact with Advanced Web Ranking data'), but the 'when' is essentially a restatement of the 'what' rather than providing explicit trigger scenarios or use cases. | 2 / 3 |
Trigger Term Quality | It includes 'Advanced Web Ranking' as a keyword which is the product name, but misses natural terms users might say like 'SEO rankings', 'keyword tracking', 'SERP monitoring', 'rank tracking', or 'AWR'. The generic terms 'data' and 'workflows' are too broad to serve as useful triggers. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Advanced Web Ranking' as a specific product name provides some distinctiveness, but the generic phrases 'manage data, records, and automate workflows' could easily overlap with many other integration or data management skills. | 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.
This is a functional integration skill with strong actionability — all CLI commands are concrete and executable. However, it suffers from some unnecessary introductory explanation, a loosely structured workflow without explicit validation checkpoints, and a monolithic layout that could benefit from better progressive disclosure. The entity overview section adds little value and the best practices, while useful, could be more tightly integrated.
Suggestions
Remove the introductory paragraph explaining what AWR is and the entity hierarchy overview — Claude can infer this from context and the API docs link.
Add a numbered end-to-end workflow summary at the top (e.g., 1. Install CLI → 2. Authenticate → 3. Connect → 4. Discover actions → 5. Run) with explicit validation checkpoints after connection and action execution steps.
Include error handling guidance for action runs (e.g., what to do if `membrane action run` fails or returns unexpected output).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content includes some unnecessary explanation (e.g., 'Advanced Web Ranking is a tool for tracking keyword rankings on search engines. SEO professionals and marketing agencies use it...') that Claude already knows. The overview section with the bullet hierarchy adds little value. However, the CLI commands themselves are reasonably lean. | 2 / 3 |
Actionability | The skill provides fully executable, 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 concrete and specific. | 3 / 3 |
Workflow Clarity | The workflow steps are present and sequenced (install → authenticate → connect → discover/create actions → run), but there's no explicit validation or error-handling feedback loop for running actions. The action creation section has a good polling/state-check pattern, but the overall workflow lacks numbered sequencing and explicit checkpoints. | 2 / 3 |
Progressive Disclosure | The content is reasonably structured with clear headers, but it's somewhat monolithic — all content is inline in a single file with no references to separate detailed docs beyond the external API docs link. The overview entity hierarchy section doesn't serve a clear navigational purpose. | 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.