Individual skill
yao-geoflow-cli
Use when operating an existing GEOFlow 2.1+ system from CLI, API v1, or authenticated admin web for catalog/material/task/job/article operations, enterprise knowledge, growth-center leads, distribution, analytics, URL import, theme editor, frontend-capability sync, system updates, settings, tokens, users, or preflight. Do not use for implementation, schema changes, direct DB edits, frontend design, or invented API routes.
skills/yao-geoflow-cli/SKILL.md
Source commit d21bfc1a7729a4b1baee896bdc51aab1caaf602a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 10, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 917
- Repository last updated
- Oct 1, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
README.mddoc · 3,113 bytesSKILL.mdcore · 2,017 bytesSKILL.mdcore · 2,017 bytesSKILL.mdcore · 2,017 bytesagents/interface.yamlasset · 1,098 bytesagents/openai.yamlasset · 620 bytesevals/expected_artifacts.jsonasset · 1,902 bytesevals/semantic_config.jsonasset · 2,786 bytesevals/trigger_cases.jsonasset · 7,029 bytesexamples/README.mddoc · 526 bytesmanifest.jsonasset · 526 bytesreferences/command-map.mddoc · 22,107 bytesreferences/geoflow-current-capability-map.mddoc · 8,583 bytesreferences/laravel-api-v1-docker.mddoc · 7,718 bytesreferences/operation-boundary.mddoc · 5,529 bytesreports/geoflow-skill-upgrade-2026-07-05.mddoc · 2,309 bytesscripts/geoflow_preflight.shruns · 7,586 bytestemplates/brief-template.mddoc · 471 bytes
Read excerpt
# Yao GEOFlow Operations
Operate a running GEOFlow instance. Prefer supported `bin/geoflow`, then API v1 for exposed content operations, then authenticated admin web for management workflows absent from API v1.
## Boundary
- Owns operational CLI/API/admin work, CSRF/session handling, idempotency, readback verification, high-risk confirmation, and secret/personal-data redaction.
- Excludes product-code edits, migrations, direct SQL, frontend design, route invention, auth bypass, and secret exposure.
- Use `yao-geoflow-design` for homepage/design payload planning.
## Checks
1. Confirm `artisan` or `bin/geoflow`.
2. Run `scripts/geoflow_preflight.sh "<workspace>" [config] [checks]` before first mutation.