Git
v1.0.0

`llm-council` — external-tools review layer

by @ffroliva0 pulls
URLopenbooklet.com/s/llm-council-external-tools-review-layer
Pinnedopenbooklet.com/s/[email protected]
APIGET /api/v1/skills/llm-council-external-tools-review-layer

7 skills from this repoffroliva/gflow-cli
`llm-council` — external-tools review layerviewing
`/gflow:doc-review` — Documentation Review Gateskills/doc-review/SKILL.md

Run this gate before cutting a release. Two phases:

`/gflow:live-verify` — Live-verification enforcementskills/live-verify/SKILL.md

gflow-cli reverse-engineers a blackbox: Google Flow. Offline checks (`ruff`, `pyright`, unit/BDD tests) verify gflow-cli's own code does what it's supposed to; they cannot verify Flow still behaves the way it was captured, because Flow is external and changes without notice (see [#174](https://githu

`/gflow:release` — Cut a new releaseskills/release/SKILL.md

Follow this sequence verbatim. Every step matters.

`issue-assessment` — triage a gflow-cli issue honestlyskills/issue-assessment/SKILL.md

Read-only conductor. Verify the reporter's claim against the code, tests, docs, `KNOWN_ISSUES.md`, and auto-memory; classify it; judge whether it can be verified end-to-end *in the current environment*; and draft a reply. The output is a standard artifact a human or the `issue-resolve` skill can act

`spike` — measure the blackbox before you describe itskills/spike/SKILL.md

gflow-cli drives a product it does not own. Every statement about what Flow does is either **measured** or **guessed**, and a guess written into code or docs becomes a fact nobody re-checks.

sonarskills/sonar/SKILL.md

Check the SonarCloud quality gate for a PR (or the current branch) and drive it to zero. Reports GREEN, or the exact PR-scoped new issues/hotspots/coverage gaps to fix.

Auto-indexed from ffroliva/gflow-cli

Are you the author? Claim this skill to take ownership and manage it.

Related Skills

@openbooklet

graceful-error-recovery

Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.

1.1K0
@openbooklet

audience-aware-communication

Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.

1.1K0
@openbooklet

Refactoring Expert

Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.

600
@openbooklet

Research Expert

Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.

600
@openbooklet

clarify-ambiguous-requests

Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.

1.1K0
@openbooklet

structured-step-by-step-reasoning

Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.

1.1K0