CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mcp-access

Open the GBrain owner dashboard, manage MCP clients and permissions, or connect a native OAuth harness. Distinguishes owner administration from ordinary MCP access.

Quality

79%

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 ./plugin-variants/gbrain-coding/skills/mcp-access/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 strong, dense operational skill body: concrete commands, explicit preview/apply validation for destructive actions, and thorough error-recovery guidance with clearly signaled external references. The main weaknesses are repeated rules across sections and dependence on remote documentation URLs rather than bundled reference files for exact command syntax.

Suggestions

State the unknown-outcome transport rule, the list-failure rule, and the broader-scopes prohibition once (in "When it fails") and reference them from the action sections, trimming the duplicated sentences.

Bundle ADMIN.md (or a command-reference extract) locally alongside the skill so exact command syntax is available without the remote GitHub/raw URL dependency.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence — no explanation of OAuth, PKCE, or MCP fundamentals — with nearly every sentence carrying GBrain-specific operational rules. It falls short of anchor 5 because several rules are stated twice (the unknown-outcome transport rule, "a failed list is not an empty list", and "do not try successively broader OAuth scopes" each appear in both the action sections and "When it fails").

4 / 5

Actionability

Concrete subcommands and flags throughout — `login-link --oauth-request ID`, `mcp grant NAME --client ID --if-version N --dry-run`, `--yes --if-version N`, `--credentials-out PRIVATE_FILE` — make the guidance mostly executable. The `gbrain mcp admin … --url URL` placeholder and deferral of full syntax to the external ADMIN.md leave minor gaps that keep it from anchor 5's copy-paste-ready standard.

4 / 5

Workflow Clarity

Destructive operations carry explicit validation checkpoints: dry-run previews before/after, `--if-version` concurrency guards, apply only after review, `whoami` confirmation afterwards, and verification via an authenticated call from the native harness. Error-recovery feedback loops are thorough — unknown-outcome handling, grant_diagnosis relay, and hidden_tool_content fix paths — matching anchor 5.

5 / 5

Progressive Disclosure

Sections are clearly organized and references are one level deep with stated purpose (ADMIN.md "for the exact commands and recovery table", the hosted guide for installation, DEPLOY.md for the running service, plus a raw-URL fallback). It misses anchor 5 because all references are remote URLs rather than bundled files, and substantial operational detail is inlined in SKILL.md instead of being split out.

4 / 5

Total

17

/

20

Passed

Description

70%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 specific, distinctive description that clearly names concrete owner-administration actions, but it omits when-to-use guidance from the description field itself (delegating that to separate frontmatter triggers) and misses several natural trigger terms. Adding an inline "Use when..." clause covering the register/revoke/invalidate actions would raise both completeness and trigger coverage.

Suggestions

Append an explicit when-clause to the description itself, e.g. "Use when the user asks to open the GBrain/MCP admin panel, register or revoke MCP clients, invalidate MCP tokens, or set up MCP OAuth" — the current description field relies on the separate when_to_use frontmatter for trigger guidance, capping completeness.

Include the full action set (register, invalidate tokens, revoke, delete clients, edit access levels) in the description to close the specificity gap that "manage" only implies and to add the natural trigger terms users say.

Add common user phrasings such as "admin panel" and "MCP admin" as synonyms alongside "owner dashboard" to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

"Open the GBrain owner dashboard, manage MCP clients and permissions, or connect a native OAuth harness" lists three concrete actions. It stops short of comprehensive coverage — token invalidation, client revocation, and deletion are only implied by "manage" — so it fits anchor 4 rather than 5, and exceeds anchor 3's 1-2 actions.

4 / 5

Completeness

The "what" is clear (open the owner dashboard, manage MCP clients/permissions, connect a native OAuth harness), but the description field itself contains no "Use when..." clause or equivalent trigger guidance — that lives in the separate when_to_use/triggers frontmatter fields. Per the guideline, a missing when-clause in the description caps completeness at 3.

3 / 5

Trigger Term Quality

"GBrain owner dashboard", "MCP clients", "permissions", and "OAuth" are phrases a user needing this skill would naturally say, giving good keyword coverage. Common variations like "admin panel", "register", "revoke", and "tokens" are missing, keeping it below anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The description names a specific product (GBrain) and a narrow niche — "Distinguishes owner administration from ordinary MCP access" — with distinct triggers like the owner dashboard and native OAuth harness, so conflict with other skills is minimal.

5 / 5

Total

16

/

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

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

14

/

16

Passed

Repository

garrytan/gbrain

Path

plugin-variants/gbrain-coding/skills/mcp-access/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.