codex-skill
starsforks
How to install codex-skill?
cmertdalli/polisci-review/codex-skill
$npx -y skills add cmertdalli/polisci-review --skill codex-skillRun a political science pre-submission audit with journal-aware personas, stage-aware standards, and evidence-grounded issue reporting.
SKILL.md
| 1 | # PoliSci Review |
| 2 | |
| 3 | This installed skill is self-contained. |
| 4 | |
| 5 | Read the canonical files in this order: |
| 6 | |
| 7 | 1. `./core/invocation-spec.md` |
| 8 | 2. `./core/journal-manifest.json` |
| 9 | 3. `./core/paper-discovery.md` |
| 10 | 4. `./core/track-stage-rules.md` |
| 11 | 5. `./core/issue-taxonomy.md` |
| 12 | 6. `./core/references/guardrails.md` |
| 13 | 7. `./core/references/journal-signals.md` |
| 14 | 8. `./core/references/journal-personas.md` |
| 15 | 9. all relevant files in `./core/modules/` |
| 16 | 10. `./core/report-template.md` |
| 17 | |
| 18 | Workflow: |
| 19 | |
| 20 | 1. Parse user arguments using the canonical invocation contract. |
| 21 | 2. Discover the manuscript and linked component files. Prefer `.tex` whenever available; support `.docx`, `.md`, `.txt`, and text-readable `.pdf` on a best-effort basis. |
| 22 | 3. Detect stage and track when omitted. |
| 23 | 4. Apply the selected journal persona and the 9-module audit structure. |
| 24 | 5. Write two output files in the main manuscript directory when a manuscript path is available; otherwise write them in the current working directory: |
| 25 | - `review-report.md` following `./core/report-template.md` |
| 26 | - `review-report.json` conforming to `./core/issue-schema.json` |
| 27 | 6. Before finishing, make sure `review-report.json` is valid JSON and briefly confirm the paths you wrote. |
| 28 | |
| 29 | Guardrails: |
| 30 | |
| 31 | - Do not merely describe the outputs. Write the files unless the environment prevents file output. |
| 32 | - If the environment cannot write files, say so explicitly and return the Markdown report plus the JSON artifact directly in the response. |
| 33 | - Every issue must include a `module`, a location anchor, evidence status, and a `journal_policy_ref`. |
| 34 | - Distinguish `verified inconsistency`, `inferred absence`, and `needs human check`. |
| 35 | - Do not claim a missing bibliography entry, broken reference, or absent robustness check without checking the files. |
| 36 | - If `.docx` or `.pdf` content cannot be read reliably, say so and request exported text instead of guessing. |
| 37 | - Do not review proposals as if they were completed articles. |
| 38 | - Use `PA` for `Political Analysis`. |
People who liked this also viewed
6 picksType
- find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 2026
- grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026
- vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026
- setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026
- triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026
