here-be-git
Initialise a git repository with optional agent commit instructions and .gitignore. Use when users say "here be git", "init git", "initialise git", or otherwise indicate they want to set up version control in the current directory.
Install with Tessl CLI
npx tessl i github:intellectronica/agent-skills --skill here-be-git84
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/skillAgent success when using this skill
Validation for skill structure
Discovery
89%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 well-crafted skill description that excels in trigger term quality and completeness with an explicit 'Use when...' clause containing both specific phrases and general intent. The main weakness is that the capabilities could be slightly more specific about what 'agent commit instructions' means and what exactly gets configured.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (git repository) and some actions (initialise, optional agent commit instructions, .gitignore), but doesn't comprehensively list all specific actions like what 'agent commit instructions' entails or other setup steps. | 2 / 3 |
Completeness | Clearly answers both what (initialise git repo with optional commit instructions and .gitignore) AND when (explicit 'Use when...' clause with specific trigger phrases and general version control setup intent). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'here be git', 'init git', 'initialise git', and the broader 'set up version control' - these are phrases users would naturally say when wanting this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche focused specifically on git initialization with unique trigger phrases like 'here be git'. Unlikely to conflict with other git-related skills that might handle commits, branches, or other operations. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a clear, well-structured workflow for git initialization with good decision points and user interaction. However, it could be more actionable by including actual executable commands and concrete .gitignore file examples rather than just listing patterns. The embedded AGENTS.md content is intentionally emphatic but adds verbosity.
Suggestions
Add a concrete .gitignore example showing the actual file content for at least one flavour (e.g., Node.js) rather than just listing patterns
Include the actual git commands as executable code blocks (e.g., `git init`, `git add AGENTS.md`, `git commit -m "..."`) rather than just describing them
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary verbosity, particularly in the AGENTS.md commit instructions block which is intentionally emphatic but quite lengthy. The workflow steps are clear but could be tightened. | 2 / 3 |
Actionability | Provides clear step-by-step instructions but lacks executable code examples. The gitignore patterns are listed as bullet points rather than actual file content, and there's no concrete example of what the generated .gitignore should look like. | 2 / 3 |
Workflow Clarity | Clear three-step sequence with explicit decision points (user confirmations), conditional logic for existing files, and commit checkpoints after each configuration step. The workflow handles edge cases like existing git repos. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines of actual instruction, the content is well-organized with clear sections (Workflow steps, Notes). No external references needed for this simple, self-contained task. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.