Team Agent Orchestration
affaan-m/ECC
Run team-based orchestration for agent squads: work items with owners and scope, agent Kanban state, branch isolation, control pane visibility, and merge gates.
Orchestrate a Steven Pinker-grounded workflow for teaching, explanatory writing, or material that must do both.
MITAuto-check passed
Install Pinker Clarity Workflow
$ npx skills add AHepi/DeepReason --skill pinker-clarity-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install AHepi/DeepReason pinker-clarity-workflow --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/AHepi/DeepReason.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/pinker-clarity-workflow .claude/skills/pinker-clarity-workflow && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "pinker-clarity-workflow" agent skill from https://github.com/AHepi/DeepReason/tree/main/.claude/skills/pinker-clarity-workflow into .claude/skills/pinker-clarity-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pinker-clarity-workflow", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/AHepi/DeepReason/tree/main/.claude/skills/pinker-clarity-workflowType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add AHepi/DeepReason --skill pinker-clarity-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install AHepi/DeepReason pinker-clarity-workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AHepi/DeepReason.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/pinker-clarity-workflow .agents/skills/pinker-clarity-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pinker-clarity-workflow" agent skill from https://github.com/AHepi/DeepReason/tree/main/.claude/skills/pinker-clarity-workflow into .agents/skills/pinker-clarity-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pinker-clarity-workflow", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add AHepi/DeepReason --skill pinker-clarity-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install AHepi/DeepReason pinker-clarity-workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AHepi/DeepReason.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/pinker-clarity-workflow .cursor/skills/pinker-clarity-workflow && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pinker-clarity-workflow" agent skill from https://github.com/AHepi/DeepReason/tree/main/.claude/skills/pinker-clarity-workflow into .cursor/skills/pinker-clarity-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pinker-clarity-workflow", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/AHepi/DeepReason.git --path .claude/skills/pinker-clarity-workflow--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add AHepi/DeepReason --skill pinker-clarity-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install AHepi/DeepReason pinker-clarity-workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AHepi/DeepReason.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/pinker-clarity-workflow .gemini/skills/pinker-clarity-workflow && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pinker-clarity-workflow" agent skill from https://github.com/AHepi/DeepReason/tree/main/.claude/skills/pinker-clarity-workflow into .gemini/skills/pinker-clarity-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pinker-clarity-workflow", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install AHepi/DeepReason pinker-clarity-workflowInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add AHepi/DeepReason --skill pinker-clarity-workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/AHepi/DeepReason.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/pinker-clarity-workflow .github/skills/pinker-clarity-workflow && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pinker-clarity-workflow" agent skill from https://github.com/AHepi/DeepReason/tree/main/.claude/skills/pinker-clarity-workflow into .github/skills/pinker-clarity-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pinker-clarity-workflow", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add AHepi/DeepReason --skill pinker-clarity-workflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install AHepi/DeepReason pinker-clarity-workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AHepi/DeepReason.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/pinker-clarity-workflow .opencode/skills/pinker-clarity-workflow && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pinker-clarity-workflow" agent skill from https://github.com/AHepi/DeepReason/tree/main/.claude/skills/pinker-clarity-workflow into .opencode/skills/pinker-clarity-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pinker-clarity-workflow", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
pinker-clarity-workflow- GitHub stars
- 141
- Token cost
- ~1.5k tokens
- SKILL.md length
- 751 words
- Files
- 2 (incl. references)
- Skills in repo
- 30
- Repo updated
- First seen
- Licence
- MIT
At a glance
Orchestrate a Steven Pinker-grounded workflow for teaching, explanatory writing, or material that must do both.
- Works in 8 steps: Ground truth. Extract the claims,… → Name the destination. State what the… → Build the model. Start from a… → …
- The user explicitly asks for a Pinker approach
- SKILL.md covers Route the request, Establish the communication…, Run the mixed workflow and Preserve these invariants, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Pinker Clarity Workflow is an agent skill from AHepi/DeepReason. Orchestrate a Steven Pinker-grounded workflow for teaching, explanatory writing, or material that must do both. Use when the user explicitly asks for a Pinker approach, invokes this skill, asks how Pinker's work bears on teaching or writing, or needs one coherent workflow that first secures understanding and then improves prose. Do not use merely to imitate Pinker's personal voice or to import his political and historical views.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/research-map.md`).
The licence is MIT.
When your agent uses it
- The user explicitly asks for a Pinker approach
- Invokes this skill
- Asks how Pinkers work bears on teaching
- Needs one coherent workflow that first secures understanding and then improves prose
Example prompts
- “/pinker-clarity-workflow”
Workflow steps
8 steps, taken from the first numbered list in SKILL.md.
- Ground truth. Extract the claims, evidence, distinctions, uncertainties, and source constraints. Research missing or current facts before…
- Name the destination. State what the audience should be able to explain, predict, distinguish, decide, or do afterward.
- Build the model. Start from a phenomenon, problem, puzzle, or consequential question. Organize the few ideas that explain it. Separate the…
- Bridge the knowledge gap. Pair each important generalization with a concrete example. Define necessary terms at first useful contact…
- Test understanding. Require paraphrase, prediction, comparison, application, or a counterexample when interaction permits. Do not use…
- Shape the prose. Put the problem before its solution, keep the topic visible, make relations between sentences recoverable, and prefer…
- Test the communication. Seek feedback from a representative reader or learner when available. If no human test occurred, say so and…
- Revise. Repair the content model before local wording. Then revise coherence, syntax, context, concision, rhythm, and usage in that order.
What it can do on your machine
Read from SKILL.md and the folder at commit 9607fba. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Pinker Clarity Workflow loads about 1.5k tokens when it runs, and up to ~5.5k if it reads all its reference files. Until then it costs about 114 tokens; SKILL.md has 751 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from AHepi/DeepReason at commit 9607fba, republished under its MIT licence (© AHepi). 751 words, ~1,498 tokens.
Download SKILL.mdSave it as
.claude/skills/pinker-clarity-workflow/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- pinker-clarity-workflow
- description
- Orchestrate a Steven Pinker-grounded workflow for teaching, explanatory writing, or material that must do both. Use when the user explicitly asks for a Pinker approach, invokes this skill, asks how Pinker's work bears on teaching or writing, or needs one coherent workflow that first secures understanding and then improves prose. Do not use merely to imitate Pinker's personal voice or to import his political and historical views.
Pinker Clarity Workflow
Produce reader or learner understanding before polishing expression. Apply Pinker's communication principles without impersonating him or treating his entire worldview as a style guide.
Route the request
Identify the operating mode from the requested outcome:
- Method: Explain how to teach, how to write, or how the two fit together. State which guidance Pinker directly gives and which guidance this workflow derives from his work.
- Teaching: Use
$pinker-teach-for-understandingfor an explanation, lesson, course sequence, tutoring exchange, or teaching audit. - Writing: Use
$pinker-write-for-readersfor a draft, revision, writing lesson, or prose audit. - Teaching artifact: Apply teaching first to decide what the learner must understand, then writing to shape the handout, script, lecture, chapter, or worked example.
- Research about Pinker: Read references/research-map.md. Verify time-sensitive claims against current primary sources.
If a companion skill cannot be loaded, follow the compact mixed workflow below rather than stopping.
Establish the communication contract
Determine the real-world subject, intended audience, desired change in understanding or ability, medium, length, register, and non-negotiable content. Infer ordinary details when safe. Ask only when a missing choice would materially change the result.
Treat the audience as intelligent but not already initiated into the writer's or teacher's guild. Record what they likely know, what they need next, and which terms or premises may be invisible to an expert.
Run the mixed workflow
- Ground truth. Extract the claims, evidence, distinctions, uncertainties, and source constraints. Research missing or current facts before drafting. Fluency is not evidence.
- Name the destination. State what the audience should be able to explain, predict, distinguish, decide, or do afterward.
- Build the model. Start from a phenomenon, problem, puzzle, or consequential question. Organize the few ideas that explain it. Separate the best current conclusion from live uncertainty.
- Bridge the knowledge gap. Pair each important generalization with a concrete example. Define necessary terms at first useful contact. Supply hidden premises and identify pronoun or acronym referents.
- Test understanding. Require paraphrase, prediction, comparison, application, or a counterexample when interaction permits. Do not use assent or smooth repetition as the test.
- Shape the prose. Put the problem before its solution, keep the topic visible, make relations between sentences recoverable, and prefer actors and actions when abstractions hide them.
- Test the communication. Seek feedback from a representative reader or learner when available. If no human test occurred, say so and provide targeted test questions instead of claiming validation. For a standalone learner-facing artifact, put that disclosure in the handoff note rather than interrupting the artifact itself.
- Revise. Repair the content model before local wording. Then revise coherence, syntax, context, concision, rhythm, and usage in that order.
Show full SKILL.md (309 more words)Show less
Preserve these invariants
- Preserve truth, warranted qualification, formal validity, authorial intent, accessibility, and genre obligations even when they conflict with elegance.
- Remove defensive or status-signaling clutter, not uncertainty that changes the claim.
- Use concrete scenes to ground abstraction; do not purge abstraction that has earned a stable meaning.
- Use classic style as a useful default for exposition, not as a universal law for contracts, procedures, formal proofs, safety warnings, poetry, or fiction.
- Keep Pinker's directly stated advice separate from inferences based on his research, practices observed in his courses, and independent learning science.
- Do not derive a general pedagogy from Pinker's contested claims about linguistic nativism, evolutionary psychology, violence, progress, or politics.
- Do not imitate Pinker's distinctive voice. Transfer principles such as reader modeling, concreteness, coherence, feedback, and revision.
- For AI-produced prose, verify claims and sources and run an anti-banality pass: replace canned framing with precise observations, examples, and relationships supported by the subject matter.
Explain the method honestly
When the user asks how the workflow works, lead with its core: teaching and writing are both problems of reconstructing enough shared context for another mind to see a model of reality. Then explain the difference: teaching must produce and test a change in understanding; writing must encode the needed context and relations without live conversational repair.
Attribute classic style to Francis-Noël Thomas and Mark Turner as adopted and developed by Pinker. Attribute the term “curse of knowledge” to Colin Camerer, George Loewenstein, and Martin Weber; describe Pinker as applying and popularizing it for writing and teaching.
Research reference
Read references/research-map.md when explaining provenance, evaluating a proposed Pinker principle, updating the workflow, or answering broad questions about his body of work. It maps all thirteen books recognized in his current official biography, the directly relevant teaching and writing sources, the 2025–2026 common-knowledge work, and the boundaries that prevent attribution drift.
© AHepi, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in .claude/skills/pinker-clarity-workflow of AHepi/DeepReason.
- SKILL.md
- references/research-map.md
Open the folder on GitHubat commit 9607fba
Compare with similar skills
Pinker Clarity Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Pinker Clarity Workflow this skillAHepi/DeepReason | 141 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Team Agent Orchestrationaffaan-m/ECC | 276k | 1 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Orca Orchestrationstablyai/orca | 88k | — | ~916 | Automated safety check: Pass | MIT | |
| Agent Orchestrator Taskruvnet/ruflo | 74k | 2 repos | ~1k | Automated safety check: Pass | MIT | |
| Plan Orchestrateaffaan-m/ECC | 276k | 1 repos | ~4.5k | Automated safety check: Pass | MIT | |
| Orchestratesickn33/agentic-awesome-skills | 47k | 1 repos | ~692 | Automated safety check: Pass | MIT |
Similar skills
Orca Orchestration
stablyai/orca
Coordinate supervised Orca workers: threaded messages, blocking ask/reply, task dispatch, worker_done/escalation waits, task DAGs, decision gates, coordinator…
Agent Orchestrator Task
ruvnet/ruflo
Agent skill for orchestrator-task - invoke with $agent-orchestrator-task
Plan Orchestrate
affaan-m/ECC
Read a plan document, decompose it into steps, design a per-step agent chain from the ECC catalogue, and emit ready-to-paste /orchestrate custom prompts.
Orchestrate
sickn33/agentic-awesome-skills
Coordinate focused subagents on substantial work, keep their ownership non-overlapping, and integrate verified results.
- Official
Teach
cursor/plugins
Explain a body of work plainly so a person actually understands it.
More from AHepi/DeepReason
All 30 skills in this repoPinker Teach For Understanding
AHepi/DeepReason
Design, deliver, or audit explanations and lessons with a Pinker-informed focus on phenomena, the curse of knowledge, concrete models, active reasoning, feedback, and revision.
Pinker Write For Readers
AHepi/DeepReason
Draft, revise, teach, or audit expository prose using Pinker's cognitive approach to style: classic presentation, reader modeling, curse-of-knowledge repair, coherent information order, deliberate…
Example Battery
AHepi/DeepReason
Build a battery of concrete instances BEFORE writing or evaluating any definition, pin, or semantic clause (Reed step 1).
Authoring Skills
AHepi/DeepReason
Rules for writing, editing, and retiring skill and workflow files for LLM agents.
Deepreason Orchestrator
AHepi/DeepReason
Entry point for any DeepReason problem. An agent skill from AHepi/DeepReason.
Dr Audit Orchestrator
AHepi/DeepReason
Router for the code-audit family. An agent skill from AHepi/DeepReason.
Questions about Pinker Clarity Workflow
What does Pinker Clarity Workflow do?
Orchestrate a Steven Pinker-grounded workflow for teaching, explanatory writing, or material that must do both. Pinker Clarity Workflow is an agent skill from AHepi/DeepReason. Orchestrate a Steven Pinker-grounded workflow for teaching, explanatory writing, or material that must do both.
When should I use Pinker Clarity Workflow?
Pinker Clarity Workflow fits situations like: the user explicitly asks for a Pinker approach; invokes this skill; asks how Pinkers work bears on teaching; needs one coherent workflow that first secures understanding and then improves prose.
How do I install Pinker Clarity Workflow in Claude Code?
Run `npx skills add AHepi/DeepReason --skill pinker-clarity-workflow -a claude-code`. Or copy the skill folder (.claude/skills/pinker-clarity-workflow in AHepi/DeepReason) into .claude/skills/pinker-clarity-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Pinker Clarity Workflow in Codex?
Run `npx skills add AHepi/DeepReason --skill pinker-clarity-workflow -a codex`. Or copy the skill folder (.claude/skills/pinker-clarity-workflow in AHepi/DeepReason) into .agents/skills/pinker-clarity-workflow in your project. Codex loads it when a task matches its description.
Can I use Pinker Clarity Workflow in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add AHepi/DeepReason --skill pinker-clarity-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pinker-clarity-workflow, .gemini/skills/pinker-clarity-workflow, .github/skills/pinker-clarity-workflow and .opencode/skills/pinker-clarity-workflow in your project.
What does Pinker Clarity Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Pinker Clarity Workflow is instructions for the agent only.
Does Pinker Clarity Workflow access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Pinker Clarity Workflow safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Pinker Clarity Workflow use?
Pinker Clarity Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Pinker Clarity Workflow use?
About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4k tokens, read only when the agent opens those files.
What are the alternatives to Pinker Clarity Workflow?
Skills that share tags, products or a category with Pinker Clarity Workflow: Team Agent Orchestration (affaan-m/ECC, 276k stars), Orca Orchestration (stablyai/orca, 88k stars), Agent Orchestrator Task (ruvnet/ruflo, 74k stars) and Plan Orchestrate (affaan-m/ECC, 276k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Pinker Clarity Workflow?
AHepi (a GitHub user) maintains it in AHepi/DeepReason, which has 141 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on September 10, 2026.
Source: AHepi/DeepReason on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.