Claude Skill

fda-catalyst-devices

Device-track catalyst analysis: 510(k), PMA, and De Novo decision events, CMS coverage and NTAP milestones, recalls and watch actions as risk signals, and post-market surveillance obligations — dated, verified, and sized per event for any medtech ticker or watchlist.

LLM Mart · 0 points · 0 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download agentii-ai-agentii-investment-intelligence-plugins_vertical-plugins_bio-pharm_skills_agentii_fda-catalyst-devices-3b0a195.zip · 5 KB
Part of agentii-ai/agentii-investment-intelligence — 46 skills

Install

skills CLI npx skills add https://github.com/agentii-ai/agentii-investment-intelligence/tree/main/plugins/vertical-plugins/bio-pharm/skills/agentii/fda-catalyst-devices
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install agentii-ai-agentii-investment-intelligence@llmmart
Git git clone https://github.com/agentii-ai/agentii-investment-intelligence.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole agentii-ai/agentii-investment-intelligence collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Methodology inspired by publicly taught medtech catalyst frameworks; all text is an original paraphrase.

Defaults

Parameter Default Value Rationale
forward_window_quarters 4 Standard catalyst window; extend to 8 on request
include_superseded false Active-only events by default; supersede chains on request
coverage_lens true Coverage and NTAP milestones tracked alongside decision events
recall_scan true Recalls and watch actions surfaced as risk signals by default
holiday_labeling true Holiday-shifted weeks flagged on every calendar row

Preflight

Run canonical pre-flight per contracts/preflight.md. Propagate X-Agentii-Trace per contracts/x-agentii-trace-header.md. Confirm ticker resolution via search_companies before catalyst queries.

Triggers

  • "What device decisions (510(k)/PMA/De Novo) are coming up for [ticker]?"
  • "When is the PMA decision date for [device/ticker]?"
  • "Which medtech names have device decisions this quarter?"
  • "What coverage or NTAP milestones are pending for [ticker]?"
  • "Has [ticker] had any recalls or watch-list actions recently?"
  • "Build a device catalyst calendar for my medtech watchlist."
  • "How do De Novo classifications differ from 510(k) as catalysts?"
  • "Evaluate the approval odds for [device] ahead of its panel."
  • "What post-market surveillance obligations does [ticker] carry?"
  • "Which device decisions overlap with [ticker]'s earnings date?"
  • "How did similar devices trade around their decision dates?"
  • "What is the installed-base story behind [ticker]'s next label expansion?"

Production Grounding

  • Device decision tracks: 510(k) clearance (substantial equivalence), PMA approval (higher evidence bar), De Novo classification (novel low-to-moderate-risk path) — each carries a binary-event dynamic.
  • Reimbursement is the second gate: CMS coverage determinations and NTAP milestones convert an approval into revenue; an approval without a coverage path is a hollow catalyst.
  • Recall and watch actions invert the signal: recall classes, watch lists, and post-market surveillance findings are negative catalysts that can compound.
  • Device vocabulary: installed base, placements, procedures, utilization, ASP with label-expansion annotations — the commercial context for sizing the post-decision move.
  • Never fabricate decision dates, recall classes, or coverage outcomes; annotate coverage gaps (per references/knowledge-frameworks.md).

Data Source Priority

  1. Structured decision data: get_device_decision (device_decision_event); asset identity via search_universe_devices / get_company_devices.
  2. Filing context: search_documents / search_sec_filings for PMA submissions, recall disclosures, MDRs.
  3. Coverage and NTAP milestones: search_documents keyword coverage/NTAP + read_source_outline/read_source_pages.
  4. Historical grounding: search_investment_cases (device decision/recall events), search_by_analogue.

Methodology

Retrieval Scope

unstructured_document_search

