← ClaudeAtlas

prepare-assessment-aid-positionlisted

Structures the clinical pharmacology content of an assessment aid or applicant's position document — the tabulated summary an agency requests to facilitate their review. Extracts every CP claim, traces it to its source document, verifies internal consistency, and flags any position statement that crosses into a clinical or regulatory decision. Use when asked to prepare or review an assessment aid's CP section. Do not use for drafting agency responses, for meeting preparation, or for taking a position.
malekokour/clinpharm-pmx-skills · ★ 6 · AI & Automation · score 77
Install: claude install-skill malekokour/clinpharm-pmx-skills
# Assessment Aid Applicant's Position Preparation Assessment Aid applicant's position — produce a source-linked finding register a qualified reviewer can act on. Every finding carries a locator, a severity, and a detection path. The register arrives open; only a named human may close an item. > **Skills review, reconcile, verify, structure and flag. Qualified humans > decide, approve, sign off, submit and act.** ## Who this is for Clinical pharmacology or pharmacometrics practitioners working in **Regulatory evidence package** who need a bounded, repeatable review of this L3 task — not a decision, not a draft to submit, and not a substitute for the accountable human owner. ## When to use this skill - "Prepare the CP section of the assessment aid for this submission" - "Check the assessment aid positions against our source data" - "Does every CP claim in the assessment aid trace to a filed document?" ## When NOT to use this skill These are close neighbours. Route them elsewhere and say so: | Request | Why not this skill | Where it belongs | |---|---|---| | Prepare for an agency meeting | Meeting preparation, different scope | prepare-meeting-strategy | | Draft a response to an agency question | Response drafting | map-agency-question-evidence | | Take a position on a CP question | A regulatory decision | Qualified reviewer | ## Required inputs Ask for these by artifact, not by category. If one is missing, say which check it disables rather than proceeding silently.