skill-alias
Skill36 starsChanged 2 months agoApache-2.0View on GitHub
Create command aliases for skills with arguments
In this repository52 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- agent-browserSkill
- arch-specSkill
- code-qualitySkill
- code-reviewSkill
- commitSkill
- coord-delegateSkill
- coord-handoffSkill
- coord-orchestrateSkill
- coord-requestSkill
- coord-reviewSkill
- coord-runSkill
- coord-syncSkill
- dispatchSkill
- edda-releaseSkill
- fleet-epic-splitSkill
- fleet-managerSkill
- fleet-orchestrateSkill
- fleet-pr-loopSkill
- fleet-reviewSkill
- fleet-triadSkill
- fleet-workerSkill
- ground-checkSkill
- health-checkSkill
- intel-scanSkill
- issue-actionSkill
- issue-compactSkill
- issue-createSkill
- issue-intakeSkill
- issue-pipelineSkill
- issue-planSkill
- issue-scanSkill
- parallel-waveSkill
- path-forwardSkill
- plan-decomposeSkill
- plan-validateSkill
- pr-checkSkill
- project-planSkill
- Project PrinciplesSkill
- pr-review-loopSkill
- pr-reviewSkill
- pull-requestSkill
- regression-guardSkill
- skill-craftSkill
- skill-testSkill
- spec-review-modesSkill
- tech-debtSkill
- testingSkill
- tracking-issueSkill
- verifiable-goal-loopSkill
- fleet-orchestrateSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
19 rules. About 0 are common, 16 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈16
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 59
Create .claude/commands/{ALIAS}.md with the following structure:
- Distinctive: line 78
After creating the file:
- Distinctive: line 125
Remove quotes from rest
- Very specific: line 130
Always create files in .claude/commands/
- Very specific: line 131
Use the ALIAS as the filename with .md extension
- Distinctive: line 132
Ensure directory exists before creating file
- Distinctive: line 150
Must be a valid TypeScript code block with:
- Distinctive: line 173
If file creation fails:
- Distinctive: line 244
Use kebab-case for alias names
- Distinctive: line 246
Avoid conflicts with existing commands
- Distinctive: line 247
Use common prefixes for related commands
- Distinctive: line 251
Keep descriptions brief (one line)
- Distinctive: line 252
Follow format: "Alias for {skill} {operation}"
- Distinctive: line 253
Don't include implementation details
- Distinctive: line 258
After creating an alias:
- Distinctive: line 259
Verify file is readable
- Distinctive: line 260
Check YAML front matter is valid
- Distinctive: line 261
Ensure TypeScript block is properly formatted
- Distinctive: line 262
Test that the alias works by using it
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill Alias Creator
You are a skill alias creator for the edda project. Your role is to create command aliases that wrap skill calls with predefined arguments.
Purpose
This skill allows users to create convenient command shortcuts for frequently used skill operations. Instead of typing /skill-name operation args repeatedly, users can create a short alias like /alias-name that executes the full command.
Usage
/skill-alias ALIAS=SKILL_NAME operation|argsParameter Format
The input parameter follows this format:
ALIAS- The name of the command alias to createSKILL_NAME- The name of the skill to invokeoperation|args- The arguments to pass to the skill
Examples
/skill-alias tech-debt-research='tech-debt research'
/skill-alias tech-debt-issue='tech-debt issue'
/skill-alias pr-check-fix='pr-check fix'Workflow
Step 1: Parse Input Parameter
Parse the input from the args parameter using this format:
ALIAS='SKILL_NAME arguments'Extract:
- ALIAS - The part before
= - SKILL_NAME - The first word after
=and' - ARGUMENTS - Everything after the first space in the quoted string
Example parsing:
- Input:
tech-debt-research='tech-debt research' - ALIAS:
tech-debt-research - SKILL_NAME:
tech-debt - ARGUMENTS:
research
Step 2: Generate Command File
Create .claude/commands/{ALIAS}.md with the following structure:
---
command: {ALIAS}
description: Alias for {SKILL_NAME} {ARGUMENTS}
---
```typescript
await Skill({
skill: "{SKILL_NAME}",
args: "{ARGUMENTS}"
});
### Step 3: Verify Creation
After creating the file:
1. **Verify file exists**:
```bash
ls -la .claude/commands/{ALIAS}.md- Display file content:
cat .claude/commands/{ALIAS}.md
Step 4: Report to User
Provide a concise summary:
# Command Alias Created
**Alias**: `/{ALIAS}`
**Executes**: `/{SKILL_NAME} {ARGUMENTS}`
**File**: `.claude/commands/{ALIAS}.md`
## Usage
You can now use:/{ALIAS}
Instead of:/{SKILL_NAME} {ARGUMENTS}
Implementation Notes
Input Parsing
The input can be in these formats:
ALIAS='SKILL_NAME args'ALIAS="SKILL_NAME args"ALIAS=SKILL_NAME args(no quotes)
Handle all variations by:
- Split on
=to get ALIAS and rest - Remove quotes from rest
- Split on first space to get SKILL_NAME and ARGUMENTS
File Path
- Always create files in
.claude/commands/ - Use the ALIAS as the filename with
.mdextension - Ensure directory exists before creating file
YAML Front Matter
Required fields:
command- The alias name (must match filename without .md)description- Brief description of what the alias does
Format:
---
command: alias-name
description: Alias for skill-name operation
---TypeScript Block
Must be a valid TypeScript code block with:
- Three backticks with
typescriptlanguage tag - Proper await Skill() call syntax
- Both skill and args parameters as strings
- Proper closing backticks
Example:
```typescript
await Skill({
skill: "tech-debt",
args: "research"
});
```Error Handling
If parsing fails:
- Report clear error message to user
- Show expected format
- Provide examples
If file creation fails:
- Check directory exists
- Check permissions
- Report specific error
Examples
Example 1: Tech Debt Research
Input: tech-debt-research='tech-debt research'
Created File: .claude/commands/tech-debt-research.md
---
command: tech-debt-research
description: Alias for tech-debt research
---
```typescript
await Skill({
skill: "tech-debt",
args: "research"
});
### Example 2: Tech Debt Issue
**Input**: `tech-debt-issue='tech-debt issue'`
**Created File**: `.claude/commands/tech-debt-issue.md`
```markdown
---
command: tech-debt-issue
description: Alias for tech-debt issue
---
```typescript
await Skill({
skill: "tech-debt",
args: "issue"
});
### Example 3: PR Check Fix
**Input**: `pr-check-fix='pr-check fix'`
**Created File**: `.claude/commands/pr-check-fix.md`
```markdown
---
command: pr-check-fix
description: Alias for pr-check fix
---
```typescript
await Skill({
skill: "pr-check",
args: "fix"
});
## Guidelines
### Command Naming
- Use kebab-case for alias names
- Make aliases descriptive but concise
- Avoid conflicts with existing commands
- Use common prefixes for related commands
### Description Writing
- Keep descriptions brief (one line)
- Follow format: "Alias for {skill} {operation}"
- Don't include implementation details
- Focus on what it does, not how
### Testing
After creating an alias:
- Verify file is readable
- Check YAML front matter is valid
- Ensure TypeScript block is properly formatted
- Test that the alias works by using it
---
## Error Messages
### Invalid Input Format
Error: Invalid input format
Expected: ALIAS='SKILL_NAME arguments' Received: {user-input}
Examples:
- tech-debt-research='tech-debt research'
- pr-check-fix='pr-check fix'
### Missing Components
Error: Could not parse input
Missing: {ALIAS/SKILL_NAME/ARGUMENTS}
Please provide input in format: ALIAS='SKILL_NAME arguments'
### File Creation Failed
Error: Failed to create command file
File: .claude/commands/{ALIAS}.md Reason: {error-message}
Please check:
- Directory exists and is writable
- No conflicting file exists
- Valid filename
---
## References
- Command documentation: `.claude/commands/`
- Skill documentation: `.claude/skills/`
- Example skills: `/tech-debt`, `/dev-server`Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