Retrieval Strategy

  1. Resolve ticker(s) via search_companies; collect company_id for device queries.
  2. Pull active decision events (get_device_decision) and asset inventory (get_company_devices).
  3. Overlay coverage/NTAP milestones and recall/watch actions from filings.
  4. For panel meetings, retrieve briefing documents via read_source_outline/read_source_pages; apply scrutiny axes.
  5. Ground the play: search_investment_cases / search_by_analogue with device filters; cite /v/ records.

Temporal Scope

See frontmatter temporal_scope block. Post-market surveillance windows may require looking back up to 8 quarters.

Tool Allowlist

See frontmatter allowed_tools.

Protocol

  1. Ticker resolution
  2. Decision enumeration (510(k) / PMA / De Novo)
  3. Coverage and NTAP milestone overlay
  4. Recall and watch risk scan
  5. Analogue grounding + calendar synthesis

Modes

  • Watchlist (default, multi-ticker): one dated calendar with per-ticker sections, sorted by date.
  • Single ticker deep-dive: full decision timeline, coverage state, and recall history.
  • Event type: restrict to PMA / De Novo / 510(k) / coverage / recalls on request.
  • Risk scan: recall and watch actions as a forward-looking risk screen.

Tool Fallbacks

Failure Fallback
get_device_decision empty search_documents keyword decision/PMA + search_sec_filings; annotate coverage_gap
Coverage milestone not found Flag reimbursement status unknown; never assume a coverage path
Recall data missing State surveillance data unavailable; do not infer recall classes
Knowledge tools empty Proceed with structured data only; annotate knowledge coverage_gap

Output File

{ticker}/{YYYY-MM-DD_HHMM}_fda-catalyst-devices_{affix}.md (watchlist: watchlist/{YYYY-MM-DD_HHMM}_fda-catalyst-devices-calendar_{affix}.md)

Output Structure

  1. Executive Summary — highest-impact device-track catalysts in the window, 2-3 sentences
  2. Catalyst Calendar — dated table: date, ticker, event type, device, application, holiday-week flag, expected-impact framing
  3. Per-Event Analysis — decision-track assessment (evidence bar, scrutiny axes) + decision history
  4. Coverage & Reimbursement State — coverage determinations, NTAP milestones, ASP context
  5. Recall & Surveillance Scan — recall classes, watch actions, post-market obligations
  6. Risk Assessment & Coverage Gaps — binary-risk sizing, signal clusters, missing data

Error Handling

Error Fallback
No device decision rows Fall back to earnings + pipeline events; annotate coverage_gap — never fabricate dates
510(k) vs PMA ambiguity State both possibilities with the evidence-bar difference; do not guess the track
Ticker not in med universe Resolve via CIK/device-universe match; surface the classification gap

Memory Load

See contracts/memory-load.md.

Snapshot

See contracts/snapshot-synthesis.md.

Final Summary (TUI)

Include ### Key Citations block with 0-10 clickable /v/ URLs.

References

  • contracts/citation-and-memory.md
  • contracts/output-frontmatter-schema.md
  • contracts/memory-load.md
  • contracts/snapshot-synthesis.md
  • contracts/preflight.md
  • references/knowledge-frameworks.md
