# Market Access Value

> Write payer-facing pharmacoeconomic value propositions

- Skill: `majiayu000/market-access-value` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds add majiayu000/market-access-value`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/market-access-value/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: MIT
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/majiayu000/market-access-value

---


# Market Access Value

Payer value proposition development.

## Use Cases
- HTA submissions
- Payer negotiations
- Pricing strategy
- Reimbursement applications

## Parameters
- `drug_profile`: Efficacy/safety data
- `comparator`: Standard of care
- `market`: US/EU/Japan pricing

## Returns
- ICER calculation narrative
- Budget impact model text
- Value dossier sections
- Payer objection handlers

## Example
ICER = $45,000/QALY with uncertainty analysis

## Risk Assessment

| Risk Indicator | Assessment | Level |
|----------------|------------|-------|
| Code Execution | Python/R scripts executed locally | Medium |
| Network Access | No external API calls | Low |
| File System Access | Read input files, write output files | Medium |
| Instruction Tampering | Standard prompt guidelines | Low |
| Data Exposure | Output files saved to workspace | Low |

## Security Checklist

- [ ] No hardcoded credentials or API keys
- [ ] No unauthorized file system access (../)
- [ ] Output does not expose sensitive information
- [ ] Prompt injection protections in place
- [ ] Input file paths validated (no ../ traversal)
- [ ] Output directory restricted to workspace
- [ ] Script execution in sandboxed environment
- [ ] Error messages sanitized (no stack traces exposed)
- [ ] Dependencies audited
## Prerequisites

No additional Python packages required.

## Evaluation Criteria

### Success Metrics
- [ ] Successfully executes main functionality
- [ ] Output meets quality standards
- [ ] Handles edge cases gracefully
- [ ] Performance is acceptable

### Test Cases
1. **Basic Functionality**: Standard input → Expected output
2. **Edge Case**: Invalid input → Graceful error handling
3. **Performance**: Large dataset → Acceptable processing time

## Lifecycle Status

- **Current Stage**: Draft
- **Next Review Date**: 2026-03-06
- **Known Issues**: None
- **Planned Improvements**: 
  - Performance optimization
  - Additional feature support