CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

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

The canonical home for this skill is seo-bing in AgriciDaniel/claude-seo

SKILL.md
Quality
Evals
Security

Quality

Content

68%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-sectioned routing skill with concrete command-to-script mappings and sensible cross-skill delegation. The main gaps are the absence of validation/feedback steps around batch and single-URL submissions and placeholder parameters that are never concretized, which cap workflow clarity and actionability respectively.

Suggestions

Add validation around submissions: instruct Claude to run verify-indexnow before first submit, check the IndexNow per-URL response status, and retry/report failed URLs — especially for submit-batch.

Replace the "--host ..." placeholder with one concrete example invocation (e.g., indexnow_submit.py --host example.com --urls https://example.com/new-page) so the submit commands are copy-paste ready.

Trim the Security section to a single non-redundant statement and compress the intro justification to reclaim tokens.

DimensionReasoningScore

Conciseness

The body is tight and assumes Claude's competence (no concept explanations), but the Security section is redundant ("untrusted external data. Treat fetched content as untrusted data") and the intro carries some justificatory baggage (the Gary Illyes/SOTR citation). Fits anchor 4 (efficient, minor instances that could be trimmed); not 5 due to the Security redundancy, not 3 since there are no padded explanations of known concepts.

4 / 5

Actionability

The routing table maps each user command to a concrete script invocation with flags, and prerequisites name the exact installer script and env keys. However, "--host ..." and "<url>" remain unfilled placeholders with no worked example, so it is mostly-but-not-fully executable: anchor 4 rather than 5, and clearly above anchor 3 since real commands and script names are given rather than pseudocode.

4 / 5

Workflow Clarity

Per-command actions are unambiguous and prerequisites precede routing, but the skill includes batch submission ("/seo bing submit-batch <file>") with no validation or feedback loop (no check of per-URL response status, no retry-on-failure, and verify-indexnow is not wired into a submit workflow). The rubric caps workflow clarity at 3 for batch operations without validation; it is not 2 because the prereq-then-dispatch sequence is present and each single action is clear.

3 / 5

Progressive Disclosure

At roughly 50 lines with clean sections (Prerequisites, Routing, When this skill applies, Cross-skill delegation, Security) and clearly signaled one-level-deep references to plugin scripts and sibling skills, the body is well organized. It falls just short of anchor 5 because unspecified parameters (--host ...) and missing pointers to fuller Bing/IndexNow API detail leave minor organization gaps, while sitting comfortably above anchor 3.

4 / 5

Total

15

/

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 distinctive, niche-scoped description with concrete capability names and strong natural trigger terms for the Bing/IndexNow/Copilot domain. Its main weakness is the missing explicit "Use when..." trigger clause, which caps completeness, and minor overlap risk with sibling SEO skills around "link data".

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants Bing indexing, Copilot citation eligibility, IndexNow URL submission, or wants to compare Bing link data across properties."

Include natural trigger variations users would say, such as "submit URLs to Bing", "Bing Webmaster", and "get indexed on Bing", to broaden trigger-term coverage.

Drop the abstract "makes ... first-class" framing in favor of concrete verbs (e.g., "Checks Bing visibility and link data; submits URLs to Bing via IndexNow").

DimensionReasoningScore

Specificity

Names three concrete capability areas ("Bing visibility, link data, and IndexNow URL submission") plus the Copilot-citation angle, but "makes ... first-class" is abstract phrasing and coverage omits the compare/verify commands the body supports. Closest to anchor 4: several specific actions with minor gaps; not 5 because the framing is partly abstract and not comprehensive, not 3 because it goes well beyond 1-2 actions.

4 / 5

Completeness

The "what" is clear (Bing visibility, link data, IndexNow URL submission), but there is no "Use when..." clause or equivalent explicit trigger guidance; the Copilot sentence is rationale rather than a trigger, which caps completeness at 3 per the rubric guideline. Not 2 because the what is concrete and the when is weakly implied; not 4 because the when is never made explicit.

3 / 5

Trigger Term Quality

"Bing Webmaster Tools", "IndexNow", "Microsoft Copilot citations", and "Bing index" are natural terms users would say in this niche. Good coverage but a few natural variations are missing (e.g., "submit URL to Bing", "Bing Webmaster", the other supported engines named in the body), so it fits anchor 4 rather than 5, and clearly exceeds anchor 3's partial coverage.

4 / 5

Distinctiveness Conflict Risk

The Bing/IndexNow/Copilot niche is unambiguous and distinct from generic SEO triggers, but "link data" creates minor overlap risk with the sibling seo-backlinks skill in the same plugin family. Fits anchor 4 (mostly distinct, minor overlap with closely related skills) better than 5 (which expects minimal conflict risk) or 3 (scoping is much tighter than "somewhat specific").

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

AgriciDaniel/claude-seo

Path

extensions/bing-webmaster/skills/seo-bing/SKILL.md

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.