Export Context

Export Context is an Automation skill for Claude Code, published by gmickel in flow-next.

685 stars54 forkson gmickel/flow-nextAdded 2026/08/23Repository updated 2026/08/22

agentic-workflowai-agentai-workflowanthropicautonomous-agentclaude-codeclaude-code-pluginclicode-reviewcodexexecutionfactory-droidmarketplaceopenai-codexplanningpluginralph-modesdlcspec-driven-developmentworkflow

Install in seconds

Install Export Context

Copy Export Context into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/gmickel/flow-next/tree/main/plugins/flow-next/skills/flow-next-export-context ~/.claude/skills/flow-next-export-context

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/gmickel/flow-next.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: plugins/flow-next/skills/flow-next-export-context/SKILL.md in gmickel/flow-next
Installs to: ~/.claude/skills/flow-next-export-context
Collection: One of 25 skills cataloged from this repository
Category: Automation — 1523 skills

What Export Context does

Export Context builds RepoPrompt review context and saves it as a markdown file for external LLM review. Use it when you want to share plan or implementation context with ChatGPT, Claude web, or another model.

Export Context is cataloged under Automation on DirSkills. Export Context comes from a repository tagged agentic-workflow, ai-agent, ai-workflow, anthropic and autonomous-agent.

Documentation

README

Excerpt

Export Context Mode

Build RepoPrompt context and export to a markdown file for use with external LLMs (ChatGPT Pro, Claude web, etc.).

Use case: When you want Carmack-level review but prefer to use an external model.

Preamble

CRITICAL: flowctl is BUNDLED — NOT installed globally. which flowctl will fail (expected). Define once; subsequent blocks use $FLOWCTL:

FLOWCTL="${DROID_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT}}/scripts/flowctl"
[ -x "$FLOWCTL" ] || FLOWCTL="<plugin-root>/scripts/flowctl"   # <plugin-root> = the directory two levels above this skill's SKILL.md file (the harness gave you that file's absolute path when the skill loaded); substitute it literally
[ -x "$FLOWCTL" ] || FLOWCTL=".flow/bin/flowctl"

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Export Context

What else does gmickel publish alongside Export Context?
Export Context is one of 25 skills that DirSkills catalogs from gmickel/flow-next, the repository it ships in. Its siblings there include Codebase Feature Map, Flow Interview and Flow Interview. Each one is a separate skill with its own page in this directory, installs the same way Export Context does, and is maintained by gmickel in that same repository. The rest of the collection is listed on the gmickel/flow-next page.
How does Export Context compare to other Automation skills?
Export Context ranks #1071 by stars among the 1523 Automation skills in this catalog. The most-starred ones next to it are Autonomous Loops, Autonomous Agent Harness and Automation Audit Ops. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Export Context against them. Open each page to compare what they document and how they install.