Agent skill · Code Review & Quality

ci-workflow

Use as the entry point for any Critical Inquiry (CI) essay. Routes to the right CI sub-skill based on where you are in the lifecycle and which format (Article, Critical Response, Review) fits. CI is an interdisciplinary journal of criticism and theory in the arts and humanities; the router's job is to keep the project pointed at a bold theoretical intervention with interdisciplinary stakes. It dispatches; it does not draft content.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ci-workflow --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: Critical-Inquiry-Skills/skills/ci-workflow/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Critical Inquiry Workflow Router (ci-workflow) The orchestrator for a *Critical Inquiry* submission. Figure out the stage and the **format**, then send the user to the matching skill. CI is **interdisciplinary criticism and theory** — not a single discipline's house organ — so the router's first job is to make sure the essay is built around a **theoretical intervention** that matters across fields, not a competent reading with no stakes. ## When to trigger - Starting a new CI essay and unsure where to begin - Mid-project and unsure which skill applies next - Deciding among the **three formats** (Article, Critical Response, Review) - Returning with a decision letter (route to `ci-revision-and-response`) ## First question: which format? | Situation | Format | Route to | |-----------|--------|----------| | Full original argument, interdisciplinary stakes | **Article** (≤ 9,500 words) | normal pipeline below | | Reply to or debate with a published CI piece | **Critical Response** (≤ 3,000 words) | `ci-argument-and-intervention` + `ci-scholarly-positioning` | | Short notice of a book/exhibition | **Review** (≤ 500 words) | `ci-writing-style` + `ci-submission` | | A themed cluster of e

What's inside
Steps it walks through
  1. When to trigger
  2. First question: which format?
  3. Routing map (stage → skill)
  4. Default order
  5. Symptom → route (when the stage is unclear)
  6. Two routing mistakes to catch early
  7. Anti-patterns
  8. Router pass for Critical Inquiry
  9. Output format
  10. Supplementary resources
More from Awesome-Journal-Skills
All skills →
About this skill
What does the ci-workflow skill do?

Use as the entry point for any Critical Inquiry (CI) essay. Routes to the right CI sub-skill based on where you are in the lifecycle and which format (Article, Critical Response, Review) fits. CI is an interdisciplinary journal of criticism and theory in the arts and humanities; the router's job is to keep the project pointed at a bold theoretical intervention with interdisciplinary stakes. It dispatches; it does not draft content.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ci-workflow --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going