gitignore-generator
Gitignore Generator - Auto-activating skill for DevOps Basics. Triggers on: gitignore generator, gitignore generator Part of the DevOps Basics skill category.
36
Quality
3%
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
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 severely underdeveloped, essentially just restating the skill name without explaining capabilities or usage triggers. It provides no actionable information for Claude to determine when to select this skill over others. The redundant trigger terms and boilerplate category information add no value.
Suggestions
Add specific actions the skill performs, e.g., 'Generates .gitignore files for various programming languages, frameworks, and IDEs. Supports common templates for Python, Node.js, Java, and other ecosystems.'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user asks to create a gitignore, ignore files in git, set up a new repository, or mentions .gitignore, gitignore template, or excluding files from version control.'
Remove the redundant duplicate trigger term and add varied natural language triggers users would actually say.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Gitignore Generator') without describing any concrete actions. It doesn't explain what the skill actually does - no mention of creating, generating, or customizing .gitignore files. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and has no 'Use when...' clause or equivalent guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'gitignore generator' repeated twice. Missing natural variations users would say like 'gitignore', '.gitignore', 'ignore files', 'git ignore', or language/framework-specific terms. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'gitignore' is fairly specific and unlikely to conflict with many other skills, but the lack of detail about what it generates or for which languages/frameworks could cause confusion with other DevOps or git-related 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 entirely meta-content describing what a gitignore generator skill would do, without providing any actual gitignore generation capability. It contains no code examples, no common gitignore patterns, no language/framework-specific templates, and no actionable instructions. The content is essentially a placeholder that fails to teach Claude anything useful about generating gitignore files.
Suggestions
Add concrete gitignore examples for common languages/frameworks (Python, Node.js, Java, etc.) with copy-paste ready content
Include a workflow for generating custom gitignore files: identify project type -> select base template -> add custom exclusions -> validate
Provide a reference to common patterns (OS files, IDE files, build artifacts, secrets) with specific examples like '.env', 'node_modules/', '__pycache__/'
Remove all meta-content about 'when to use' and 'example triggers' - replace with actual gitignore generation instructions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with meta-descriptions about when the skill activates and what it does, rather than providing actual gitignore generation guidance. It explains obvious concepts like 'provides step-by-step guidance' without providing any actual guidance. | 1 / 3 |
Actionability | No concrete code, commands, or examples of actual gitignore patterns are provided. The content describes what the skill could do but never shows how to generate a gitignore file or provides any executable guidance. | 1 / 3 |
Workflow Clarity | No workflow is present. The skill claims to provide 'step-by-step guidance' but contains zero actual steps for generating or customizing gitignore files. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-information with no structure for actual content. There are no references to detailed materials, examples, or templates that would help with gitignore generation. | 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
994edc4
- 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.