CtrlK
BlogDocsLog inGet started
Tessl Logo

seo-bing

Bing Webmaster Tools + IndexNow extension. Microsoft Copilot citations are fed by the Bing index; this skill makes Bing visibility, link data, and IndexNow URL submission first-class.

60

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./extensions/bing-webmaster/skills/seo-bing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A compact, well-structured routing skill with concrete commands and clean sectioning. Its main gaps are the elided IndexNow host/key arguments and the absence of any validation or verification step for the batch URL submission workflow.

Suggestions

After the submit/submit-batch routes, add an explicit validation step such as 'After submitting, run /seo bing verify-indexnow and re-submit any URLs reported failed' to create a feedback loop for the batch operation.

Replace the elided '--host ...' in the IndexNow routing rows with the concrete flag usage (e.g. '--host <site-host> --key ${INDEXNOW_KEY}') so the commands are copy-paste ready.

Trim the time-sensitive citation ('per Gary Illyes, multiple SOTR episodes 2024-2025') to a plain statement like 'Google does not support IndexNow'.

DimensionReasoningScore

Conciseness

The body is a lean routing table plus short sections; almost every token earns its place. It is not a 5 due to minor over-explanation and time-sensitive trivia: 'per Gary Illyes, multiple SOTR episodes 2024-2025' is unverifiable citation padding, and 'which pulls from the Bing index' repeats information already in the description. Well above the 3 anchor, which requires noticeably unnecessary explanation.

4 / 5

Actionability

The Routing table gives concrete, mostly executable invocations like '"${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run bing_webmaster.py links <url>' plus concrete prerequisites ('Run extensions/bing-webmaster/install.sh or install.ps1'). Not a 5: the IndexNow rows elide the host/key details with '--host ...', leaving a gap the reader must fill in; still more concrete and complete than the 3 anchor's missing key details.

4 / 5

Workflow Clarity

The routing action itself is unambiguous, but the skill includes a batch operation — '/seo bing submit-batch <file>' — with no validation or verification step in its workflow (no check of submission output, no instruction to run the provided verify-indexnow route after submitting, no guidance on handling failed URLs). Per the batch-operation cap, workflow clarity cannot exceed 3. Not a 2: routing commands are clearly sequenced per command, not 'poorly defined'.

3 / 5

Progressive Disclosure

The body is under 50 lines with well-organized sections (Prerequisites, Routing, When this skill applies, Cross-skill delegation) and no inlined content that belongs in separate files, so the simple-skill exception applies. Script paths are clearly routed through the plugin root table; nothing is buried or nested.

5 / 5

Total

16

/

20

Passed

Description

66%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A focused, domain-specific description with good natural keywords, but it answers only 'what' and never 'when'. Adding an explicit 'Use when...' clause would also lift completeness and reinforce distinctiveness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants their site indexed by Bing, wants Microsoft Copilot citation eligibility, or asks to submit URLs via IndexNow.'

Enumerate the concrete operations more comprehensively (fetch Bing link data, compare two properties, submit single URLs or batches, verify IndexNow setup) instead of the claim-style 'makes ... first-class'.

Include one distinguishing phrase against sibling skills (e.g. 'non-Google search engines only') to reduce overlap with generic backlink/SEO skills.

DimensionReasoningScore

Specificity

The description names concrete capabilities — 'Bing visibility, link data, and IndexNow URL submission' — anchored to a specific domain (Bing Webmaster Tools + IndexNow). It falls below the 5 anchor because coverage is not comprehensive (no mention of comparing properties or verifying submissions) and 'makes ... first-class' is a claim rather than an explicit action; it is above the 3 anchor because it lists three specific capabilities, not just 1-2.

4 / 5

Completeness

The 'what' is clear ('this skill makes Bing visibility, link data, and IndexNow URL submission first-class'), but there is no 'Use when...' clause or equivalent explicit trigger guidance anywhere in the description, which caps completeness at 3 per the judging guidelines. It is not a 4 because the 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Natural terms users would say are present: 'Bing Webmaster Tools', 'IndexNow', 'Microsoft Copilot', 'URL submission', 'Bing index'. Not a 5 because common variations like 'get indexed on Bing', 'submit URLs to search engines', or 'Bing Webmaster Tools API' phrasings are missing; well above a 3, which would have only domain keywords without natural search-intent phrasing.

4 / 5

Distinctiveness Conflict Risk

A clear niche is stated — Bing/non-Google indexing and 'Microsoft Copilot citations are fed by the Bing index' — making confusion with Google-SEO skills unlikely. Not a 5: 'link data' overlaps with generic backlink/SEO skills and the description does not name distinct trigger phrasing to fully separate it; clearly more distinct than the 3 anchor's 'somewhat specific but could still overlap'.

4 / 5

Total

15

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
AgriciDaniel/claude-seo
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.