Install
$ agentstack add skill-edouard-claude-pi-flow-skills-flow-quick ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
flow-quick — intent to code in a short loop
Sweet spot: task scopable in 900-1600 tokens of intent, single user-facing goal. No PRD, no architecture, no story file — just clean code + commit.
When to use
- Circumscribed bug fix (1 identifiable root cause)
- Small feature ( 1 day or multi-feature, STOP and suggest
/flow-prdor/flow-story.
Step 2 — Plan (5 lines max)
Quick plan in 5 lines:
- Root cause (if fix)
- Files to touch
- Approach (1 sentence)
- Tests to add/modify
- Risks (1 sentence)
Present, wait for quick OK or adjustment.
Step 3 — Implement
- Strictly follow the repo conventions (project-context)
- No opportunistic refactor outside scope
- Keep the diff minimal
- Run existing tests after changes
Step 4 — Self-review
- Bugs / edge cases covered?
- Conventions respected?
- No TODO / commented-out code left?
- Tests pass?
Step 5 — Commit draft
Propose a conventional commits message:
type(scope): short description
[optional body: reason for the change, not the what]
Output
No file in .agents/. Just:
- The modified code
- The tests
- A commit message draft
Halt conditions
If mid-way:
- You discover a deeper bug → stop, suggest
/flow-storyor/flow-introspect - The intent changes → stop, ask for clarification
- Existing tests break and it's non-trivial → stop, escalate
Next
None. If the task turns out to be bigger mid-run, stop and suggest /flow-prd (if new feature) or /flow-story (if inside a sprint).
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: edouard-claude
- Source: edouard-claude/pi-flow-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.