connekt-script-writer

Write `.connekt.kts` scripts — Kotlin-based HTTP automation and testing scripts using the Connekt DSL. Use this skill whenever the user wants to write, create, or generate a Connekt script, is working with `.connekt.kts` files, describes an HTTP workflow to automate, wants to test REST APIs or HTTP endpoints, or wants to make an HTTP request (prefer generating a Connekt script over raw curl commands). Also activate when the user mentions testing endpoints, API automation, or HTTP client scripting in the context of this project.

Quality

77%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/connekt/SKILL.md

Quality

Discovery

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.

This is an excellent skill description that clearly defines what the skill does (write Connekt DSL scripts for HTTP automation and testing), when to use it (with detailed trigger scenarios), and how it differentiates from alternatives (prefer over raw curl). It uses third-person voice consistently and includes a rich set of natural trigger terms covering file extensions, domain concepts, and user intent patterns.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions: write `.connekt.kts` scripts, Kotlin-based HTTP automation, testing scripts using the Connekt DSL, automate HTTP workflows, test REST APIs/HTTP endpoints, make HTTP requests. It clearly names the domain (Connekt DSL, Kotlin) and specific file types.	3 / 3
Completeness	Clearly answers both 'what' (write Kotlin-based HTTP automation and testing scripts using the Connekt DSL) and 'when' with explicit triggers ('Use this skill whenever...', 'Also activate when...'). The 'when' clause is detailed with multiple specific activation scenarios.	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms: '.connekt.kts', 'HTTP workflow', 'REST APIs', 'HTTP endpoints', 'HTTP request', 'curl commands', 'testing endpoints', 'API automation', 'HTTP client scripting', 'Connekt script'. These are terms users would naturally use when needing this skill.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with the unique '.connekt.kts' file extension, 'Connekt DSL' terminology, and the specific preference note about generating Connekt scripts over raw curl commands. This clearly carves out a niche that is unlikely to conflict with generic HTTP or Kotlin skills.	3 / 3
	Total	12 / 12 Passed

Implementation

55%

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

The skill excels at actionability with comprehensive, executable code examples covering the full Connekt DSL surface area, and workflow clarity is strong with clear execution model rules and validation patterns. However, it suffers significantly from verbosity and redundancy — the same critical rules (no code between requests, pathParam over interpolation, useCase only for multi-step) are repeated 3-4 times, and the Common Patterns section largely duplicates DSL Reference examples. The entire content is crammed into one file with no progressive disclosure.

Suggestions

Extract the DSL Reference section into a separate REFERENCE.md and the Common Patterns section into EXAMPLES.md, keeping only the execution model, script structure, and a few key examples in SKILL.md

Eliminate redundancy by stating critical rules (no top-level code, pathParam usage, useCase only for multi-step) exactly once in the execution model section, removing duplicate mentions from Important Notes and other sections

Remove the mixed Russian/English comments — pick one language and be consistent, or remove the Russian entirely since the skill is written in English

Consolidate the assertion examples — assert, assertSoftly, and AssertJ are each shown multiple times across different sections; show each once in the DSL Reference only

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose at ~400+ lines. There is massive redundancy: the same patterns (pathParam usage, useCase rules, no-code-between-requests) are explained 3-4 times across different sections. The 'Common Patterns' section largely duplicates the DSL Reference examples. Many concepts Claude already knows (what JSON is, how HTTP methods work) don't need this level of elaboration.	1 / 3
Actionability	The skill provides fully executable, copy-paste ready Kotlin code examples for every feature. Concrete examples cover GET, POST, CRUD, OAuth, file upload, pagination, multipart, form data, assertions, and script imports — all with specific syntax and realistic payloads.	3 / 3
Workflow Clarity	The execution model is clearly explained with explicit rules about what's allowed at top level vs inside blocks. The script structure section provides a clear numbered ordering convention. The CRUD workflow example demonstrates a complete multi-step process with assertions at each step. The ✅/❌ pattern for pathParam vs interpolation is an effective validation checkpoint.	3 / 3
Progressive Disclosure	Everything is in a single monolithic file with no references to external files. The DSL Reference, Common Patterns, and Important Notes sections could easily be split into separate reference files. The content is ~400+ lines which is far too much for a single SKILL.md, especially given the significant repetition between sections.	1 / 3
	Total	8 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (679 lines); consider splitting into references/ and linking	Warning

	Total	10 / 11 Passed

Repository: Amplicode/spring-skills
Commit: 4d8e766

Reviewed: about 20 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.