function-class-generator

Generate complete, production-ready functions and classes from formal specifications, design descriptions, type signatures, or natural language requirements. Use this skill when implementing APIs from specifications, creating data structures from schemas, building classes from UML diagrams, generating code from contracts, or translating design documents into code. Supports multiple programming languages and follows language-specific best practices.

Install with Tessl CLI

npx tessl i github:ArabelaTso/Skills-4-SE --skill function-class-generator

What are skills?

Review — 73%

Does it follow best practices?

If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:

npx tessl skill review --optimize ./path/to/skill

Learn more

Validation — 10 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

Discovery

92%

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 a strong skill description that clearly articulates specific capabilities and provides explicit trigger guidance with a 'Use this skill when' clause. The description covers multiple concrete use cases and includes natural trigger terms. The main weakness is potential overlap with other code generation or programming skills, though the focus on formal specifications provides some differentiation.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'Generate complete, production-ready functions and classes', 'implementing APIs from specifications', 'creating data structures from schemas', 'building classes from UML diagrams', 'generating code from contracts', 'translating design documents into code'.	3 / 3
Completeness	Clearly answers both what ('Generate complete, production-ready functions and classes from formal specifications...') AND when ('Use this skill when implementing APIs from specifications, creating data structures from schemas...'). Has explicit 'Use this skill when' clause with multiple trigger scenarios.	3 / 3
Trigger Term Quality	Includes natural keywords users would say: 'specifications', 'type signatures', 'APIs', 'schemas', 'UML diagrams', 'contracts', 'design documents', 'functions', 'classes'. These cover common variations of how users describe code generation tasks.	3 / 3
Distinctiveness Conflict Risk	While it specifies 'from specifications/schemas/UML', code generation is a broad domain that could overlap with general coding skills. The focus on 'formal specifications' and 'design documents' provides some distinction, but 'generating code' could still conflict with other coding-related skills.	2 / 3
	Total	11 / 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 provides excellent actionable guidance with complete, executable code examples and a clear workflow, but is severely bloated with content Claude already knows. The document would benefit greatly from being split into a concise overview with references to detailed pattern files, reducing the main skill to perhaps 100 lines while maintaining the valuable examples in separate documents.

Suggestions

Reduce the main SKILL.md to a concise overview (~50-100 lines) with the core workflow and one representative example, moving detailed patterns to separate files like PATTERNS.md or language-specific files

Remove explanations of concepts Claude already knows: what type signatures are, what SOLID principles mean, basic programming concepts, and obvious best practices

Create separate reference files for language-specific templates (e.g., PYTHON.md, TYPESCRIPT.md) and link to them from the main skill

Consolidate the 'Best Practices' and 'Common Patterns' sections into a brief checklist or remove entirely, as Claude knows these patterns

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~600+ lines with extensive explanations Claude already knows (what type signatures are, basic programming concepts, SOLID principles). The document explains obvious patterns and includes redundant information throughout.	1 / 3
Actionability	Provides fully executable, copy-paste ready code examples across multiple languages (Python, TypeScript, Java concepts). Each pattern includes complete implementations with proper error handling and corresponding test suites.	3 / 3
Workflow Clarity	Clear 5-step workflow (Parse → Design → Generate → Document → Test) with explicit validation steps. Each step has concrete examples showing inputs and outputs, and the workflow includes verification through generated tests.	3 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files. All content is inline including detailed patterns, language templates, and best practices that could be split into separate reference documents for different use cases.	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 (897 lines); consider splitting into references/ and linking	Warning

	Total	10 / 11 Passed

Reviewed: 14 days 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.