Name: code-climate
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

code-climate

Code Climate (Qlty) integration. Manage Repositories, Organizations. Use when the user wants to interact with Code Climate (Qlty) data.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/code-climate/SKILL.md

Quality

Content

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

The body is genuinely actionable with executable Membrane CLI commands and a useful actions table, and the connection workflow includes real validation checkpoints. It loses points for an unnecessary introductory explainer, no confirmation guidance around the destructive delete action, and inlined bulk reference content.

Suggestions

Trim the opening paragraph explaining what Code Climate is — Claude already knows this; lead instead with the integration mechanics.

Add an explicit confirmation/validation checkpoint before destructive actions, e.g. "Before running `delete-repository`, confirm the repository id with the user and verify it is not protected."

Move the 20-row popular-actions table into a `references/actions.md` file and link to it from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The intro paragraph ("Code Climate is a platform that helps software engineering teams improve code quality... It's used by developers, QA engineers, and engineering managers") explains concepts Claude already knows, but the rest is mostly efficient concrete commands.	3 / 5
Actionability	It provides copy-paste-ready CLI commands throughout (install, login, connection ensure, action list/run, request) plus a table of specific action keys, with only minor gaps such as the generic `--input '{"key": "value"}'` example and no full end-to-end worked example.	4 / 5
Workflow Clarity	The connection flow has good validation checkpoints (poll until READY, handle CLIENT_ACTION_REQUIRED, check error fields), but the skill exposes destructive operations ("delete-repository") with no confirmation/verification guidance, so the destructive-ops cap applies and numbering is loose ("Step 2" is referenced but not labeled).	3 / 5
Progressive Disclosure	There are no bundle files; all content is inline with decent section headers, but the 20-row popular-actions table is bulk reference content inlined in SKILL.md that would be better split into a separate reference file.	3 / 5
	Total	13 / 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.

The description is concise, third-person, and includes an explicit "Use when..." trigger with both platform synonyms, which is solid. Its main weakness is the generic verb "Manage" and a "when" clause that could name more concrete triggering phrases.

Suggestions

Replace the generic "Manage" with concrete actions, e.g. "List repositories and organizations, retrieve code quality ratings and test coverage reports, add or delete repositories."

Sharpen the "when" clause with natural triggers, e.g. "Use when the user wants to check code quality ratings, review test coverage, or manage Code Climate/Qlty repositories and organizations."

Add common user-facing synonyms ("code quality", "test coverage", "snapshots", "issues") to broaden trigger term coverage.

Dimension	Reasoning	Score
Specificity	"Manage Repositories, Organizations" names the domain and two concrete objects, but the verb "Manage" is generic rather than a specific action, so it sits at the named-domain/1-2-concrete-actions level rather than comprehensive coverage.	3 / 5
Completeness	It has a clear "what" (Code Climate integration, manage repositories/organizations) and an explicit "Use when..." clause, but the "when" ("interact with Code Climate (Qlty) data") is generic rather than a concrete trigger phrase.	4 / 5
Trigger Term Quality	It includes both platform synonyms ("Code Climate" and "Qlty") plus "Repositories" and "Organizations", giving good keyword coverage, though natural terms like "code quality", "test coverage", or "ratings" are missing.	4 / 5
Distinctiveness Conflict Risk	The named "Code Climate (Qlty)" platform gives it a clear niche with distinct triggers, but "Repositories/Organizations" terminology has minor overlap risk with related dev-platform skills like GitHub.	4 / 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/code-climate/SKILL.md
Commit: f484c82

Reviewed: ~14 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.