Skills — Reasonix Playbooks

A skill is a named playbook the Reasonix agent can invoke with run_skill. Each skill packages instructions, tooling patterns, and context into a reusable recipe so the agent doesn't need to re-derive the approach every time.

How they work

Skills appear in the agent's system prompt as a pinned index (one-liner + tag). The agent calls run_skill({ name: "<skill-name>", arguments: "<task>" }) and the skill body tells it what to do. Two modes:

Mode	Behavior
Inline	The skill body becomes a tool result the agent reads and follows directly — steps are visible in the conversation
Subagent ([🧬 subagent])	Spawns an isolated child loop — only the final answer comes back. Tool calls and reasoning during the run never enter the main context

Built-in skills

Skill	Mode	Purpose
explore	subagent	Wide-net codebase investigation — read-only, returns one distilled answer
research	subagent	Web search + code reading combined for external questions
review	subagent	Review pending changes (branch diff) — flags correctness, security, style
security-review	subagent	Security-focused diff review — injection, authz, secret leakage
test	inline	Run test suite, diagnose failures, propose fixes, re-run until green

User-added skills

Skill	Mode	Purpose
gog	inline	Google Workspace CLI — Gmail, Calendar, Drive, Contacts, Sheets, Docs via gog. Requires OAuth setup. See MCP Directory for the skill definition.

Cross-tool skill installation (Skillfish)

Skillfish installs skills across multiple AI coding tools simultaneously. Each tool stores its skills here:

Tool	Skills directory
Claude Code	~/.claude/skills/
Cursor	~/.cursor/skills/
Codex	~/.codex/skills/
GitHub Copilot	~/.github/skills/
Gemini CLI	~/.gemini/skills/
OpenClaw	~/skills/

Creating a new skill

The agent uses create_skill to scaffold a SKILL.md file under .reasonix/skills/<name>.md. The skill is then available in future sessions via /skill <name> or run_skill.

Claude Code — review vs gh-pr-review

Two PR review skills available in Claude Code. They solve the same problem differently.

review (plugin: pr-review-toolkit)

• Source: Installed from the Claude Code plugin marketplace into ~/.claude/plugins/.../pr-review-toolkit/
• Mechanism: Launches specialized review agents (code-reviewer, silent-failure-hunter, comment-analyzer, pr-test-analyzer, type-design-analyzer, code-simplifier) each focused on one aspect
• Scope: Local only — analyzes git diffs and codebase files
• GitHub integration: None — doesn't post comments, doesn't interact with PRs
• Best for: Pre-PR self-review before pushing code

gh-pr-review (custom skill)

• Source: Hand-written skill in ~/.claude/skills/gh-pr-review/SKILL.md
• Mechanism: Single workflow using the GitHub CLI (gh) — fetch diff → review → present findings → user picks which to post → post inline comments via GitHub API
• Scope: Full GitHub integration — can fetch PR diffs, post inline comments, submit reviews, approve/request changes
• GitHub integration: Deep — uses gh pr diff, gh api for inline comments, gh pr review for summaries
• Best for: Reviewing someone else's PR on GitHub with actual inline feedback

When to use which

Scenario	Use
Self-review before pushing	review
Reviewing a teammate's open PR	gh-pr-review
Need inline comments on GitHub	gh-pr-review
Deep dive on a specific aspect (tests, types, etc.)	review with targeted agent
End-to-end PR feedback workflow	gh-pr-review