skill-authoring
- Repo stars 198
- Author updated Live
- Author repo siclaw
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @scitix · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- macOS · Linux · Windows
- Runtime requirements
- Node.js
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: skill-authoring
description: >- Read this guide before creating a new skill or improving an existing one. name: <kebab-case-n…
category: other
runtime: Node.js
---
# skill-authoring output preview
## PART A: Task fit
- Use case: >- Read this guide before creating a new skill or improving an existing one. name: <kebab-case-name> One-line summary. Mention the execution tool if the skill uses scripts. runs entirely locally; runs on Node.js. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “SKILL.md Format / Purpose / Tool” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “>- Read this guide before creating a new skill or improving an existing one. name: <kebab-case-name> One-line summary. Mention the execution tool if the skill uses scripts. runs entirely locally; runs on Node.js. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “SKILL.md Format / Purpose / Tool” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source mentions slash commands such as `/proc`, `/sys`; use them first when your agent supports command triggers.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands.
Validate with a small run
Start with a small task and check whether the result follows “SKILL.md Format / Purpose / Tool”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: skill-authoring
description: >- Read this guide before creating a new skill or improving an existing one. name: <kebab-case-n…
category: other
source: scitix/siclaw
---
# skill-authoring
## When to use
- >- Read this guide before creating a new skill or improving an existing one. name: <kebab-case-name> One-line summary.…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “SKILL.md Format / Purpose / Tool” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "skill-authoring" {
input -> user goal + target files + boundaries + acceptance criteria
context -> SKILL.md Format / Purpose / Tool
rules -> SKILL.md triggers / order / output contract
runtime -> Node.js | read files, write/modify files, run shell commands | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Skill Authoring Guide
Read this guide before creating a new skill or improving an existing one.
SKILL.md Format
---
name: <kebab-case-name>
description: >-
One-line summary. Mention the execution tool if the skill uses scripts.
---Followed by markdown body:
# <Title>
## Purpose
What problem this skill solves and when to use it.
## Tool
<execution tool invocation — required for script-based skills>
Example: local_script: skill="check-pod-oom", script="check.sh", args="<ns> <pod>"
## Parameters
| Parameter | Required | Description |
|-----------|----------|-------------|
| `<arg1>` | Yes | ... |
## Procedure
Step-by-step actions with concrete commands.
## Examples
Concrete tool invocations with realistic parameters.Script Execution Modes
| Tool | Runs where | When to use |
|---|---|---|
local_script |
AgentBox (local) | kubectl commands from outside the cluster — most common |
node_script |
K8s node (host) | Needs host tools, /proc, /sys, devices, nsenter |
pod_script |
Inside a pod | Diagnostics inside a running container |
node_script + netns |
Node + pod's network ns | Host tools + pod's network view (call resolve_pod_netns first) |
Best Practices
- One skill, one purpose — don't make Swiss army knives
- Script over inline commands — if the procedure has more than 3 steps, write a script
- Idempotent and read-only — skills are for diagnosis, not remediation
- Description is critical — the agent uses it to decide whether to use this skill
- Concrete examples — at least 2 examples with realistic parameters
- Explain expected output — describe what normal vs abnormal output looks like
- Severity thresholds — when checking error counters, give thresholds so the agent can judge
Common Mistakes
- Too much raw output — dump kubectl describe without filtering. Grep for relevant lines
- Missing Tool section — without it, the agent doesn't know which execution tool to use
- Wrong execution mode — using
local_scriptfor host-level tools (usenode_script) - Hardcoded values — node names, namespaces should be parameters
- No severity guidance — e.g., CRC errors: 0 = normal, 1-100 = minor, >1000 = critical
Decide Fit First
Design Intent
How To Use It
Boundaries And Review