CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/codeclimate-config

Configure Code Climate Quality (now Qlty) for repository-wide quality gates - duplication, complexity, similar-code, exclude_patterns. Covers both legacy `.codeclimate.yml` (Code Climate Velocity / GitHub integration) and the new `.qlty/qlty.toml` per the Qlty platform migration. Use when a repo needs duplication and complexity thresholds enforced on PRs, or when an existing `.codeclimate.yml` must be migrated to Qlty without losing its plugin and exclude settings.

74

Quality

93%

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

Overview
Quality
Evals
Security
Files

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable and well-sequenced with strong validation checkpoints and a useful anti-patterns table. The main weakness is redundancy: the upstream-diff and tests-exclusion rationales are repeated across Step 6, the Verify blocks, the Worked Example, and the Anti-patterns.

Suggestions

Consolidate the `--upstream main` rationale into one place (Step 6) and have the Worked Example and Anti-patterns reference it rather than re-explaining it.

Merge the 'Excluding `**/test/**` is required' note and the Anti-patterns 'Scan tests + production' row into a single statement of the rule to avoid repeating the qa-test-review/qa-code-quality ownership rationale.

Consider trimming the Worked Example to only the parts not already demonstrated in Steps 1-6, since it currently re-narrates the full flow.

DimensionReasoningScore

Conciseness

Code blocks and most prose are lean and executable, but the `--upstream main` rationale, the tests-exclusion rationale, and the Worked Example restate guidance already given in Steps 1-6 and the Anti-patterns table, so it could be tightened.

2 / 3

Actionability

Provides fully executable, copy-paste-ready install commands, complete `.codeclimate.yml` and `qlty.toml` config blocks, and concrete `qlty check/smells/metrics` invocations plus a CI yaml with `QLTY_TOKEN`.

3 / 3

Workflow Clarity

Clear 6-step sequence with two explicit Verify checkpoints and feedback loops (e.g. 'assert a newly introduced duplicate block fails while pre-existing findings stay green'; 'confirm `--upstream main` is set and the base branch is correct, then re-run').

3 / 3

Progressive Disclosure

No bundle files exist; the body is organized into clear titled sections with a one-level-deep References section linking three external docs and no nested references, satisfying the simple-skill allowance.

3 / 3

Total

11

/

12

Passed

Description

100%

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, specific description that clearly states capabilities and gives an explicit 'Use when' trigger covering both adoption and migration scenarios. Voice is third person and there is no vague fluff.

DimensionReasoningScore

Specificity

Names multiple concrete actions: 'Configure... quality gates - duplication, complexity, similar-code, exclude_patterns', covering both legacy `.codeclimate.yml` and new `.qlty/qlty.toml`, plus migration 'without losing its plugin and exclude settings'.

3 / 3

Completeness

Explicitly answers both what (configure quality gates, cover both formats, migration) and when via an explicit 'Use when...' clause giving two trigger scenarios.

3 / 3

Trigger Term Quality

Includes natural phrasing a user adopting the tool would say - 'duplication and complexity thresholds enforced on PRs' and 'migrate... `.codeclimate.yml`' - covering the common request forms for this niche.

3 / 3

Distinctiveness Conflict Risk

Clear niche around Code Climate/Qlty config and migration with distinct triggers (codeclimate.yml, qlty.toml, PR duplication/complexity gating) unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents