CtrlK
BlogDocsLog inGet started
Tessl Logo

setup-openseo

Set up OpenSEO in the current AI agent. Use when a user pastes the OpenSEO installation prompt or asks to connect its plugin, MCP, and skills.

69

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 well-structured, mostly efficient setup workflow with strong sequencing, explicit verification, and good error-recovery branching. The weakest dimension is actionability, since the actual install mechanics rely on external guides rather than inline steps.

Suggestions

Inline the highest-value install steps (e.g., the exact MCP-add command for the most common agent) alongside the external guide links so the skill is executable without fetching docs.

Tighten section 6's adaptation rules by merging the redundant "do not include" exclusions into a single concise line.

DimensionReasoningScore

Conciseness

The body is largely lean and action-oriented, but section 6's template-adaptation notes (e.g., "Do not add more sections or a verification checklist", "Omit versions, paths, connection details...") include minor over-explanation that could be trimmed.

4 / 5

Actionability

It provides concrete endpoints (https://app.openseo.so/mcp), specific verification tools (whoami, list_projects), and clear fallback paths; the core install steps are deferred to external guides, a justified gap given agent variability but still a gap.

4 / 5

Workflow Clarity

Six clearly sequenced steps with an explicit validation gate ("Never claim verification before the free reads succeed"), separate tracking of installation/sign-in/verification, and multiple error-recovery branches (plugin unsupported, no OAuth, skills unsupported, reload needed).

5 / 5

Progressive Disclosure

A single well-organized SKILL.md with six clear sections and no bundle files needed; external doc links are well-signaled and one level deep, appropriate for a setup checklist.

5 / 5

Total

18

/

20

Passed

Description

87%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 strong, specific description that clearly states both capability and trigger conditions in a distinct niche. The only mild gap is that the listed actions ("connect plugin, MCP, skills") are slightly generic in verb choice.

DimensionReasoningScore

Specificity

The description names the domain and several concrete sub-actions ("connect its plugin, MCP, and skills"), giving broad coverage with only minor genericness in the verb "connect".

4 / 5

Completeness

It explicitly answers both what ("Set up OpenSEO in the current AI agent") and when ("Use when a user pastes the OpenSEO installation prompt or asks to connect...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger phrases like "OpenSEO installation prompt" and "connect its plugin, MCP, and skills" give good keyword coverage, though synonym/extension coverage is limited by the niche domain.

4 / 5

Distinctiveness Conflict Risk

The OpenSEO niche and specific installation-prompt trigger make it clearly distinct from other skills with minimal conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
every-app/open-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.