skills/writing-research/applying-imrad/SKILL.md
Decide whether IMRaD fits, review an IMRaD draft, transform mixed material into IMRaD, or draft a new evidence-traceable IMRaD output without fabricating results.
npx skillsauth add narumiruna/agent-skills applying-imradInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use IMRaD only when a clear question, a real or responsibly inferable method, results or explicitly non-empirical outputs, and interpretation all exist. Do not force it onto simple explanations, tutorials, brainstorming, or style-only edits.
| Mode | Trigger | Deliverable | | --- | --- | --- | | Detector | applicability, readiness, or section-gap question | fit verdict and gap analysis, not a full article | | Reviewer | existing IMRaD draft needs audit | prioritized structural/evidence findings, not a rewrite unless asked | | Recomposer | notes or mixed material must become IMRaD | full transformed draft | | Writer | new research-style output is requested | full new draft |
Infer the mode when clear. Ask only when the choice materially changes the deliverable.
inferred, hypothetical, expected, or simulated.Abstract or Conclusion only when requested.Classify each section as explicit, partial, inferable, or unavailable. Return applicability (high, medium, or low), required assumptions, and one recommendation: full IMRaD, partial IMRaD, or no IMRaD. Do not turn unavailable evidence into results.
Check section presence/order, boundary purity, claim traceability, empirical labels, and question→method→result→interpretation linkage. Lead with the overall verdict, then findings with severity, section, problem, impact, and specific fix. Mention strengths only when they help preserve sound structure.
Extract the question and method, separate findings from interpretation, compose the four sections in exact order, expose assumptions in Methods, and validate claim traceability before handoff.
Define the question/objective, describe the actual or explicitly analytical method, present available outputs objectively, and interpret only those outputs. If an empirical method or results are missing, do not invent them; either produce clearly labeled non-empirical work or explain why a responsible full IMRaD draft is unavailable.
Finish with the requested artifact or verdict first, followed by material assumptions, evidence gaps, and section-boundary caveats.
development
Score or compare one or more agent skills across trigger clarity, workflow actionability, safety boundaries, verification rigor, incremental knowledge value, and leanness. Use only when the user explicitly asks for ratings, numerical quality scores, rubric-based scorecards, or scored comparisons; use creating-agent-skills for unscored reviews or revisions.
development
Assess or improve an existing codebase's architecture when the user asks about module boundaries, coupling, scattered ownership, testability, change locality, deep modules, seams, or behavior-preserving structural refactoring. Use for cross-module design rather than ordinary diff review or a confirmed edge-case bug fix.
development
Perform read-only security audits, vulnerability assessments, or threat-focused reviews of diffs, pull requests, code paths, or explicitly scoped repositories when security is the primary objective or acceptance criterion. Use reviewing-code for ordinary review with baseline security coverage and hardening-code-paths for fixing confirmed findings.
development
Run iterative multi-reviewer panels over a code diff, verify their findings, apply explicitly authorized fixes, and re-review the updated change until it passes or reaches a stopping condition. Use when the user asks for a panel loop, multi-model code-review consensus, or a review-fix-re-review cycle.