bl-record
Record changes as a new commit in git-branchless workflow
67
55%
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/git-workflow/skills/bl-record/SKILL.mdQuality
Discovery
32%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is too brief and lacks explicit trigger guidance, making it difficult for Claude to know when to select this skill over other git-related skills. While it mentions the specific 'git-branchless' context which helps with distinctiveness, it fails to explain the full scope of capabilities or provide clear usage triggers.
Suggestions
Add a 'Use when...' clause specifying triggers like 'when user mentions git-branchless, stacked commits, or wants to record changes without traditional branches'
Expand the capabilities list to include specific git-branchless actions like 'create stacked commits, amend previous commits in stack, rebase commit stacks'
Include natural trigger terms users might say such as 'save my changes', 'make a commit', 'snapshot code', 'git record'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (git-branchless workflow) and one action (record changes as a new commit), but doesn't list multiple concrete actions or elaborate on what recording changes entails. | 2 / 3 |
Completeness | Describes what it does (record changes as a commit) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'commit' and 'git-branchless' which are relevant keywords, but misses common variations users might say like 'save changes', 'snapshot', 'stage', or just 'git commit'. | 2 / 3 |
Distinctiveness Conflict Risk | The 'git-branchless workflow' qualifier provides some distinction from generic git skills, but 'record changes as a new commit' could easily overlap with standard git commit skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with clear workflow steps and good error handling coverage. The main weakness is some verbosity in the flow examples that repeat information from the execution instructions, and the explanatory section at the end that Claude doesn't need. The structure is good but could be slightly more concise.
Suggestions
Remove or significantly condense the 'Flow Examples' section since the execution instructions already provide the same information with concrete commands
Remove the 'Why Detach After Branch Creation?' section - Claude can infer this from the workflow context
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some redundancy - the flow examples largely duplicate information already covered in the execution instructions, and the 'Why Detach After Branch Creation?' section explains something Claude could infer from the workflow. | 2 / 3 |
Actionability | Provides fully executable bash commands, specific flag usage, and copy-paste ready examples. The execution instructions are concrete with exact commands to run in each scenario. | 3 / 3 |
Workflow Clarity | Clear 4-step sequence with explicit checkpoints (check prerequisites, stage changes, record commit, show result). Includes verification via `git sl` and error handling table for common failure modes. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but everything is inline in one file. The flow examples section is lengthy and could potentially be separated, though for a skill of this size it's borderline acceptable. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- jpoutrin/product-forge
- Commit
0ebe7ae
- 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.