CtrlK
BlogDocsLog inGet started
Tessl Logo

adding-mcp-store-servers

Add a third-party MCP server (Linear, Notion, GitHub, ...) to the PostHog MCP store catalog. Use when asked to "add X to the MCP store", expand the MCP server marketplace, or fix a broken catalog entry. Covers finding the vendor's remote MCP endpoint, probing it (handshake, OAuth discovery, DCR), authoring the catalog entry in products/mcp_store/backend/catalog.py, verification tiers, and the operator handoff for servers without Dynamic Client Registration.

73

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

—

The risk profile of this skill

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.

An actionable, well-sequenced skill body with strong validation checkpoints and a concrete operator handoff. It is lean but a couple of dense sections and the absence of bundle-file references keep conciseness and progressive disclosure just short of the top anchor.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's competence — it never explains what MCP or OAuth is — but a few dense probe-verdict bullets could be slightly tightened, keeping it just below the top anchor.

4 / 5

Actionability

Fully executable: concrete commands ('DEBUG=1 python manage.py probe_mcp_server ...', 'hogli test ...'), precise catalog field guidance, and a copy-paste operator checklist cover the common cases.

5 / 5

Workflow Clarity

A clearly sequenced 6-step workflow with an embedded probe-verdict decision tree, explicit validation ('test_catalog_entries_are_valid'), verification tiers, and a feedback loop (probe failure → re-research).

5 / 5

Progressive Disclosure

Well-organized sections (Read first, Workflow, Operator checklist, What not to do) with clearly signaled one-level-deep references to repo files; no bundle files exist, so structure is internal, leaving minor organization headroom.

4 / 5

Total

18

/

20

Passed

Description

92%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 description: third-person voice, concrete capabilities, explicit 'Use when' triggers, and a well-scoped niche. Trigger-term coverage is good but could add a couple more natural synonyms to reach the top anchor.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'finding the vendor's remote MCP endpoint, probing it (handshake, OAuth discovery, DCR), authoring the catalog entry', verification tiers, and the operator handoff — giving comprehensive coverage rather than vague language.

5 / 5

Completeness

Explicitly answers both what (add a third-party MCP server to the catalog, covering five sub-tasks) and when ('Use when asked to...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural triggers like 'add X to the MCP store', 'expand the MCP server marketplace', and 'fix a broken catalog entry' match what users would say, plus named vendors (Linear, Notion, GitHub); a few common synonyms are absent so it is not a full 5.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (PostHog MCP store catalog) with distinct triggers, making conflict with unrelated skills minimal.

5 / 5

Total

19

/

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
PostHog/posthog
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.