gitignore-generator
Gitignore Generator - Auto-activating skill for DevOps Basics. Triggers on: gitignore generator, gitignore generator Part of the DevOps Basics skill category.
41
11%
Does it follow best practices?
Impact
100%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/01-devops-basics/gitignore-generator/SKILL.mdQuality
Discovery
22%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 severely underdeveloped. It names the skill topic ('gitignore generator') but fails to describe any concrete capabilities, lacks a 'Use when...' clause, and duplicates its only trigger term. It would be very difficult for Claude to confidently select this skill over other DevOps or Git-related skills based on this description alone.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Generates .gitignore files with language-specific and framework-specific ignore patterns for common development environments.'
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to create a .gitignore file, needs to configure git ignore rules, or mentions excluding files from version control.'
Expand trigger terms to include natural variations like '.gitignore', 'git ignore', 'ignore file', 'exclude from git', and specific languages/frameworks (e.g., 'Python gitignore', 'Node gitignore').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('gitignore generator') but does not describe any concrete actions like 'creates .gitignore files', 'adds language-specific ignore patterns', or 'configures exclusion rules'. It only states it is an 'auto-activating skill' with no actionable detail. | 1 / 3 |
Completeness | The 'what' is extremely weak — it only says 'Gitignore Generator' without explaining what it actually does. The 'when' is partially addressed by listing trigger terms, but there is no explicit 'Use when...' clause or meaningful guidance on when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | It includes 'gitignore generator' as a trigger term, which is a natural keyword a user might say. However, it duplicates the same trigger and misses common variations like '.gitignore', 'git ignore', 'ignore file', 'exclude files from git', or language/framework-specific terms. | 2 / 3 |
Distinctiveness Conflict Risk | The term 'gitignore' is fairly niche and unlikely to conflict with many other skills, but the description is so vague that it could overlap with broader DevOps or Git-related skills. The mention of 'DevOps Basics' category adds some context but doesn't sharpen the niche enough. | 2 / 3 |
Total | 6 / 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 an empty template/placeholder with no actual content. It contains only meta-descriptions of what the skill would do without providing any gitignore patterns, examples, commands, or actionable guidance. It fails on every dimension because it describes a skill rather than being one.
Suggestions
Replace the meta-description sections with actual gitignore content: common patterns for popular languages/frameworks (Python, Node.js, Java, etc.) with ready-to-use .gitignore snippets.
Add concrete, copy-paste-ready .gitignore examples, e.g., `# Python\n__pycache__/\n*.pyc\n.env\nvenv/`
Include a brief workflow: 1. Identify project type, 2. Generate appropriate .gitignore, 3. Verify with `git status` that intended files are excluded.
Remove all 'When to Use', 'Example Triggers', and 'Capabilities' boilerplate sections — these waste tokens and provide no actionable value to Claude.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is almost entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual gitignore content, patterns, or commands. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are empty padding. | 1 / 3 |
Actionability | There is zero concrete, executable guidance. No gitignore patterns, no example .gitignore files, no commands, no code snippets. The entire content describes rather than instructs — it's a placeholder, not a skill. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains no actual steps. There is nothing for Claude to follow or execute. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no structure that aids navigation. There are no references to supporting files, no sections with actual content, and no meaningful organization beyond boilerplate headings. | 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 | |
- Commit
13d35b8
- 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.