fda-med-device — Claude Code skill: features and setup
The fda-med-device Claude Code skill explains FDA rules for medical-device software. Ask about submission routes, software documentation, validation, cybersecurity, or whether a function falls under device regulation.
no license ★ 93 updated 2026-11-04
npx skills add jgsystemsconsulting/jgs-se-knowledge-packs --skill fda-med-device -a claude-codeWhat fda-med-device does
The skill answers questions about US FDA rules for software used in or alongside medical devices. It covers 510(k), De Novo and PMA submissions, Basic and Enhanced documentation levels, software validation, Computer Software Assurance, and the Quality Management System Regulation. Cybersecurity topics include SBOMs; other chapters address clinical decision support, MDDS, and software changes that can trigger a new 510(k).
Its reference notes are organized into chapters, with a topic index and the supporting files glossary.md and cheatsheet.md. The scope is US FDA regulation; it does not cover EU MDR or UKCA. The materials use Markdown, and runtime use needs no MCP server, API key, or paid tier.
What it helps with
- choose between Basic and Enhanced software documentation
- interpret FDA software validation expectations
- identify cybersecurity materials for a premarket submission
- assess whether a software change could require a new 510(k)
Example prompts for the agent
- Find the right documentation level for this device software.
- Explain FDA validation expectations for our system.
- Could this software change require a new 510(k)?
How to install fda-med-device
1Skills CLI (Vercel)
npx skills add jgsystemsconsulting/jgs-se-knowledge-packs --skill fda-med-device -a claude-code2Manually: put the files in place
~/.claude/skills/fda-med-device/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/fda-med-device/
1Skills CLI (Vercel)
npx skills add jgsystemsconsulting/jgs-se-knowledge-packs --skill fda-med-device -a codex2Manually: put the files in place
.agents/skills/fda-med-device/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add jgsystemsconsulting/jgs-se-knowledge-packs --skill fda-med-device -a cursor2Manually: put the files in place
.cursor/skills/fda-med-device/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install jgsystemsconsulting/jgs-se-knowledge-packs packs/fda-med-device/SKILL.md2Manually: put the files in place
.github/skills/fda-med-device/SKILL.md1Skills CLI (Vercel)
npx skills add jgsystemsconsulting/jgs-se-knowledge-packs --skill fda-med-device -a gemini-cli2Platform CLI
gemini skills install https://github.com/jgsystemsconsulting/jgs-se-knowledge-packs --path packs/fda-med-deviceManually: put the files in place
.devin/skills/fda-med-device/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add jgsystemsconsulting/jgs-se-knowledge-packs --skill fda-med-device -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about fda-med-device
How do I install fda-med-device in Claude Code?
Run npx skills add jgsystemsconsulting/jgs-se-knowledge-packs --skill fda-med-device -a claude-code. The skill file is at ~/.claude/skills/fda-med-device/SKILL.md.
What does fda-med-device do?
It helps answer questions about FDA requirements for medical-device software, including submission routes, documentation levels, validation, QMSR, and cybersecurity.
What does fda-med-device need to run?
The reference material is in Markdown. Runtime use requires no MCP server, API key, or paid tier.