Files (agentii-investment-intelligence)
  • references
    • knowledge-frameworks.md 4.2 KB
      # FDA Catalyst Devices — Knowledge Frameworks
      
      Static grounding for `fda-catalyst-devices` (spec 055). Runtime records are retrieved via the knowledge tools and cited with /v/ URLs; this file carries the device pathway ladder, failure modes, and the pattern disciplines. Shared regulatory scaffolding (scrutiny axes, binary-event sizing) lives in `../../fda-catalyst-analysis/references/knowledge-frameworks.md`.
      
      ## Device Pathway Ladder
      
      1. **Submission**: 510(k) (substantial equivalence to a predicate), PMA (de novo evidence of safety and effectiveness for high-risk), or De Novo (novel classification for low-to-moderate risk).
      2. **Decision**: clearance (510(k)), approval (PMA), or classification grant (De Novo) — a binary event, but the evidence bar differs sharply by track.
      3. **Reimbursement gate**: CMS coverage determination (NCD/LCD) and NTAP add-on payments — approval without coverage is a hollow catalyst.
      4. **Launch / installed base**: placements, procedures, utilization ramps; ASP carries label-expansion annotations.
      5. **Post-market**: surveillance studies, MDR reporting, recalls — an ongoing catalyst stream, mostly negative when it fires.
      
      ## Coverage and Recall Ladders
      
      - **Coverage**: approval → coding → coverage determination → NTAP window → payment rate. Each step is a dated, tradeable milestone.
      - **Recall classes**: Class I (serious harm/death risk), II, III — plus watch-list actions that precede recalls. Recalls compound: one class I often triggers guidance cuts and competitor share shifts.
      
      ## Failure Modes
      
      - **Equating 510(k) clearance with PMA approval**: the evidence bar differs; sizing a 510(k) like a PMA decision overstates the move.
      - **Ignoring the reimbursement gate**: the commercial catalyst is coverage, not clearance.
      - **Missing recall signals**: watch actions and MDR trends precede formal recalls — a screen that skips them misses the negative side.
      - **Treating approval as adoption**: installed-base ramp is the real revenue catalyst; utilization data settles whether the launch is tracking.
      - **Unlabeled holiday weeks**: procedure volumes across holiday-shifted weeks read as trend when they are seasonality.
      
      ## Methodology Patterns (original paraphrase of publicly taught practice)
      
      ### Device vocabulary (P1, cross-cutting)
      
      Installed base / placements / procedures / utilization / ASP ($/unit with label-expansion annotations). For launch tracking: consensus sales ÷ ASP ÷ procedure ramp → required procedure volume → linear path vs actuals, overlaid with at least two named same-category adoption curves.
      
      ### Event-takeaway anatomy (P4)
      
      Headline verdict → per-stock takeaways with model numbers → KOL distillation → data lattices → modeled deltas vs consensus → what's-changed vectors (estimates / thesis / positioning) → risk bullets. Conflicting views surfaced and rated by materiality, never averaged.
      
      ### POS / scenario discipline (cross-cutting)
      
      Unadjusted peak x POS = modeled number; both terms shown; POS changes logged with reasons. Bull/base/bear with named-driver grids; explicit abstention where unquantifiable. Reimbursement is a probability input, not an assumption: an uncovered device gets a discounted POS.
      
      ## Structured Data Surfaces
      
      - `get_device_decision` — device_decision_event rows (track, status, date).
      - `search_universe_devices` / `get_company_devices` — device identity and owner joins.
      - Recall, coverage, and NTAP context is document-sourced; annotate when unavailable.
      
      ## Cross-Cutting Habits
      
      - **Buy-side lens**: track where investor attention sits; the client-question pattern — answer the most common question directly (e.g. "does the coverage decision matter more than the clearance?"); per-name bull/bear pivot conditions.
      - **Living-thesis loop**: estimates move first, ratings last; append exhibits to the prior note, never rewrite; holiday labels persist.
      - **Badge mapping (FR-092)**: verifiable facts `[FACT]`, derived arithmetic `[DEDUCTED]`, judgments `[VIEW]` — with a Category/Count/% summary table.
      
      ## Authoring-time citations
      
      Spec 055 med strategies and cases are linked here as they reach `approved` status; at runtime retrieve via `search_investment_cases` / `search_by_analogue` and cite with /v/ URLs.
      
    • modes.md 575 B
      # fda-catalyst-devices — Analyst Mode Definitions
      
      Derived from the skill's ## Modes section (spec 046 M1).
      
      ### Mode: watchlist
      
      **Objective**: One dated device catalyst calendar with per-ticker sections, sorted by date.
      
      ### Mode: single-target
      
      **Objective**: Full decision timeline for one ticker with coverage state and recall history.
      
      ### Mode: event-type
      
      **Objective**: Restrict coverage to one event class — PMA, De Novo, 510(k), coverage, or recalls.
      
      ### Mode: risk-scan
      
      **Objective**: Recall and watch actions as a forward-looking negative-catalyst screen.
      
  • SKILL.md 7.2 KB
    ---
    name: fda-catalyst-devices
    description: "Device-track catalyst analysis: 510(k), PMA, and De Novo decision events, CMS coverage and NTAP milestones, recalls and watch actions as risk signals, and post-market surveillance obligations — dated, verified, and sized per event for any medtech ticker or watchlist."
    sectors: [med.medicines_biotech, med.medical_devices]
    multi_ticker_semantics: basket_v1_1
    temporal_scope:
      default_quarters: 4
      max_quarters: 8
      description: "Forward catalyst window default 4 quarters; up to 8 for long-horizon coverage and surveillance mapping."
    allowed_tools:
      - get_device_decision
      - search_universe_devices
      - get_company_devices
      - search_companies
      - get_company_profile
      - search_documents
      - search_sec_filings
      - read_source_outline
      - read_source_pages
      - search_investment_cases
      - search_by_analogue
      - search_knowledge_entries
    retrieval_scope: unstructured_document_search
    min_tool_diversity: 3
    parameter_free: false
    ---
    
    > Methodology inspired by publicly taught medtech catalyst frameworks; all text is an original paraphrase.
    
    ## Defaults
    
    | Parameter | Default Value | Rationale |
    |-----------|---------------|-----------|
    | forward_window_quarters | 4 | Standard catalyst window; extend to 8 on request |
    | include_superseded | false | Active-only events by default; supersede chains on request |
    | coverage_lens | true | Coverage and NTAP milestones tracked alongside decision events |
    | recall_scan | true | Recalls and watch actions surfaced as risk signals by default |
    | holiday_labeling | true | Holiday-shifted weeks flagged on every calendar row |
    
    ## Preflight
    
    Run canonical pre-flight per `contracts/preflight.md`. Propagate X-Agentii-Trace per `contracts/x-agentii-trace-header.md`. Confirm ticker resolution via `search_companies` before catalyst queries.
    
    ## Triggers
    
    - "What device decisions (510(k)/PMA/De Novo) are coming up for [ticker]?"
    - "When is the PMA decision date for [device/ticker]?"
    - "Which medtech names have device decisions this quarter?"
    - "What coverage or NTAP milestones are pending for [ticker]?"
    - "Has [ticker] had any recalls or watch-list actions recently?"
    - "Build a device catalyst calendar for my medtech watchlist."
    - "How do De Novo classifications differ from 510(k) as catalysts?"
    - "Evaluate the approval odds for [device] ahead of its panel."
    - "What post-market surveillance obligations does [ticker] carry?"
    - "Which device decisions overlap with [ticker]'s earnings date?"
    - "How did similar devices trade around their decision dates?"
    - "What is the installed-base story behind [ticker]'s next label expansion?"
    
    ## Production Grounding
    
    - Device decision tracks: 510(k) clearance (substantial equivalence), PMA approval (higher evidence bar), De Novo classification (novel low-to-moderate-risk path) — each carries a binary-event dynamic.
    - Reimbursement is the second gate: CMS coverage determinations and NTAP milestones convert an approval into revenue; an approval without a coverage path is a hollow catalyst.
    - Recall and watch actions invert the signal: recall classes, watch lists, and post-market surveillance findings are negative catalysts that can compound.
    - Device vocabulary: installed base, placements, procedures, utilization, ASP with label-expansion annotations — the commercial context for sizing the post-decision move.
    - Never fabricate decision dates, recall classes, or coverage outcomes; annotate coverage gaps (per `references/knowledge-frameworks.md`).
    
    ## Data Source Priority
    
    1. Structured decision data: `get_device_decision` (device_decision_event); asset identity via `search_universe_devices` / `get_company_devices`.
    2. Filing context: `search_documents` / `search_sec_filings` for PMA submissions, recall disclosures, MDRs.
    3. Coverage and NTAP milestones: `search_documents` keyword coverage/NTAP + `read_source_outline`/`read_source_pages`.
    4. Historical grounding: `search_investment_cases` (device decision/recall events), `search_by_analogue`.
    
    ## Methodology
    
    ### Retrieval Scope
    unstructured_document_search
    
    ### Retrieval Strategy
    1. Resolve ticker(s) via `search_companies`; collect company_id for device queries.
    2. Pull active decision events (`get_device_decision`) and asset inventory (`get_company_devices`).
    3. Overlay coverage/NTAP milestones and recall/watch actions from filings.
    4. For panel meetings, retrieve briefing documents via `read_source_outline`/`read_source_pages`; apply scrutiny axes.
    5. Ground the play: `search_investment_cases` / `search_by_analogue` with device filters; cite /v/ records.
    
    ### Temporal Scope
    See frontmatter temporal_scope block. Post-market surveillance windows may require looking back up to 8 quarters.
    
    ### Tool Allowlist
    See frontmatter allowed_tools.
    
    ### Protocol
    1. Ticker resolution
    2. Decision enumeration (510(k) / PMA / De Novo)
    3. Coverage and NTAP milestone overlay
    4. Recall and watch risk scan
    5. Analogue grounding + calendar synthesis
    
    ## Modes
    
    - **Watchlist** (default, multi-ticker): one dated calendar with per-ticker sections, sorted by date.
    - **Single ticker deep-dive**: full decision timeline, coverage state, and recall history.
    - **Event type**: restrict to PMA / De Novo / 510(k) / coverage / recalls on request.
    - **Risk scan**: recall and watch actions as a forward-looking risk screen.
    
    ## Tool Fallbacks
    
    | Failure | Fallback |
    |---------|----------|
    | get_device_decision empty | `search_documents` keyword decision/PMA + `search_sec_filings`; annotate coverage_gap |
    | Coverage milestone not found | Flag reimbursement status unknown; never assume a coverage path |
    | Recall data missing | State surveillance data unavailable; do not infer recall classes |
    | Knowledge tools empty | Proceed with structured data only; annotate knowledge coverage_gap |
    
    ## Output File
    
    `{ticker}/{YYYY-MM-DD_HHMM}_fda-catalyst-devices_{affix}.md` (watchlist: `watchlist/{YYYY-MM-DD_HHMM}_fda-catalyst-devices-calendar_{affix}.md`)
    
    ## Output Structure
    
    1. **Executive Summary** — highest-impact device-track catalysts in the window, 2-3 sentences
    2. **Catalyst Calendar** — dated table: date, ticker, event type, device, application, holiday-week flag, expected-impact framing
    3. **Per-Event Analysis** — decision-track assessment (evidence bar, scrutiny axes) + decision history
    4. **Coverage & Reimbursement State** — coverage determinations, NTAP milestones, ASP context
    5. **Recall & Surveillance Scan** — recall classes, watch actions, post-market obligations
    6. **Risk Assessment & Coverage Gaps** — binary-risk sizing, signal clusters, missing data
    
    ## Error Handling
    
    | Error | Fallback |
    |-------|----------|
    | No device decision rows | Fall back to earnings + pipeline events; annotate `coverage_gap` — never fabricate dates |
    | 510(k) vs PMA ambiguity | State both possibilities with the evidence-bar difference; do not guess the track |
    | Ticker not in med universe | Resolve via CIK/device-universe match; surface the classification gap |
    
    ## Memory Load
    
    See `contracts/memory-load.md`.
    
    ## Snapshot
    
    See `contracts/snapshot-synthesis.md`.
    
    ## Final Summary (TUI)
    
    Include ### Key Citations block with 0-10 clickable /v/ URLs.
    
    ## References
    
    - `contracts/citation-and-memory.md`
    - `contracts/output-frontmatter-schema.md`
    - `contracts/memory-load.md`
    - `contracts/snapshot-synthesis.md`
    - `contracts/preflight.md`
    - `references/knowledge-frameworks.md`
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related