Advanced Web Ranking integration. Manage data, records, and automate workflows. Use when the user wants to interact with Advanced Web Ranking 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/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.
The description relies heavily on the product name 'Advanced Web Ranking' for differentiation but fails to describe any concrete, domain-specific capabilities. The generic language around data management and workflow automation provides almost no useful information for skill selection. It needs specific actions tied to what Advanced Web Ranking actually does (e.g., SEO rank tracking, keyword monitoring) and more natural trigger terms.
Suggestions
Replace generic phrases like 'manage data, records, and automate workflows' with specific AWR capabilities such as 'track keyword rankings, monitor SERP positions, generate SEO ranking reports, manage keyword groups'.
Add natural trigger terms users would say, such as 'SEO rankings', 'keyword tracking', 'SERP monitoring', 'rank tracking', 'AWR', or 'search engine rankings'.
Expand the 'Use when' clause with concrete scenarios, e.g., 'Use when the user asks about SEO keyword rankings, wants to pull AWR reports, track search engine positions, or automate rank monitoring workflows.'
| 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 relevant, but misses natural terms users might say like 'SEO rankings', 'keyword tracking', 'SERP monitoring', 'rank tracking', or 'AWR'. The generic terms 'data', 'records', 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
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 functional, actionable skill with clear executable commands and a well-structured connection workflow. Its main weaknesses are moderate verbosity (generic Membrane boilerplate and unnecessary introductory context about AWR) and lack of progressive disclosure—everything is in one file when some content could be split. The AWR-specific content is thin; most of the skill is generic Membrane CLI usage.
Suggestions
Remove the introductory paragraph explaining what AWR is—Claude already knows this and it wastes tokens.
Consider extracting the generic Membrane CLI setup/authentication/proxy sections into a shared reference file, keeping only AWR-specific guidance inline.
Add AWR-specific action examples (e.g., fetching rankings for a keyword, listing campaigns) to make the skill more actionable for its stated domain.
| 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...') and the overview section listing Campaign/Keyword/Competitor etc. adds little value. The Membrane CLI instructions are reasonably efficient but could be tightened—much of this is generic Membrane boilerplate not specific to AWR. | 2 / 3 |
Actionability | The skill provides concrete, executable CLI commands for every step: installation, authentication, connection setup, action discovery, action execution, and proxy requests. Commands are copy-paste ready with clear parameter placeholders and a useful flags reference table. | 3 / 3 |
Workflow Clarity | The multi-step connection workflow is clearly sequenced with explicit state checks (READY, BUILDING, CLIENT_ACTION_REQUIRED, errors), polling instructions, and conditional branching. The flow from install → authenticate → connect → discover actions → run actions is well-structured with validation at each stage. | 3 / 3 |
Progressive Disclosure | The content is a single monolithic file with no references to supporting files, despite being long enough (~150 lines) that sections like proxy request details or the connection state machine could be split out. The structure within the file is reasonable with clear headings, but there's no progressive disclosure via external 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 | |
f484c82
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.