CtrlK
BlogDocsLog inGet started
Tessl Logo

configuration-generator

Generate configuration files for applications, services, and infrastructure. Use when: (1) Setting up new projects (package.json, requirements.txt, tsconfig.json), (2) Creating Docker or Kubernetes configurations, (3) Configuring CI/CD pipelines (GitHub Actions, GitLab CI, CircleCI), (4) Setting up web servers (Nginx, Apache), (5) Defining infrastructure as code (Terraform, CloudFormation), (6) Generating linter/formatter configs (ESLint, Prettier, Black). Provides templates and custom-generated configs for diverse tech stacks.

83

1.24x
Quality

76%

Does it follow best practices?

Impact

97%

1.24x

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/configuration-generator/SKILL.md
SKILL.md
Quality
Evals
Security

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 highly actionable with executable examples and a useful decision tree, but it is verbose and over-inlined, duplicating reference-file content and explaining general knowledge. Tighter delegation to the reference files would materially improve it.

Suggestions

Move the full inline examples (package.json, tsconfig, Dockerfile, k8s deployment, GitHub Actions workflow) into the existing reference/asset files and keep only one compact representative snippet per category in SKILL.md.

Cut the Best Practices explanations of environment variables, .gitignore, and secret management, which Claude already knows; retain only the validation command list as a quick reference.

Weave explicit validation checkpoints (e.g., validate -> fix -> re-validate -> deploy) into each Generation Approach so workflows have feedback loops rather than treating validation as a separate section.

DimensionReasoningScore

Conciseness

The ~540-line body inlines extensive material (package.json, tsconfig, Dockerfile, k8s deployment, GitHub Actions workflow, .gitignore, env-var and secret-management basics) that duplicates the reference files and explains concepts Claude already knows, making it noticeably padded.

2 / 5

Actionability

Provides copy-paste-ready, executable examples and concrete validation commands ('docker-compose config', 'kubectl apply --dry-run=client', 'terraform validate', 'yamllint') covering the common configuration cases.

5 / 5

Workflow Clarity

Generation approaches are numbered and a validation section exists, but validation is in a separate Best Practices area rather than woven as explicit checkpoints with feedback loops into the generation workflows, leaving sequence gaps.

3 / 5

Progressive Disclosure

References (app_configs.md, infra_configs.md) and assets are clearly signaled with markdown links, but large blocks of content that belong in those files are inlined in SKILL.md, duplicating rather than delegating the detail.

3 / 5

Total

13

/

20

Passed

Description

96%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, well-structured description with explicit what/when guidance, rich trigger terms, and concrete enumerated scenarios. Its only weakness is a degree of breadth in the project-setup framing that invites minor overlap with adjacent skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across 'Generate configuration files for applications, services, and infrastructure' with specific enumerated outputs (package.json, Docker, Kubernetes, Terraform, CloudFormation, ESLint, Prettier, Black), giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both what ('Generate configuration files... Provides templates and custom-generated configs for diverse tech stacks') and when via a numbered 'Use when:' clause with six concrete trigger scenarios.

5 / 5

Trigger Term Quality

Comprehensive natural trigger terms plus file extensions and tool names ('Setting up new projects', 'package.json', 'requirements.txt', 'tsconfig.json', 'GitHub Actions', 'Terraform', 'ESLint, Prettier, Black'), covering synonyms and concrete artifacts users would mention.

5 / 5

Distinctiveness Conflict Risk

Clear config-generation niche with concrete tool-specific triggers, but 'Setting up new projects' and broad config framing create minor overlap risk with general scaffolding or project-setup skills.

4 / 5

Total

19

/

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 (541 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
ArabelaTso/Skills-4-SE
Reviewed

Table of Contents

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.