Install
$ agentstack add skill-viknesh20-20-claude-code-tool-kit-write-skill ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Skill Creator
Existing Skills (for pattern reference)
!ls .claude/skills/ 2>/dev/null
Process
Step 1: Gather Requirements
From the user's description, determine:
- Name: lowercase-with-hyphens, becomes the
/slash-command - Purpose: What does this skill do?
- Trigger: When should someone use it?
- Input: What arguments does it need?
- Output: What should it produce?
- Tools needed: Which Claude Code tools does it require?
Step 2: Generate SKILL.md
Create the file following this template:
---
name: skill-name
description: "One sentence: what it does + when to use it. Be specific enough for auto-invocation."
argument-hint: "[argument description]"
allowed-tools: Read, Grep, Glob
---
# Skill Title
## Context Detection
!`relevant shell command for auto-detecting project context`
---
## Instructions
### Step 1: [First action]
Detailed instructions for what Claude should do.
### Step 2: [Second action]
...
### Step N: [Final action]
...
## Output Format
Describe the expected structure of the output.
## Rules
- Rule 1
- Rule 2
Step 3: Validate the Skill
Check the generated SKILL.md against these requirements:
- [ ] Frontmatter has
nameanddescription(required) - [ ] Description is under 150 characters and specific
- [ ]
allowed-toolslists only what's needed (principle of least privilege) - [ ] Shell injection uses
!command`` syntax correctly - [ ] Instructions are numbered steps, not vague paragraphs
- [ ] Output format is defined
- [ ] Rules section exists with boundaries
Step 4: Save and Test
- Create directory:
.claude/skills// - Save
SKILL.mdto that directory - Instruct user to test: open Claude Code, type
/
Frontmatter Reference
| Field | Required | Description | |-------|----------|-------------| | name | Yes | Slash command name (lowercase, hyphens) | | description | Yes | When to use (specific, <150 chars) | | argument-hint | No | Autocomplete hint, e.g. [filename] | | allowed-tools | No | Tools allowed without asking | | disable-model-invocation | No | true = manual only | | user-invocable | No | false = hidden from menu | | model | No | Override model | | effort | No | low, medium, high, max | | context | No | fork for subagent isolation |
Rules
- Follow existing skill patterns in this project
- Keep SKILL.md under 200 lines
- Use shell injection for context detection, not hardcoded assumptions
- Description must be specific enough for Claude to auto-invoke correctly
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: viknesh20-20
- Source: viknesh20-20/claude-code-tool-kit
- License: MIT
- Homepage: https://viknesh20-20.github.io/claude-code-tool-kit/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.