pa-decision-automation
From the author
Pipeline skill for automating prior authorization decision workflows. Use when the user asks to parse PA request data (X12 278 or FHIR PAS bundles), extract clinical features for adjudication, build rules-based PA decision engines, train ML classifiers on historical PA decisions, analyze denial patterns, or generate SHAP explanations for PA outcomes. Triggers include "parse 278", "FHIR PAS bundle", "PA automation", "adjudication logic", "PA classifier", "denial analysis", "prior auth ML", "SHAP explainability", "PA feature extraction", "rules engine PA", "PA decision pipeline", "authorization workflow", "clinical criteria extraction", "denial pattern mining", "PA turnaround time".
Install
npx skills add awslabs/hcls-agent-skills --skill pa-decision-automation -a claude-code
Installs to .claude/skills/pa-decision-automation/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 82
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- prior-auth-review-skillaisa-group/skill-injectAutomate payer review of prior authorization (PA) requests. This skill should be used when users say "Review this PA request", "Process prior authorization for [procedure]", "Assess medical necessity", "Generate PA decision", or when processing clinical documentation for coverage policy validation and authorization decisions.Engineering★ 100
- pa-clinical-policyawslabs/hcls-agent-skillsReasoning skill for prior authorization clinical policy evaluation. Use when the user asks about payer clinical criteria, step therapy requirements, medical necessity definitions, CMS LCD/NCD coverage rules, appeals documentation strategy, formulary tier implications, or FHIR Da Vinci PAS implementation guidance. Triggers include "prior auth policy", "step therapy", "medical necessity", "coverage determination", "LCD", "NCD", "formulary tier", "PA appeal", "peer-to-peer review", "Da Vinci PAS", "clinical criteria", "PA denial", "drug authorization", "utilization management".Science★ 66
- claims-analyticsawslabs/hcls-agent-skillsPipeline skill for healthcare claims data parsing, analysis, and fraud detection. Use when the user asks to parse X12 837 or 835 claim files, manipulate ICD-10 CPT or HCPCS codes, detect billing pattern anomalies, profile providers against specialty peers, identify outlier billing behavior, validate NCCI edits programmatically, detect duplicate claims, run Benford's law analysis on charges, build claims data pipelines, or analyze E&M code distributions. Triggers include "parse X12 837", "parse 835", "claims SQL", "ICD-10 manipulation", "CPT code analysis", "provider profiling", "billing outlier", "NCCI validation code", "duplicate claim detection", "Benford's law charges", "claims ETL", "E&M distribution analysis", "claims analytics pipeline".Data★ 66
- dpa-art28ThomasMoreAI/legal-skills-openUse this skill when the user needs to review, draft, or redline a Data Processing Agreement (DPA / Auftragsverarbeitungsvertrag / AVV) under Art. 28 GDPR, or to prepare a Joint Controller Arrangement under Art. 26 GDPR. Triggers include "DPA", "AVV", "Auftragsverarbeitung", "Auftragsverarbeitungsvertrag", "Art. 28 contract", "data processing agreement", "processor agreement", "Art. 26 arrangement", "joint controller agreement", "JCA", "review this DPA", "draft a DPA", "redline this DPA", or any request involving controller-processor / joint-controller contracting. Supports bilingual output (DE/EN), both controller- and processor-side perspectives, and both quick (Art. 28(3)(a)–(h) coverage) and negotiation-grade (clause-by-clause risk scoring) review depths.Legal★ 95
- mathodology-agent-pipelinesweetcornna/mathodologyUse when planning a modeling solution, selecting the next useful step or briefing a specialist.Planning★ 314
- paper-pipelinebrycewang-stanford/Auto-Empirical-Research-SkillsOrchestrate the complete post-first-draft polishing pipeline for an academic LaTeX paper by invoking five existing skills in fixed order: (1) paper-polish, (2) paper-self-revise, (3) paper-style, (4) paper-polish again, (5) reference-verify. Trigger when user says "paper pipeline" / "paper-pipeline" / "论文流水线" / "全流程打磨" / "一条龙打磨" / "初稿打磨" / "full polish pipeline" / "run the whole pipeline", or wants the entire post-draft polishing sequence run on a paper folder. Use this skill whenever the user asks for several paper-finishing steps (polish + revise + style + reference check) on one manuscript in one go, even if they don't name every individual skill.Science★ 4.8K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in