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
Example Agent Skills
siGit Code supports the open Agent Skills format. A
skill is a folder containing a SKILL.md file — YAML frontmatter (name and
description, at minimum) followed by Markdown instructions. Skills can bundle
scripts/, references/, and assets/ that the agent reads on demand.
Installing a skill
Copy a skill folder into one of the directories siGit scans (in priority order):
.sigit/skills/or.claude/skills/in your project (project-local)~/.config/sigit/skills/(honours$SIGIT_CONFIG_DIR)~/.claude/skills/(shared with the broader ecosystem)
For example, to install the commit-message skill here for the current project:
mkdir -p .sigit/skills
cp -R examples/skills/commit-message .sigit/skills/
The folder name must match the skill's name field.
How siGit uses them
siGit follows the spec's progressive disclosure:
- Discovery — at the start of each turn, siGit loads only each skill's
nameanddescriptioninto theskilltool's description. - Activation — when your task matches a skill, the agent calls the
skilltool with that name, which loads the fullSKILL.mdinto context. - Execution — the agent follows the instructions, reading any bundled files from the skill's directory with its normal file and command tools.
Run /skills to list the skills siGit can see.