flow-next-setup
Installs the flowctl CLI and adds automation instructions to the project repository.
Install
mkdir -p .claude/skills/flow-next-setup && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/3162" && unzip -o skill.zip -d .claude/skills/flow-next-setup && rm skill.zipInstalls to .claude/skills/flow-next-setup
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Optional local install of flowctl CLI and CLAUDE.md/AGENTS.md instructions. Use when user runs /flow-next:setup.Key capabilities
- →Installs flowctl CLI to local project path
- →Initializes CLAUDE.md project documentation
- →Standardizes agent environment configuration
- →Copies portable configuration scripts
How it works
It performs a local script-based installation of tools and populates documentation files to guide multi-assistant environments.
Inputs & outputs
When to use flow-next-setup
- →Setting up local flowctl tools
- →Initializing project agent documentation
- →Standardizing agent environment config
About this skill
Flow-Next Setup (Optional)
Wire this repo to the plugin: the versioned docs snippet plus flow-next configuration. Fully optional - flow-next works without this via the plugin.
Benefits
- Other AI agents (Codex, Cursor, etc.) can read instructions from CLAUDE.md/AGENTS.md
Read working-rules.md first; it holds for every step of this skill.
Workflow
Read workflow.md and follow each step in order.
Notes
- Fully optional - standard plugin usage works without local setup
- Copies nothing into the repo - plugin updates need no per-repo re-run, on any host
- Safe to re-run - needed only when the snippet schema bumps or configuration/seeds change
When not to use it
- →When you prefer global CLI installations
- →When standard agent plugins already meet all requirements
Limitations
- →Fully optional and not required for core plugin usage
- →Requires manual path addition to environment
- →No background updates for installed binaries
How it compares
It focuses on project-local portability and environment-agnostic agent instructions rather than globally configured tools.
Compared to similar skills
flow-next-setup side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| flow-next-setup (this skill) | 1 | 3mo | No flags | Beginner |
| codex-cli-bridge | 9 | 11mo | Review | Intermediate |
| skill-forge | 11 | 10mo | Review | Intermediate |
| obsidian-data-handling | 4 | 2mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by gmickel
View all by gmickel →You might also like
codex-cli-bridge
alirezarezvani
Bridge between Claude Code and OpenAI Codex CLI - generates AGENTS.md from CLAUDE.md, provides Codex CLI execution helpers, and enables seamless interoperability between both tools
skill-forge
WilliamSaysX
Automated skill creation workshop with intelligent source detection, smart path management, and end-to-end workflow automation. This skill should be used when users want to create a new skill or convert external resources (GitHub repositories, online documentation, or local directories) into a skill. Automatically fetches, organizes, and packages skills with proactive cleanup management.
obsidian-data-handling
jeremylongshore
Implement vault data backup, sync, and recovery strategies. Use when building backup features, implementing data export, or handling vault synchronization in your plugin. Trigger with phrases like "obsidian backup", "obsidian sync", "obsidian data export", "vault backup strategy".
rsyslog-doc-dist
rsyslog
Ensures doc/Makefile.am stays in sync with changes to documentation files.
custom-workers
ruvnet
Create and run custom background analysis workers with composable phases. Use when you need automated code analysis, security scanning, pattern learning, or API documentation generation.
droidrun-docs
droidrun
DroidRun documentation reference. Use when users ask about DroidRun setup, configuration, SDK usage, CLI commands, device setup, agents, architecture, app cards, credentials, tracing, Docker, migration, structured output, or any DroidRun "how do I..." questions.