How do I install the Geoflow skill?

Run npx skillmds@latest add yaojingang/geoflow 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 Geoflow safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Geoflow?

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 Geoflow free to use?

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

Who published Geoflow?

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

Geoflow by yaojingang — Agent Skill

Name: Geoflow
Author: yaojingang

Geoflow

Develop or operate GEOFlow across Laravel backend/admin/API/CLI, the default site, themes, leads, and GeoFlow Agent channel sites. Use for code changes, running-system operations, frontend or template edits, channel capability sync, legacy PHP migration, or retired yao-geoflow-cli, yao-geoflow-design, and yao-geoflow-template IDs. Discover real routes first. Excludes unrelated work, database shortcuts, invented routes, auth bypass, secret exposure, raw copying, and unapproved live or destructive actions.

yaojingang 4037edc 59 files · 385.8 KB Updated Sep 17, 2026

File contents

GEOFlow

Route

Run scripts/discover_geoflow_workspace.py <workspace> for source work or scripts/geoflow_preflight.sh "<workspace>" [config] [checks] before runtime mutations. Inspect current CLI help and routes when available.
Load one route:

development: development-workflow.md and system-capability-discovery.md
operations: operation-boundary.md, command-map.md, and geoflow-current-capability-map.md
public_frontend: frontend-resource-index.md and geoflow-frontend-map.md
channel_frontend: frontend-resource-index.md and channel-frontend-contract.md
legacy_migration: legacy-template-migration.md and legacy-skill-id-migration.md

Mixed work follows: discover, implement, test or preview, approved finalize.

Mode Boundaries

Each phase has one mode. development edits code and tests; operations uses supported runtime interfaces; public_frontend prepares themes or payloads; channel_frontend handles target-package contracts. Switch modes when crossing these boundaries. Keep authenticated form creation, sync, activation, and publication as confirmed operations phases.

Guardrails

Follow repository rules and focused tests.
Run bundled helpers on macOS, Linux, or WSL with Python 3.10+ and Bash where required; runtime preflight also needs curl, and live channel reports need PHP CLI plus a working project artisan. If a dependency is unavailable, stay in read-only discovery, report the missing verification layer, and do not claim live success.
Preserve authentication, CSRF, idempotency, permissions, readback, contracts, and secret redaction.
Separate preview, import, sync, activation, publication, updates, rollback, and destructive actions. Require the exact target and explicit approval for high-risk steps.
Report the selected mode, evidence, touched files/routes/resources, verification, final state, and remaining risks.

---name: geoflowdescription: Develop or operate GEOFlow across Laravel backend/admin/API/CLI, the default site, themes, leads, and GeoFlow Agent channel sites. Use for code changes, running-system operations, frontend or template edits, channel capability sync, legacy PHP migration, or retired yao-geoflow-cli, yao-geoflow-design, and yao-geoflow-template IDs. Discover real routes first. Excludes unrelated work, database shortcuts, invented routes, auth bypass, secret exposure, raw copying, and unapproved live or destructive actions.---# GEOFlow## Route1. Run `scripts/discover_geoflow_workspace.py <workspace>` for source work or `scripts/geoflow_preflight.sh "<workspace>" [config] [checks]` before runtime mutations. Inspect current CLI help and routes when available.2. Load one route:- `development`: [development-workflow.md](references/development-workflow.md) and [system-capability-discovery.md](references/system-capability-discovery.md)- `operations`: [operation-boundary.md](references/operation-boundary.md), [command-map.md](references/command-map.md), and [geoflow-current-capability-map.md](references/geoflow-current-capability-map.md)- `public_frontend`: [frontend-resource-index.md](references/frontend-resource-index.md) and [geoflow-frontend-map.md](references/geoflow-frontend-map.md)- `channel_frontend`: [frontend-resource-index.md](references/frontend-resource-index.md) and [channel-frontend-contract.md](references/channel-frontend-contract.md)- `legacy_migration`: [legacy-template-migration.md](references/legacy-template-migration.md) and [legacy-skill-id-migration.md](references/legacy-skill-id-migration.md)3. Mixed work follows: discover, implement, test or preview, approved finalize.## Mode BoundariesEach phase has one mode. `development` edits code and tests; `operations` uses supported runtime interfaces; `public_frontend` prepares themes or payloads; `channel_frontend` handles target-package contracts. Switch modes when crossing these boundaries. Keep authenticated form creation, sync, activation, and publication as confirmed operations phases.## Guardrails- Follow repository rules and focused tests.- Run bundled helpers on macOS, Linux, or WSL with Python 3.10+ and Bash where required; runtime preflight also needs `curl`, and live channel reports need PHP CLI plus a working project `artisan`. If a dependency is unavailable, stay in read-only discovery, report the missing verification layer, and do not claim live success.- Preserve authentication, CSRF, idempotency, permissions, readback, contracts, and secret redaction.- Separate preview, import, sync, activation, publication, updates, rollback, and destructive actions. Require the exact target and explicit approval for high-risk steps.- Report the selected mode, evidence, touched files/routes/resources, verification, final state, and remaining risks.

Frequently asked questions