Execute this skill allows AI assistant to construct and configure neural network architectures using the neural-network-builder plugin. it should be used when the user requests the creation of a new neural network, modification of an existing one, or assistance... Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
21
3%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/ai-ml/neural-network-builder/skills/building-neural-networks/SKILL.mdQuality
Discovery
7%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 description is extremely weak, appearing to be a template or auto-generated placeholder rather than a thoughtfully crafted skill description. It uses first-person framing ('allows AI assistant'), trails off with ellipsis, and contains entirely generic placeholder text for trigger guidance ('Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.'). It fails to provide actionable information for skill selection.
Suggestions
Replace the placeholder 'Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.' with explicit trigger guidance, e.g., 'Use when the user asks to build, design, or modify a neural network, mentions layers, architectures, or deep learning model construction.'
Complete the truncated description and list specific concrete actions, e.g., 'Constructs neural network architectures by adding layers (dense, convolutional, recurrent), configuring activation functions, setting optimizers, and defining input/output shapes using the neural-network-builder plugin.'
Remove first-person framing ('allows AI assistant') and rewrite in third person, e.g., 'Builds and configures neural network architectures...'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | While it mentions 'construct and configure neural network architectures' and references a plugin name, the description trails off with '...' and the actual capabilities are vague. It doesn't list specific concrete actions like 'add layers, set activation functions, configure optimizers'. | 1 / 3 |
Completeness | The 'what' is partially stated but truncated with '...', and the 'when' clause is entirely placeholder text ('Use when appropriate context detected') with no real guidance. Both halves are weak or missing. | 1 / 3 |
Trigger Term Quality | The description ends with the generic filler 'Trigger with relevant phrases based on skill purpose' which provides zero actual trigger terms. It lacks natural keywords users would say like 'neural network', 'deep learning', 'model architecture', 'layers', 'training', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'neural-network-builder plugin' and 'neural network architectures' does carve out a somewhat specific domain, but the vague trailing text and lack of concrete triggers could cause overlap with general ML/AI coding skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is almost entirely generic boilerplate with no actionable content. It never shows the actual syntax for the `build-nn` command, provides no executable code examples, no configuration schemas, and no concrete parameter specifications. Every section reads like a template placeholder rather than genuine instructional content for building neural networks.
Suggestions
Add the actual `build-nn` command syntax with complete, executable examples showing real configuration parameters (layer types, dimensions, activation functions, etc.)
Replace the abstract 'How It Works' narrative with a concrete step-by-step workflow including validation checkpoints, e.g., showing the exact command to run and how to verify the output
Remove generic sections like 'When to Use This Skill', 'Integration', 'Prerequisites', and the boilerplate 'Instructions' — these waste tokens on information Claude can infer
Provide at least one complete end-to-end example with actual input configuration and expected output, rather than describing what the skill 'will do' in abstract terms
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive explanation of concepts Claude already knows. Sections like 'Overview', 'How It Works', 'When to Use This Skill', 'Best Practices', and 'Integration' are padded with generic descriptions that add no actionable value. The 'Instructions' section is entirely generic boilerplate ('Invoke this skill when the trigger conditions are met'). | 1 / 3 |
Actionability | No concrete code, commands, or executable examples anywhere. The examples describe what the skill 'will do' in abstract terms but never show actual configuration syntax, command invocations, or output formats. References to `build-nn` command are never accompanied by actual usage syntax or parameter specifications. | 1 / 3 |
Workflow Clarity | The workflow steps ('Analyzing Requirements', 'Generating Configuration', 'Executing Build') are abstract descriptions of intent rather than actionable sequences. No validation checkpoints, no error recovery loops, no concrete commands or verification steps are provided. The 'Instructions' section is entirely generic placeholder text. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files and no bundle files to support it. Content is poorly organized with multiple sections that repeat similar vague information. The 'Resources' section lists 'Project documentation' and 'Related skills and commands' without any actual links or file references. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
3a2d27d
Table of Contents
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.