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.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill advanced-web-ranking72
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.
This description has proper structure with an explicit 'Use when' clause, but suffers from generic action language that doesn't convey what Advanced Web Ranking actually does. The trigger terms are limited to the product name without including natural SEO-related keywords users might use. The vague capabilities ('manage data, records') could apply to almost any integration skill.
Suggestions
Replace generic actions with specific AWR capabilities like 'track keyword rankings, generate SEO reports, monitor SERP positions, analyze competitor rankings'
Add natural trigger terms users would say: 'AWR', 'SEO rankings', 'keyword tracking', 'search rankings', 'SERP data'
Expand the 'Use when' clause to include specific scenarios: 'Use when the user mentions AWR, keyword rankings, SEO tracking, or wants to analyze search engine positions'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Advanced Web Ranking) and mentions general actions ('Manage data, records, and automate workflows'), but these actions are generic and not specific to what Advanced Web Ranking actually does. No concrete capabilities like 'track keyword rankings', 'generate SEO reports', or 'monitor SERP positions' are listed. | 2 / 3 |
Completeness | The description answers both 'what' (manage data, records, automate workflows) and 'when' (when user wants to interact with Advanced Web Ranking data) with an explicit 'Use when' clause. While the content could be more specific, the structure is complete. | 3 / 3 |
Trigger Term Quality | Includes 'Advanced Web Ranking' as a trigger term, but misses natural variations users might say like 'AWR', 'ranking data', 'SEO rankings', 'keyword tracking', or 'SERP monitoring'. The generic terms 'data' and 'records' are too broad to serve as effective triggers. | 2 / 3 |
Distinctiveness Conflict Risk | The specific mention of 'Advanced Web Ranking' provides some distinctiveness, but 'manage data, records, and automate workflows' is extremely generic language that could apply to dozens of integration skills. Without more specific SEO/ranking terminology, it could conflict with other data management or 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 Advanced Web Ranking integration with good structure. However, it includes unnecessary introductory content, lacks validation/error handling in workflows, and could benefit from trimming the overview section. The best practices section is valuable but the skill would be stronger with explicit error recovery steps.
Suggestions
Remove the introductory paragraph explaining what AWR is and who uses it - Claude already knows this context
Add validation checkpoints after connection creation and action runs (e.g., 'Verify connection succeeded by checking output for connectionId')
Add error handling guidance: what to do if connection fails, if action returns an error, or if authentication expires
Trim or remove the bullet-point overview section (Campaign, Keyword, etc.) as it provides minimal actionable value
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., 'SEO professionals and marketing agencies use it to monitor website performance') and the overview section with bullet points adds little value. However, the CLI commands and examples are reasonably efficient. | 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. The proxy request section includes a helpful options table. | 3 / 3 |
Workflow Clarity | Steps are listed for setup and connection but lack validation checkpoints. No error handling or feedback loops are mentioned for failed connections or action runs. The workflow assumes success without recovery guidance. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline in one file. The overview section could be trimmed, and advanced proxy usage could potentially be split out. References to external docs exist but no internal file structure. | 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.