Name: codacy
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

codacy

Codacy integration. Manage Repositories, Organizations. Use when the user wants to interact with Codacy data.

Quality

65%

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/codacy/SKILL.md

Quality

Content

67%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 highly actionable with concrete CLI commands, a useful actions table, and a clear connection workflow with state-based checkpoints. Its main weaknesses are a padded conceptual intro paragraph and placeholder-laden examples that lack a fully worked end-to-end run.

Suggestions

Trim or remove the opening "Codacy is a code analytics platform..." paragraph and other explanatory asides (e.g., "so you can focus on the integration logic") that restate concepts Claude already knows.

Add one fully worked end-to-end example with concrete values substituted for CONNECTION_ID and actionId so a user can copy-paste a complete flow.

Label the post-connection sections as "Step 2: Search for actions" and "Step 3: Run actions" so the existing "skip to Step 2" reference resolves to an actual header.

Dimension	Reasoning	Score
Conciseness	The bulk is efficient executable commands and tables, but the opening "Codacy is a code analytics platform..." paragraph and prose like "so you can focus on the integration logic rather than auth plumbing" are unnecessary explanations Claude does not need, matching the mostly-efficient-with-some-padding anchor.	3 / 5
Actionability	Concrete copy-paste commands appear throughout (install, login, connection ensure, action list, action run, request) with a flag-options table and a popular-actions table, but examples rely on unsubstituted placeholders like CONNECTION_ID with no fully filled worked example, matching the mostly-executable-with-minor-gaps anchor.	4 / 5
Workflow Clarity	The install-login-connect-search-run sequence is clear with explicit connection-state checkpoints (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a poll-again feedback loop, but "skip to Step 2" references a Step 2 that is never labeled as such, a minor sequencing gap matching the clear-sequence-with-most-checkpoints anchor.	4 / 5
Progressive Disclosure	With no bundle files present, the single ~160-line file is organized into clear sections (Overview, Working with Codacy, Install, Authentication, Connecting, Searching, Popular actions, Running actions, Proxy, Best practices); the popular-actions table is reasonable inline for a CLI skill, matching the good-structure-with-minor-gaps anchor.	4 / 5
	Total	15 / 20 Passed

Description

62%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 clearly identifies the Codacy niche and includes an explicit 'Use when' trigger, but it is generic in its action verbs and lacks synonyms or concrete trigger variations. It is functional but could be sharper.

Suggestions

Replace the generic verb "Manage" with specific actions users perform, e.g., "List and inspect repositories, organizations, commits, pull requests, and code quality issues."

Broaden trigger terms with natural synonyms users say, e.g., "Use when the user wants to check Codacy code quality, review pull request issues, or browse analysis results."

Keep the explicit "Use when..." clause but pair it with concrete objects (issues, branches, security dashboard) so the trigger is specific rather than "interact with Codacy data".

Dimension	Reasoning	Score
Specificity	"Manage Repositories, Organizations" names the Codacy domain plus one to two entity actions, but "Manage" is generic and coverage is not comprehensive, matching the anchor for naming domain and 1-2 concrete actions.	3 / 5
Completeness	It states both what ("Codacy integration. Manage Repositories, Organizations.") and an explicit when ("Use when the user wants to interact with Codacy data"), but the when clause is somewhat generic rather than concrete, matching the anchor for having both with an improvable when.	4 / 5
Trigger Term Quality	Terms like "Codacy", "Repositories", "Organizations", and "interact with Codacy data" are relevant but lack common synonyms or variations users might naturally say, fitting the anchor for some relevant keywords with missing variations.	3 / 5
Distinctiveness Conflict Risk	"Codacy integration" establishes a clear niche with minimal conflict risk, though the generic "Repositories, Organizations" terms create minor overlap with other code-quality skills, matching the mostly-distinct anchor.	4 / 5
	Total	14 / 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/codacy/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.