main
claude/code-feature-parity-q003hm
claude/elegant-carson-l1menh
claude/sigit-acp-local-chat-cx6380
claude/sigit-cloud-agent-expansion-reox0a
claude/tool-permission-system
claude/zen-feynman-0u78dk
development
feature/agent-tools-multiedit-glob-todos-remember
feature/background-commands
feature/commit-coauthor-attribution
feature/headless-mode
feature/init-command
feature/load-local-model-explicitly
feature/session-persistence-compaction
feature/sigit-code-cloud
feature/subagent-tool
feature/tool-permission-system
feature/tui-repo-tabs
feature/tui-tabs
main
release/v1.3.1
| 1 | # Example Agent Skills |
| 2 | |
| 3 | siGit Code supports the open [Agent Skills](https://agentskills.io) format. A |
| 4 | skill is a folder containing a `SKILL.md` file — YAML frontmatter (`name` and |
| 5 | `description`, at minimum) followed by Markdown instructions. Skills can bundle |
| 6 | `scripts/`, `references/`, and `assets/` that the agent reads on demand. |
| 7 | |
| 8 | ## Installing a skill |
| 9 | |
| 10 | Copy a skill folder into one of the directories siGit scans (in priority order): |
| 11 | |
| 12 | - `.sigit/skills/` or `.claude/skills/` in your project (project-local) |
| 13 | - `~/.config/sigit/skills/` (honours `$SIGIT_CONFIG_DIR`) |
| 14 | - `~/.claude/skills/` (shared with the broader ecosystem) |
| 15 | |
| 16 | For example, to install the `commit-message` skill here for the current project: |
| 17 | |
| 18 | ```sh |
| 19 | mkdir -p .sigit/skills |
| 20 | cp -R examples/skills/commit-message .sigit/skills/ |
| 21 | ``` |
| 22 | |
| 23 | The folder name must match the skill's `name` field. |
| 24 | |
| 25 | ## How siGit uses them |
| 26 | |
| 27 | siGit follows the spec's *progressive disclosure*: |
| 28 | |
| 29 | 1. **Discovery** — at the start of each turn, siGit loads only each skill's |
| 30 | `name` and `description` into the `skill` tool's description. |
| 31 | 2. **Activation** — when your task matches a skill, the agent calls the `skill` |
| 32 | tool with that name, which loads the full `SKILL.md` into context. |
| 33 | 3. **Execution** — the agent follows the instructions, reading any bundled files |
| 34 | from the skill's directory with its normal file and command tools. |
| 35 | |
| 36 | Run `/skills` to list the skills siGit can see. |