From the author
Use when parallelizing loops or tasks with OpenMP: parallel for, schedules, reductions, data sharing, simd, target offload, OMP_* tuning, or false sharing. Not for multi-node work: use mpi.
Install
npx skills add OutlineDriven/outline-driven-development --skill openmp -a claude-code
Installs to .claude/skills/openmp/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 82
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- mpiOutlineDriven/outline-driven-developmentUse when writing or debugging MPI programs: sends and receives, collectives, non-blocking requests, communicators, MPI-IO, hybrids with OpenMP, or mpirun launches. Not for threads alone: use openmp.Writing★ 54
- orchestrate-ompdsebban/skillsCoordinate OMP subagents on substantial work. Use when parallel discovery, specialist review, or clearly partitioned implementation will shorten or strengthen the result; skip trivial tasks.Planning★ 68
- parallel-processingcxcscmu/SkillLearnBenchParallel processing with joblib for grid search and batch computations. Use when speeding up computationally intensive tasks across multiple CPU cores.Productivity★ 91
- diamond-taskOutlineDriven/outline-driven-developmentUse when one issue or PR is too large for a worker and partitions into disjoint write sets. Not for independent parallel tasks: use parallel-launch. No remote or irreversible changes.Productivity★ 54
- mutual-syncOutlineDriven/outline-driven-developmentUse when the user and agent may hold different pictures of current state after a gap, sync request, or exposed stale claim. Not for persistence: use memory-update.Productivity★ 54
- parallelericrisco/rsc-harnessUse when two or more pieces of work are genuinely independent — disjoint files, no shared state, no ordering edge — and should fan out across subagents, then be gathered and reconciled under a combined test suite. Decides WHAT can run concurrently; NOT the isolation it runs in (that is `worktrees`), NOT the per-unit TDD loop (that is `implement`).Testing★ 255
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in