geoflow

Operate/develop GEOFlow CLI/Laravel/admin/API, topics/专题 and topic tasks, theme libraries/replication, sites/leads/Agent, channel sync and legacy yao-geoflow-cli/design/template migration. Use for source-free previews, planned Updater operations and receipt recovery. Discover capabilities; exclude unrelated work, SQL shortcuts, invented routes, auth bypass, secrets and unapproved live/destructive actions.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exceptionally lean routing-and-boundaries overview that delegates detail to a well-organized, one-level-deep reference bundle and includes an explicit discover→implement→verify→authorize sequence with retry-safety rules. The main weaknesses are that executable specifics live almost entirely in referenced files rather than the body, and a meaningful slice of the bundle (about a third of the files) is not reachable by any link or mention from SKILL.md.

Suggestions

Link or list the currently unreachable bundle files from SKILL.md or from the reference files that cover their modes — notably laravel-api-v1-docker.md and scripts/channel_endpoint_safety.py are mentioned nowhere in the bundle.

Surface the key scripts in the Route/Boundaries sections the way discover_geoflow_workspace.py is surfaced (e.g. geoflow_preflight.sh for the 'preflight curl' step, discover_themes.py for theme work) so executable entry points are visible without reading references.

Expand the one-line 'Discover→implement→verify→authorized finalize' chain into a short numbered sequence naming where each step's detailed checklist lives (which reference file), keeping the per-mode workflows as the detail layer.

Dimension	Reasoning	Score
Conciseness	The ~30-line body is lean and assumes Claude's competence — every line carries routing or boundary information ("Instance: installed `geoflow` help/profile, `whoami`, `capabilities`, `doctor`"; "One mode: source/tests→development; runtime writes→operations; themes/payloads→frontend") with zero padding and no explanation of concepts Claude already knows.	5 / 5
Actionability	Concrete, executable guidance is present — the exact invocation "scripts/discover_geoflow_workspace.py <workspace>", named CLI subcommands (`whoami`, `capabilities`, `doctor`), and environment specifics ("Python 3.10+", "preflight curl") — but most executable detail is delegated to the reference files and some directives remain high-level ("Follow repository rules/tests"), so it is not fully copy-paste-ready anchor 5.	4 / 5
Workflow Clarity	A clear sequenced process with an explicit verification gate is stated ("Discover→implement→verify→authorized finalize") plus error-recovery feedback loops ("Lost draft create/change responses: inspect state before retry"; "reconcile business state before an explicitly authorized new request"), and high-risk actions require "exact target and explicit authorization". Detailed per-operation step sequences live in the per-mode workflow files rather than the body, leaving minor checkpoint gaps versus anchor 5.	4 / 5
Progressive Disclosure	The body is a well-organized hub: mode-indexed labeled references (development/operations/public_frontend/channel_frontend/legacy_migration), all 15 linked paths exist on disk, and reference files link no further references, so depth is one level. However, 8 of 22 reference files and 11 of 12 scripts are not linked from SKILL.md (e.g. laravel-theme-contract.md, geoflow_preflight.sh), and laravel-api-v1-docker.md and channel_endpoint_safety.py are mentioned nowhere in the bundle, so navigation is good but not gapless.	4 / 5
	Total	17 / 20 Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A dense, domain-specific description that names concrete subsystems, includes an explicit "Use for" trigger clause, and is tightly scoped to a unique system. Its main weakness is that the when-clause covers only three scenarios (previews, Updater operations, receipt recovery) while the capability list is far broader, and the heavy slash-compression slightly obscures natural trigger phrasing.

Suggestions

Extend the "Use for..." clause to cover the other major scenarios the what-clause names (e.g. topic/专题 tasks, theme library edits and replication, channel frontend work, legacy template/skill-ID migration) so the when matches the breadth of the what.

Replace telegraphic fragments like "sites/leads/Agent" with the natural phrases a user would type when they need those capabilities (e.g. "manage sites and leads").

State the actions for each named subsystem rather than listing objects alone, so every clause pairs a verb with its target.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions across named subsystems — "Operate/develop GEOFlow CLI/Laravel/admin/API", "channel sync and legacy yao-geoflow-cli/design/template migration", "receipt recovery" — but verbs like "Operate/develop" are generic and "sites/leads/Agent" names objects without actions, leaving minor gaps versus the comprehensive anchor 5.	4 / 5
Completeness	The what is clear ("Operate/develop GEOFlow CLI/Laravel/admin/API ... migration") and an explicit when clause exists ("Use for source-free previews, planned Updater operations and receipt recovery"), so above anchor 3; but the when covers only three scenarios while the what spans topics, themes, channel sync, frontends and migration, so it is not the fully explicit anchor 5.	4 / 5
Trigger Term Quality	Good coverage of natural domain terms a user would say — "GEOFlow", "Laravel", "topics/专题", "channel sync", "Updater", "preview" — including the bilingual synonym "专题". A few natural phrasings users would plausibly say (e.g. "publish", "theme edit") are absent, and the telegraphic slash style compresses others, so not anchor 5.	4 / 5
Distinctiveness Conflict Risk	"GEOFlow", "yao-geoflow-cli" and "专题" pin the description to a single named system with a clear niche and distinct triggers, giving minimal conflict risk with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: yaojingang/GEOFlow
Path: .agents/skills/geoflow/SKILL.md
Commit: d7f601d

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.