Name: coderpad
Rating: 64.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

coderpad

CoderPad integration. Manage Pads. Use when the user wants to interact with CoderPad data.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/coderpad/SKILL.md

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.

This is a strong, executable skill body: concrete commands, a clear multi-step connection workflow with validation checkpoints, and good structure. The only gaps are minor verbosity in the overview and a lack of file-splitting for the long action/flag reference material.

Dimension	Reasoning	Score
Conciseness	The body is largely lean command-and-flag documentation that assumes Claude's competence, with only minor over-explanation (e.g. 'CoderPad is a technical interview platform used by recruiters and engineers') that could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready executable commands with flags, --json usage, JSON input examples, and a full popular-actions table covering common cases.	5 / 5
Workflow Clarity	The connection workflow is clearly sequenced with explicit polling, enumerated state outcomes (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), and feedback loops (re-poll after the user completes an action).	5 / 5
Progressive Disclosure	Content is well-organized into clear sections with no nested references, but everything is inlined in one file — the popular-actions table and proxy flags could live in a separate reference file for a tighter SKILL.md.	4 / 5
	Total	18 / 20 Passed

Description

66%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.

The description is third-person, has an explicit 'Use when' trigger, and names a distinct product, so it clears the main bars. Its weakness is thinness — only 'Manage Pads' concretely, missing the richer pad/question/org capabilities the skill supports.

Suggestions

Add 1-2 more concrete actions to the description, e.g. 'Manage Pads and interview questions, retrieve org stats and pad events.'

Broaden trigger terms to include natural user phrasings like 'coding interviews', 'interview pads', or 'CoderPad questions'.

Dimension	Reasoning	Score
Specificity	Names the domain ('CoderPad integration') and one concrete action ('Manage Pads'), but does not enumerate the breadth of capabilities (pads, questions, org stats, proxy) that the skill actually offers.	3 / 5
Completeness	Both 'what' ('CoderPad integration. Manage Pads.') and an explicit 'when' ('Use when the user wants to interact with CoderPad data') are present; the trigger clause could be more specific to score 5.	4 / 5
Trigger Term Quality	Includes relevant keywords ('CoderPad', 'Pads', 'interact with CoderPad data') but misses common natural variations a user might say like 'interview pad', 'coding interview', or 'pads/questions'.	3 / 5
Distinctiveness Conflict Risk	'CoderPad' is a distinct, named product niche with clear triggers and minimal overlap risk with other skills.	5 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/coderpad/SKILL.md
Commit: f484c82

Reviewed: ~12 hours ago

Table of Contents

Discovery Implementation Validation

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.