Compare local case files with insurer policies to prepare a concise prior authorization packet, covering approval requirements, referrals, missing information, and a checklist for staff reviewing the case and communicating with the patient.
Build a concise prior authorization packet from local case files and payer policy docs.
Review the instructions the agent will receive before you install.
Use this skill when a case requires prior authorization review, referral validation, imaging review, or payer-specific policy checks.
case/scenario.json and case/transcript.txt.policies/ for payer, prior auth, referral, imaging, and PPO guidance:
rg -n -i 'prior authorization|prior-auth|imaging|referral|billing|PPO|Blue Cross' policies || grep -RniE 'prior authorization|prior-auth|imaging|referral|billing|PPO|Blue Cross' policies.rg launcher or bootstrap failure is not evidence that there are no policy matches.output/policy_findings.md with these exact headings:
## Case summary## Matched policy files## Prior authorization## Referral## Missing information
Cite each matched policy by its filename.output/human_review_checklist.md with:
finalize_policy_packet only after both artifacts exist.grep -RniE fallback only when rg cannot complete the search.finalize_policy_packet succeeds.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Run final checks on reviewed SDK changes, covering code formatting, linting for code issues, type checking, and tests. Confirm completion only after every required check succeeds, with wrappers for macOS, Linux, and Windows.
Fix a small formatting bug in a credit note shell script while keeping the output label as credit and the amount positive. Run the specified targeted test and summarize the bug, fix, and verification command.
Analyze CSV files with Python and get concise numerical summaries. The skill checks column structure before calculating requested aggregates, includes units when available, and explains assumptions when data is missing or incorrectly formatted.
Compare SDK implementation with English documentation to find missing features, incorrect defaults, and outdated behavior descriptions. Report evidence and suggested locations, or make requested updates while keeping navigation consistent and following the repository’s documentation checks.
Review logs and source files from a completed manual example run. Check that results are current and complete, verify intended behavior beyond successful exit codes, and distinguish product defects from environment or credential problems.
Compare a Python SDK release plan or candidate with the previous release to assess compatibility, versioning, and proven regressions. Produce a ship-or-block recommendation, documentation handoff, and key changes for minor releases.