flowai-plugins

Recommend which LLM to use for a task. Use when asked which model or best LLM for X, to pick a model, or for a shortlist ranked on live leaderboard evidence (coding, reasoning, agentic, tool-use, price, speed). Fetches leaderboards and cites them.

Use when the user asks to add Deno/TypeScript code-style rules to AGENTS.md, or during initial Deno project setup. Do NOT trigger for non-Deno TypeScript projects (use setup-agent-code-style-strict), or for runtime-agnostic style advice.

Add TypeScript strict-mode code-style rules to AGENTS.md. The rule text ships inside this skill, so write it from here, not from memory. Use when the user asks for strict-mode style rules. Not for Deno projects (use setup-agent-code-style-deno).

Generate a .devcontainer (devcontainer.json plus Dockerfile) for AI-IDE development with AI CLI integration, skill mounting and security hardening. Use when the user wants to set up or containerize a local dev environment. Not for cloud deploys.

Use when the user asks to take a new task all the way: plan, implement, review, commit and push. Not when a ready task file already exists. Self-contained — execute the inlined steps directly, do NOT invoke other skills via the Skill tool.

Use when the user asks to implement a ready task file (its Solution filled), then review, commit and push it. No planning; not for work that stops before the commit. Self-contained — execute the inlined steps directly, do NOT invoke other skills.

Show the current state of the project's tasks, hiding archived ones, by writing a project-local status script for however the project stores its tasks. Use when the user asks which tasks are open or in progress, or how far the work has got.

Use when the user asks to reconcile the project's AGENTS.md, CLAUDE.md and scaffolded files with the current flowai templates after a framework upgrade. Not for first-time setup, and not for tailoring the installed skills.

Build and run benchmarks that measure an AI AGENT's behaviour — scenarios, checklists, judged runs. Use when authoring or evaluating agent benchmark scenarios. Not for code performance benchmarks (deno bench, criterion) or ordinary test suites.

Write a Development Enhancement Proposal (DEP) for a technical improvement. Use when the user wants to propose, document, or formalize a technical change for review.

Supplies the accepted task format GODS (Goal, Overview, Definition of Done, Solution). Use when the user asks what that format is, or to write up decided work in it. NOT for planning before coding — weighing variants belongs to the planning skill.

Rewrite text in a dense, factual informational style with no fluff or marketing. Use when the user asks to write or rewrite docs or notes concisely or to apply a neutral informational tone.

Produce a Product Requirements Document (PRD) for a product feature. Use when the user asks to write a PRD, or to formalize a feature's scope, goals, user value and success metrics. Not for internal technical or architecture change proposals.