Find the best skills for |

Fit first-order dynamic models to experimental step response data and extract K (gain) and tau (time constant) parameters.

Problem-solving strategies for first order odes in odes pdes

First principles analysis. USE WHEN first principles, fundamental, root cause, decompose. SkillSearch('firstprinciples') for docs.

Fitbit fitness data integration. Use when the user wants fitness insights, workout summaries, step counts, heart rate data, sleep analysis, or to ask questions about their Fitbit activity data. Provides AI-powered analysis of fitness metrics.

Fitbit health and fitness data integration. Fetch steps, heart rate, sleep, activity, calories, and trends from Fitbit Web API. Generate automated health reports and alerts. Requires FITBIT_CLIENT_ID, FITBIT_CLIENT_SECRET, FITBIT_ACCESS_TOKEN, FITBIT_REFRESH_TOKEN.

分析运动数据、识别运动模式、评估健身进展，并提供个性化训练建议。支持与慢性病数据的关联分析。

Use when you have lint errors, formatting issues, or before committing code to ensure it passes CI.

Guide for fixing bugs in ClaudeBar following Chicago School TDD and rich domain design. Use this skill when:\n(1) User reports a bug or unexpected behavior\n(2) Fixing a defect in existing functionality\n(3) User asks \

Fetch GitHub CI failure information, analyze root causes, reproduce locally, and propose a fix plan. Use `/fix-ci` for current branch or `/fix-ci u003crun-idu003e` for a specific run.

Fix all CVEs in the Okteto CLI Docker image by scanning with Trivy and updating vulnerable dependencies and binaries

Fix Dependabot security alerts by updating vulnerable npm dependencies. Use when the user mentions \

dependabotから上がってきた複数のPRを一括で解決し、まとめPRを作成する。dependabotのPR対応を依頼された時に使用。

Fix a GitHub issue by number. Use when asked to fix GitHub issues.

Use when working on a GitHub issue - fetches issue details, analyzes codebase, implements fix following project methodology

Use when asked to fix short descriptions of Python type members.

Fix a failing PR by analyzing CI logs and fixing errors. Autonomous workflow that identifies failures, rebases, fixes issues, and pushes.

Verify fix commits address audit findings without new bugs

Fix the \

Fix accessibility issues.

Diagnose and fix bugs through systematic investigation, root cause analysis, and targeted validation. Use when something is broken, errors occur, performance degrades, or unexpected behavior manifests.

Ship correct, complete metadata.

Fix animation performance issues.

Analyze and fix failed GitHub Actions CI jobs for the current branch/PR. Use when CI checks fail, PR checks show failures, or you need to diagnose lint/type/test errors and verify fixes locally.

Generate fixture generator operations. Auto-activating skill for Test Automation.\nTriggers on: fixture generator, fixture generator\nPart of the Test Automation skill category. Use when working with fixture generator functionality. Trigger with phrases like \

This skill should be considered when you need to repair an infeasible or non-optimal flexible job scheduling planning schedule into a downtime-feasible, precedence-feasible one while keep no worse policy budget.

Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels.

Generate flame graph generator operations. Auto-activating skill for Performance Testing.\nTriggers on: flame graph generator, flame graph generator\nPart of the Performance Testing skill category. Use when working with flame graph generator functionality. Trigger with phrases

Flask Blueprint Creator - Auto-activating skill for Backend Development.\nTriggers on: flask blueprint creator, flask blueprint creator\nPart of the Backend Development skill category.

Flight canvas for comparing flights and selecting seats.\nUse when users need to browse flight options and book seats.

Create flink job creator operations. Auto-activating skill for Data Pipelines.\nTriggers on: flink job creator, flink job creator\nPart of the Data Pipelines skill category. Use when working with flink job creator functionality. Trigger with phrases like \

Manage Flipt feature flags - list, create, enable/disable, and configure rollout rules. Use when you need to control feature flag state or set up segmented rollouts.

Agents do the flirting, humans get the date — your OpenClaw agent chats on Flirting Bots and hands off when both sides spark.

Detect flood events by comparing water levels to thresholds. Use when determining if flooding occurred, counting flood days, aggregating instantaneous data to daily values, or classifying flood severity.

Use when you need to run Flow type checking, or when seeing Flow type errors in React code.

John Carmack-level implementation review via rp-cli for current branch changes. Use when reviewing code changes, PRs, or implementations. Triggers on mentions of code review, implementation review, or PR review.

Interview user in-depth about a spec, bead, or feature idea to extract complete implementation details. Use when user wants to flesh out a spec, refine requirements, discuss technical details, clarify a feature before building, or asks to be interviewed about their idea.

Manage .flow/ tasks and epics. Triggers: 'show me my tasks', 'list epics', 'what tasks are there', 'add a task', 'create task', 'what's ready', 'task status', 'show fn-1-add-oauth'. NOT for /flow-next:plan or /flow-next:work.

Show epic dependency graph and execution order. Use when asking 'what's blocking what', 'execution order', 'dependency graph', 'what order should epics run', 'critical path', 'which epics can run in parallel'.

Epic completion review - verifies all epic tasks implement spec requirements. Triggers on /flow-next:epic-review.

Export RepoPrompt context for external LLM review (ChatGPT, Claude web, etc.). Use when you want to review code or plans with an external model. Triggers on /flow-next:export-context.

John Carmack-level implementation review via RepoPrompt or Codex. Use when reviewing code changes, PRs, or implementations. Triggers on /flow-next:impl-review.

Interview user in-depth about an epic, task, or spec file to extract complete implementation details. Use when user wants to flesh out a spec, refine requirements, or clarify a feature before building. Triggers on /flow-next:interview with Flow IDs (fn-1-add-oauth,

Create structured build plans from feature requests or Flow IDs. Use when planning features or designing implementation. Triggers on /flow-next:plan with text descriptions or Flow IDs (fn-1-add-oauth, fn-1-add-oauth.2, or legacy fn-1, fn-1.2, fn-1-xxx, fn-1-xxx.2).

Carmack-level plan review via RepoPrompt or Codex. Use when reviewing Flow epic specs or design docs. Triggers on /flow-next:plan-review.

Scaffold repo-local Ralph autonomous harness under scripts/ralph/. Use when user runs /flow-next:ralph-init.

Token-efficient codebase exploration using RepoPrompt CLI. Use when user says \

Optional local install of flowctl CLI and CLAUDE.md/AGENTS.md instructions. Use when user runs /flow-next:setup.

Manually trigger plan-sync to update downstream task specs after implementation drift. Use when code changes outpace specs.