prior-auth-packet-builder
$
npx mdskill add openai/openai-agents-python/prior-auth-packet-builderAssemble a concise prior authorization packet by synthesizing case data and payer policies.
- Streamlines the creation of necessary documentation for payer review.
- Interacts with local case files and policy documentation directories.
- Determines necessary human verification steps and case ownership.
- Generates structured Markdown files for immediate review and action.
SKILL.md
.github/skills/prior-auth-packet-builderView on GitHub ↗
--- name: prior-auth-packet-builder description: Build a concise prior authorization packet from local case files and payer policy docs. --- # Prior Auth Packet Builder Use this skill when a case requires prior authorization review, referral validation, imaging review, or payer-specific policy checks. ## Workflow 1. Inspect `case/scenario.json` and `case/transcript.txt`. 2. Use `rg` against `policies/` to find payer, prior auth, referral, imaging, and PPO guidance. 3. Read only the most relevant policy files. 4. Create `output/policy_findings.md` with: - case summary - matched policy files - prior auth determination - referral determination - missing information 5. Create `output/human_review_checklist.md` with: - what a human reviewer should verify - what to tell the patient - what queue should own the case ## Rules - Use targeted `rg` searches over broad file reads. - Only cite policy files you actually inspected. - Keep outputs concise and operational. - If referral status is pending and prior auth is unclear, recommend human review.
More from openai/openai-agents-python
- code-change-verificationRun the mandatory verification stack when changes affect runtime code, tests, or build/test behavior in the OpenAI Agents Python repository.
- credit-note-fixerFix the tiny credit-note formatting bug and rerun the exact targeted test command.
- csv-workbenchAnalyze CSV files in /mnt/data and return concise numeric summaries.
- docs-syncAnalyze main branch implementation and configuration to find missing, incorrect, or outdated documentation in docs/. Use when asked to audit doc coverage, sync docs with code, or propose doc updates/structure changes. Only update English docs under docs/** and never touch translated docs under docs/ja, docs/ko, or docs/zh. Provide a report and ask for approval before editing docs.
- examples-auto-runRun python examples in auto mode with logging, rerun helpers, and background control.
- final-release-reviewPerform a release-readiness review by locating the previous release tag from remote tags and auditing the diff (e.g., v1.2.3...<commit>) for breaking changes, regressions, improvement opportunities, and risks before releasing openai-agents-python.
- implementation-strategyDecide how to implement runtime and API changes in openai-agents-python before editing code. Use when a task changes exported APIs, runtime behavior, serialized state, tests, or docs and you need to choose the compatibility boundary, whether shims or migrations are warranted, and when unreleased interfaces can be rewritten directly.
- openai-knowledgeUse when working with the OpenAI API (Responses API) or OpenAI platform features (tools, streaming, Realtime API, auth, models, rate limits, MCP) and you need authoritative, up-to-date documentation (schemas, examples, limits, edge cases). Prefer the OpenAI Developer Documentation MCP server tools when available; otherwise guide the user to enable `openaiDeveloperDocs`.
- playwrightUse when the task requires capturing or automating a real browser from the terminal.
- pr-draft-summaryCreate the required PR-ready summary block, branch suggestion, title, and draft description for openai-agents-python. Use in the final handoff after moderate-or-larger changes to runtime code, tests, examples, build/test configuration, or docs with behavior impact; skip only for trivial or conversation-only tasks, repo-meta/doc-only tasks without behavior impact, or when the user explicitly says not to include the PR draft block.