CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

commonly

Use a Commonly pod as shared context for coding work, and post concise handoffs or files to teammates through its MCP tools. Load whenever commonly_* MCP tools are available.

Quality

90%

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

93%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 exemplary short instruction skill: token-efficient, highly actionable with exact paths and commands, and clearly sequenced with sensible safety guardrails ('Never paste a token into a pod message, a commit, or this chat'). The only minor gap is the absence of explicit post-action validation or error-recovery steps in the pod workflow.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains what MCP or a pod is, and every sentence carries operational detail (exact paths, file modes, commands), matching 'every token earns its place'.

5 / 5

Actionability

Guidance is fully executable for an instruction-only skill: exact path ('${CLAUDE_PLUGIN_DATA}/token'), mode '0600', exact UI navigation ('Bring your own' → 'Use my own agent' → 'Get my connect command'), commands ('/mcp', '/config', 'commonly agent run <agent-name> --adapter claude'), and named tool calls for every workflow step.

5 / 5

Workflow Clarity

The sequence is clear and ordered (token setup → reconnect → get_started → list_pods → get_context → work → post) with conditionals and a pre-post checkpoint ('Before any pod post, call commonly_get_context'), but there are no explicit verify-success or error-recovery loops after posting, so it sits between anchors 4 and 5.

4 / 5

Progressive Disclosure

The skill is under 50 lines, self-contained with no external references needed, and organized into three clear sections (First connection, Pod workflow, What this plugin does not do), which scores 5 under the simple-skill guideline.

5 / 5

Total

19

/

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 strong description with an explicit what-and-when structure and a highly distinctive, tool-availability-based trigger. Its only weakness is that the action list stops at posting handoffs and files, leaving capabilities covered in the body (reading pod context, @mention handling) unmentioned.

Suggestions

Add one or two more concrete actions from the body, e.g. 'read a pod's latest messages and files for context before replying', to lift specificity from 1-2 actions to several.

Include a natural-language trigger variation users might actually say, such as 'share an update with teammates' or 'message the pod', to broaden trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain ('Commonly pod', 'MCP tools') and 1-2 concrete actions ('post concise handoffs or files to teammates'), but 'use as shared context for coding work' is a purpose statement rather than a discrete action, so coverage is not comprehensive as anchor 4 requires.

3 / 5

Completeness

Clearly answers both 'what' (use a Commonly pod as shared context, post handoffs or files via its MCP tools) and 'when' with an explicit, concrete trigger clause ('Load whenever commonly_* MCP tools are available'), matching the anchor-5 example structure; not capped at 3 since explicit trigger guidance is present.

5 / 5

Trigger Term Quality

Good keyword coverage including natural phrases users would say ('Commonly pod', 'teammates', 'handoffs', 'files') plus the concrete 'commonly_*' tool-pattern trigger; a few natural variations like 'share with the team' or 'message the pod' are missing, keeping it just below anchor 5.

4 / 5

Distinctiveness Conflict Risk

'Commonly pod' and the 'commonly_*' MCP tool pattern form a clear niche with distinct triggers that no generic skill would match, giving minimal conflict risk.

5 / 5

Total

17

/

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

Team-Commonly/commonly

Path

plugins/commonly/skills/commonly/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.