CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

87%

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

88%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 tightly written, highly actionable setup runbook: it sequences the full installation workflow with explicit verification gates, agent-specific branch handling, and a bounded output template. Weaknesses are minor — some repetition of the hosted-only caveat and one overloaded bullet that hurts scannability more than correctness.

DimensionReasoningScore

Conciseness

The body is dense, imperative, and free of concept explanations Claude already knows, but has minor trim opportunities: "The plugin connects only to hosted OpenSEO" is repeated across sections 2, 3, and 4, and the Claude Cowork bullet in section 3 is an overstuffed run-on packing paid/Free/self-hosted branches into one paragraph. Efficient overall — not 3, since no section is padded or unnecessary.

4 / 5

Actionability

Guidance is fully concrete for an instruction-only skill: exact URLs ("https://app.openseo.so/mcp", the GitHub marketplace repo), exact UI paths ("Customize → Plugins → + or Add → Add marketplace → Add from a repository"), exact verification calls ("run whoami and list_projects"), and a word-bounded handoff template. Specific steps cover the common agent cases; the few deferrals to official guides are clearly labeled external references, not vagueness.

5 / 5

Workflow Clarity

A clearly numbered 1–7 sequence (check → install → sign in → reload/verify → handoff) with explicit validation checkpoints and feedback loops: "Never claim verification before the free reads succeed", "Track installation, sign-in, and verification separately", plus recovery branches ("If list_projects returns no projects... create a project", "If a reload needs my action, give the instructions rather than repeatedly retrying"). This matches the anchor-5 pattern of sequence + validation + error recovery.

5 / 5

Progressive Disclosure

Good structure with clear numbered sections and clearly labeled one-level-deep external references ([plugin guide], [MCP guide], [ChatGPT setup guide], [public skills]). Not 5: at ~78 lines with no bundle files, some inlined per-agent branches (the Cowork bullet, the ChatGPT custom-connection paragraph) and the long handoff-adaptation rules would benefit from being split out or tightened into subsections.

4 / 5

Total

18

/

20

Passed

Description

82%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 concise, well-formed description that clearly states what the skill does and gives explicit, natural trigger conditions tied to the named product. Its only weakness is that the capability list is thin — the specific setup actions (plugin install, MCP connection, skills, sign-in, verification) are implied via the trigger clause rather than stated.

DimensionReasoningScore

Specificity

"Set up OpenSEO in the current AI agent" names the domain and one concrete action, but the components it touches ("plugin, MCP, and skills") appear only in the trigger clause rather than as stated capabilities like install plugin, add MCP connector, sign in, verify. It matches 'names domain and 1-2 concrete actions, but not comprehensive' — not 4, which requires several specific actions listed.

3 / 5

Completeness

Explicitly answers both parts: what — "Set up OpenSEO in the current AI agent"; when — "Use when a user pastes the OpenSEO installation prompt or asks to connect its plugin, MCP, and skills", with concrete trigger phrases. This mirrors the anchor-5 example structure; 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

"pastes the OpenSEO installation prompt or asks to connect its plugin, MCP, and skills" gives natural, likely-user phrasing with good coverage (installation prompt, connect, plugin, MCP, skills). Not 5 because common variations like 'install OpenSEO', 'add OpenSEO', or 'set it up' are absent.

4 / 5

Distinctiveness Conflict Risk

The niche is a named product (OpenSEO) with product-specific triggers ("OpenSEO installation prompt", "its plugin, MCP, and skills"), so it is clearly distinguishable and unlikely to fire for unrelated skills. No overlap risk beyond the anchor-5 threshold.

5 / 5

Total

17

/

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.

Validation — 14 / 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

Path

.agents/skills/setup-openseo/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.