How do I install the Erk Exec skill?

Run npx skillmds@latest add majiayu000/erk-exec in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Erk Exec safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: CAUTION, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Erk Exec?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Erk Exec free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Erk Exec?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Erk Exec by majiayu000 — Agent Skill

Name: Erk Exec
Rating: 4.2 (5 reviews)
Author: majiayu000

Erk Exec

Guide for erk exec subcommands. Use when running erk exec commands to understand syntax, find the right command for a task, or learn common workflows. Always check syntax with -h or load this skill before running erk exec commands.

majiayu000 Updated Sep 9, 2026 567 repo stars

File contents

erk exec Guide

Quick Start

Before running any erk exec command, check syntax with -h:

erk exec <command> -h

Commands by Workflow

PR Review Operations

When addressing PR review comments or resolving threads:

Command	Purpose
`get-pr-review-comments`	Fetch review comments (use `--pr N`)
`resolve-review-thread`	Resolve a thread (use `--thread-id`)
`reply-to-discussion-comment`	Reply to discussion comment
`get-pr-discussion-comments`	Fetch discussion comments

Typical workflow:

erk exec get-pr-review-comments --pr 123
Make code changes
erk exec resolve-review-thread --thread-id PRRT_xxx

Plan Operations

When working with erk-plan issues:

Command	Purpose
`plan-save-to-issue`	Save plan to GitHub issue
`get-plan-metadata`	Get metadata from plan issue
`setup-impl-from-issue`	Set up .impl/ from issue
`plan-submit-for-review`	Extract plan content for PR review
`plan-create-review-branch`	Create review branch with plan
`get-issue-body`	Fetch issue body (REST API)
`update-issue-body`	Update issue body (REST API)

Session Operations

When working with Claude Code sessions:

Command	Purpose
`list-sessions`	List sessions for current project
`preprocess-session`	Compress session for analysis
`upload-session`	Upload session to gist
`download-remote-session`	Download session from gist

Marker Operations

For inter-process communication:

Command	Purpose
`marker create`	Create marker file
`marker exists`	Check if marker exists
`marker read`	Read marker content
`marker delete`	Delete marker file

All marker commands require --session-id.

Full Reference

For complete syntax details on all 65+ commands:

@reference.md

---name: erk-execdescription: Guide for erk exec subcommands. Use when running erk exec commands to understand syntax, find the right command for a task, or learn common workflows. Always check syntax with -h or load this skill before running erk exec commands.--- # erk exec Guide ## Quick Start Before running any `erk exec` command, check syntax with `-h`: ```bash erk exec <command> -h ``` ## Commands by Workflow ### PR Review Operations When addressing PR review comments or resolving threads: | Command | Purpose | | ----------------------------- | ------------------------------------ | | `get-pr-review-comments` | Fetch review comments (use `--pr N`) | | `resolve-review-thread` | Resolve a thread (use `--thread-id`) | | `reply-to-discussion-comment` | Reply to discussion comment | | `get-pr-discussion-comments` | Fetch discussion comments | **Typical workflow:** 1. `erk exec get-pr-review-comments --pr 123` 2. Make code changes 3. `erk exec resolve-review-thread --thread-id PRRT_xxx` ### Plan Operations When working with erk-plan issues: | Command | Purpose | | --------------------------- | ---------------------------------- | | `plan-save-to-issue` | Save plan to GitHub issue | | `get-plan-metadata` | Get metadata from plan issue | | `setup-impl-from-issue` | Set up .impl/ from issue | | `plan-submit-for-review` | Extract plan content for PR review | | `plan-create-review-branch` | Create review branch with plan | | `get-issue-body` | Fetch issue body (REST API) | | `update-issue-body` | Update issue body (REST API) | ### Session Operations When working with Claude Code sessions: | Command | Purpose | | ------------------------- | --------------------------------- | | `list-sessions` | List sessions for current project | | `preprocess-session` | Compress session for analysis | | `upload-session` | Upload session to gist | | `download-remote-session` | Download session from gist | ### Marker Operations For inter-process communication: | Command | Purpose | | --------------- | ---------------------- | | `marker create` | Create marker file | | `marker exists` | Check if marker exists | | `marker read` | Read marker content | | `marker delete` | Delete marker file | All marker commands require `--session-id`. ## Full Reference For complete syntax details on all 65+ commands: @reference.md

Frequently asked questions