hyperflow-status
hyperflow-status displays a read-only snapshot of a Hyperflow project's current state, including active tasks with progress bars, completed subtasks, Git branches, specification and audit file counts, and memory entry totals. Use it to monitor project progress, check task status, and understand what work is currently in flight without triggering any modifications or new work execution.
git clone --depth 1 https://github.com/jeremylongshore/claude-code-plugins-plus-skills /tmp/hyperflow-status && cp -r /tmp/hyperflow-status/plugins/ai-agency/hyperflow/templates/antigravity/skills/hyperflow-status ~/.claude/skills/hyperflow-statusSKILL.md
# hyperflow-status — read-only state (Antigravity single-agent) One-screen view of hyperflow project state. **Read-only** — never edits files or runs work. Follow the `hyperflow` doctrine. ## Steps 1. Read `.hyperflow/tasks/*.md`; for each, report the status block (progress bar, sub-tasks done/total, branch). 2. Count `.hyperflow/specs/*.md` and `.hyperflow/audits/*.md`. 3. Count `.hyperflow/memory/*` entries. 4. Print a compact summary: active tasks + their progress, spec/audit counts, memory size. If `.hyperflow/` is absent, say so and suggest `hyperflow-scaffold`. ## Rules - Never modify any file. Never dispatch work. Output is a single status block.
Audit and fix Claude Code SKILL.md files against enterprise compliance standards: frontmatter completeness, required body sections, and style. Use when validating or repairing skills in a plugin directory. Trigger with "audit skill", "fix skill compliance".
Learn how SKILL.md files work in Claude Code plugins, then build a production-quality agent skill from scratch. Covers frontmatter schema, body structure, testing, and iteration.
Step-by-step guide to writing a SKILL.md file for Claude Code. Learn how to plan, structure, and test auto-activating skills with proper frontmatter, allowed-tools, dynamic context injection, and supporting files.
|
|
|
|
|