Claude Code Skills·Claude Skills·The open SKILL.md registry for Claude
ClaudSkills › General › Page 808

General-Purpose Claude Skills (Page 808 of 2095)

Productivity, automation, knowledge management, integrations, AI tooling, and general-purpose skills for Claude Code.

125,692 skills · updated 2026-10-25 · showing 48421–48480 of 125,692 by quality score

Sub-topics:Ai Tooling (5,608)Automation (5,509)Integrations (4,833)Business Ops (3,213)Design Creative (2,312)Orchestration Frameworks (2,152)Agents Skills Meta (2,094)Legal Compliance (1,836)

For the full experience including quality scoring and one-click install features for each skill — upgrade to Pro.

Fix Zod schema import issues during Flow to Output SDK migration. Use when seeing "incompatible schema" errors, type errors at step boundaries, or when migrating files that import…
Execute an approved plan with subagents, TDD, and two-stage review. Invoke with /flow-execute to resume or when plan exists without an active spec session.
Przygotowanie sekcji INTEGRATIONS Flow Explorera dla trybow COMPACT i DEEP: zewnetrzne systemy, kanaly, targety, transport, payload, error handling i handoff.
Kontrakt odpowiedzi Flow Explorera - JSON-only, Overview plus aktywne sekcje sectionModes, compact/deep, source refs, confidence i visibility limits.
Author NULL-safe, type-correct, performance-aware Formula resources and condition expressions in Flow: lazy re-evaluation, BLANKVALUE/ISBLANK guards, ISPICKVAL vs =,…
Orchestrate SDLC phase gate validation with multi-agent review and comprehensive reporting
Use when establishing operational standards for a Salesforce Flow portfolio, including naming conventions, ownership, version discipline, retirement of stale flows, and release…
Compute and budget governor-limit consumption per Flow type with worked math: SOQL, DML rows, CPU time, heap.
Orchestrate autonomous issue-to-code implementation using existing tools and agents with bounded iteration
Orchestrate handoff validation between SDLC phases and tracks (Discovery→Delivery, Delivery→Ops, phase transitions)
Call external HTTP APIs directly from Flow using HTTP Callout actions (no Apex), handling auth, schema, and errors. NOT for complex Apex-based integration logic.
Orchestrate hypercare monitoring period with 24/7 support, SLO tracking, and rapid issue response
John Carmack-level implementation review via rp-cli for current branch changes. Use when reviewing code changes, PRs, or implementations.
Orchestrate production incident triage, escalation, resolution, and post-incident review using ITIL best practices
Analisa o projeto inteiro e inicializa a pasta ./flow/ com um documento de estrutura geral do projeto e, opcionalmente, flows individuais de cada feature.
Initialize Flow projects from scratch, migrate existing docs, or update old structures. Use when user says "start flow", "initialize", "migrate to flow", "set up flow project".
Interview user in-depth about a spec, bead, or feature idea to extract complete implementation details.
Orchestrate dual-track iteration with synchronized Discovery (next) and Delivery (current) workflows
Orchestrate Knowledge Transfer flow with assessment, documentation, shadowing, validation, and handover
Use when Flows must stay healthy at large data volumes: total SOQL rows returned per transaction, unbounded Get Records, collection sizing, scheduled or record-triggered scale,…
Cách lái SEOSONA Flow (gen ẢNH/VIDEO/b-roll) qua Local MCP server (mcp-local/) — cho agent HOẶC SEOSONA Video AI V2 gọi.
Navigate Flow projects with dashboard-first pattern. Use when user asks about status, current work, what's next, or project progress. Read-only skill.
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…
Audit `.flow/memory/` entries against the current codebase and decide Keep / Update / Consolidate / Replace / Delete per entry.
Synthesize the current conversation context into a flow-next epic spec at `.flow/specs/.md` via `flowctl epic create + epic set-plan` — agent-native, source-tagged, with…
Decision-map discovery for one oversized unclear idea before capture. Resolve one decision per invocation, brief for capture.
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',…
Drive any UI surface like a real user - a web app, a Chromium-backed desktop app (Electron / WebView2, reached over CDP), or a genuinely native app (macOS AppKit/SwiftUI, or a…
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.
Recommend the smallest sufficient flow-next workflow from the starting state. Stateless router. Use when unsure which command or stage applies next.
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.
Autonomous PR babysitter tick. Fixes CI, resolves feedback, merges when converged, closes the spec, releases. Emits LAND_VERDICT. Use when asked to land PRs.
Render a cognitive-aid PR body from flow-next state and open via gh. Triggers on /flow-next:make-pr with optional spec id and flags (--draft, --ready, --no-mermaid, --base ,…
Build a semantic feature index of the repo via clawpatch map (opt-in). Use when asked to map the repo.
Migrate pre-fn-30 legacy flat memory files (`.flow/memory/pitfalls.md`, `conventions.md`, `decisions.md`) into the categorized YAML schema.
Single-tick autonomous build-loop conductor. Advances one ready spec one stage per tick, emits PILOT_VERDICT. Use when asked to pilot a spec or backlog.
Create structured build plans from feature requests or Flow IDs. Use when planning features or designing implementation.
Carmack-level plan review via RepoPrompt or Codex. Use when reviewing Flow epic specs or design docs. Triggers on /flow-next:plan-review.
Comprehensive codebase assessment for agent and production readiness. Scans 8 pillars (48 criteria), verifies commands work, checks GitHub settings.
Live-app QA pass derived from the spec. Drives the running app, files P0/P1/P2 findings with evidence, emits a YES or NO qa_verdict receipt.
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 "use rp to..." or "use repoprompt to..." followed by explore, find, understand, search, or similar…
Optional local install of flowctl CLI and CLAUDE.md/AGENTS.md instructions. Use when user runs /flow-next:setup.
Spec completion review - verifies all spec tasks implement the spec requirements. Triggers on /flow-next:spec-completion-review.
Manually trigger plan-sync to update downstream task specs after implementation drift. Use when code changes outpace specs.
Project a flow-next spec to a tracker issue (Linear first, GitHub next) and reconcile body/status/comments two-way — projection, not coordination.
Execute a Flow epic or task systematically with git setup, task tracking, quality checks, and commit workflow. Use when implementing a plan or working through a spec.
Manage git worktrees (create/list/switch/cleanup) and copy .env files. Use for parallel feature work, isolated review, clean workspace, or when user mentions worktrees.
Flow Orchestration admin: stage configuration, step assignment, background steps, interactive steps, evaluation flows, work items, pause/resume.
Flow Orchestration design patterns — multi-stage, multi-step flows where each step is itself an autolaunched flow or a screen flow assigned to a user / queue, with Work Items…
Decompose and execute large changes, migrations, or multi-issue fixes in parallel with quality gates
Tune Flow runtime performance: pick Before-Save over After-Save, consolidate Get Records, eliminate loop-DML, cache lookups, split with Scheduled Paths, and measure actual…
Create structured build plans from feature requests, bug reports, or Beads issue IDs. Use when planning features, designing implementation, preparing work breakdown, or when given…
Plan phases, tasks, and iterations. Use when structuring new work, adding features, or organizing development plans.
Build reactive Flow screens where one component updates another without navigation using reactive formulas and component outputs. NOT for Aura-based screens.
Handle code review feedback with technical rigor. Don't blindly agree - verify before implementing.
Diagnose and prevent UNABLE_TO_LOCK_ROW + parent-record contention in record-triggered, scheduled, and screen flows by mapping the implicit lock chain and applying decouple…
Reason about how record-triggered flows interleave with the Salesforce Save Order (validation, before-save flows, before triggers, duplicate rules, after-save flows, workflow,…
Search all 125,692 General skills →