CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

incremental-python-programmer

Takes a Python repository and natural language feature description as input, implements the feature with proper code placement, generates comprehensive tests, and ensures all tests pass. Use when Claude needs to: (1) Add new features to existing Python projects, (2) Implement functions, classes, or modules based on requirements, (3) Modify existing code to add functionality, (4) Generate unit and integration tests for new code, (5) Fix failing tests after implementation, (6) Ensure code follows existing patterns and conventions.

78

1.05x
Quality

75%

Does it follow best practices?

Impact

90%

1.05x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/incremental-python-programmer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 content is highly actionable with concrete code and a well-sequenced, validated workflow, but it is bloated with generic best-practice material Claude already knows and keeps too much detail inline rather than delegating to the existing reference files.

Suggestions

Trim or remove generic sections Claude already knows (Testing Best Practices, Best Practices, Code Style basics like snake_case/PascalCase) to recover token budget.

Move Common Scenarios and Troubleshooting into a reference file and keep SKILL.md as a lean overview pointing to implementation-patterns.md and testing-strategies.md.

Make the run-tests validation checkpoint an emphatic gate (e.g., 'Only proceed to documentation once all tests pass') to strengthen the feedback loop.

DimensionReasoningScore

Conciseness

The ~540-line body includes several padded generic sections Claude already knows ('Tests should be independent, fast, deterministic', 'Start with simplest solution', snake_case/PascalCase conventions), making it noticeably verbose beyond 'some' unnecessary explanation.

2 / 5

Actionability

Provides executable, copy-paste-ready code (function/class/modification examples, pytest suites, pytest CLI commands) plus a real analyzer script invocation, with only minor gaps where examples are template-like rather than scenario-specific.

4 / 5

Workflow Clarity

An explicit 8-step sequence with a test-run validation checkpoint and a fix-failing-tests feedback loop plus documentation/final-verification checklists; stops short of 5 because gating language ('only proceed when valid') is implicit rather than emphatic.

4 / 5

Progressive Disclosure

References (implementation-patterns.md, testing-strategies.md) and the analyzer script are real and clearly signaled one level deep, but large generic sections (Common Scenarios, Troubleshooting, Best Practices) are inlined in SKILL.md that would be better split into reference files.

3 / 5

Total

13

/

20

Passed

Description

83%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 that clearly states capabilities and provides an explicit, enumerated 'Use when' trigger list. It is specific to Python incremental development with testing, with only minor gaps in action granularity and trigger-term synonyms.

DimensionReasoningScore

Specificity

Names several concrete actions ('implements the feature with proper code placement, generates comprehensive tests, and ensures all tests pass') but they stay somewhat high-level rather than granular, leaving minor gaps versus the comprehensive anchor.

4 / 5

Completeness

Explicitly answers both what (implement feature, generate tests, ensure pass) and when via a numbered 'Use when Claude needs to: (1)...(6)' clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ('Add new features to existing Python projects', 'Implement functions, classes, or modules', 'Fix failing tests') with good coverage, but lacks synonyms and file extensions like .py that would reach comprehensive.

4 / 5

Distinctiveness Conflict Risk

The Python-repository + incremental-feature + test-generation niche is mostly distinct with only minor overlap risk against general coding skills; not a 5 because 'implement features' is broadly applicable.

4 / 5

Total

17

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (547 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

ArabelaTso/Skills-4-SE

Path

skills/incremental-python-programmer/SKILL.md

Revision

4f38503

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill