Recording
codewhale-hq/Codewhale
Capture screenshots on registered computers, record on macOS or HarmonyOS, and manage saved captures.
Request your medical records and actually get them — what to ask for, the request letter that can't be shuffled aside, the timelines and fee rules to cite (jurisdiction-flagged), and the escalation…
MITAuto-check passed
Install Medical Records Request
$ npx skills add mohitagw15856/pm-claude-skills --skill medical-records-request -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills medical-records-request --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/medical-records-request .claude/skills/medical-records-request && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "medical-records-request" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/medical-records-request into .claude/skills/medical-records-request/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "medical-records-request", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/medical-records-requestType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill medical-records-request -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills medical-records-request --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/medical-records-request .agents/skills/medical-records-request && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "medical-records-request" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/medical-records-request into .agents/skills/medical-records-request/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "medical-records-request", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill medical-records-request -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills medical-records-request --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/medical-records-request .cursor/skills/medical-records-request && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "medical-records-request" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/medical-records-request into .cursor/skills/medical-records-request/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "medical-records-request", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/medical-records-request--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill medical-records-request -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills medical-records-request --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/medical-records-request .gemini/skills/medical-records-request && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "medical-records-request" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/medical-records-request into .gemini/skills/medical-records-request/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "medical-records-request", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills medical-records-requestInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill medical-records-request -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/medical-records-request .github/skills/medical-records-request && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "medical-records-request" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/medical-records-request into .github/skills/medical-records-request/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "medical-records-request", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill medical-records-request -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills medical-records-request --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/medical-records-request .opencode/skills/medical-records-request && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "medical-records-request" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/medical-records-request into .opencode/skills/medical-records-request/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "medical-records-request", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
medical-records-request- GitHub stars
- 1.4k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 811 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Request your medical records and actually get them — what to ask for, the request letter that can't be shuffled aside, the timelines and fee rules to cite (jurisdiction-flagged), and the escalation…
- Works in 5 steps: Itemize or receive a summary: "my… → Put it in writing, address it to the… → You, not just your doctors: records… → …
- Asked how do I get my medical records
- SKILL.md covers What This Skill Produces, Required Inputs, Framework: The… and Output Format, plus 7 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Medical Records Request is an agent skill from mohitagw15856/pm-claude-skills. Request your medical records and actually get them — what to ask for, the request letter that can't be shuffled aside, the timelines and fee rules to cite (jurisdiction-flagged), and the escalation path for stonewalls. Use when asked how do I get my medical records, write a records request, my doctor's office won't send my records, or what records should I collect. Produces the itemized request letter, the delivery and format choices decoded, the follow-up ladder, and the personal health-file structure for…
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked how do I get my medical records
- Write a records request
- My doctors office wont send my records
- What records should I collect
Example prompts
- “s office won”
- “/medical-records-request”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Itemize or receive a summary: "my records" gets you a visit summary; the letter names each item — clinic notes [date range], lab results…
- Put it in writing, address it to the records custodian: verbal requests evaporate; the letter creates the clock. Ask the office which…
- You, not just your doctors: records offices sometimes claim patient copies aren't available or only provider-to-provider transfer exists…
- Fees and timelines have rules: most jurisdictions cap copying fees and set response windows. The letter asks for the fee schedule up front…
- The purpose sets the format: consults need source materials (images, slides); continuity needs the summary set; archives want the complete…
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Medical Records Request loads about 1.6k tokens when it runs. Until then it costs about 137 tokens; SKILL.md has 811 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 811 words, ~1,561 tokens.
Download SKILL.mdSave it as
.claude/skills/medical-records-request/SKILL.md (or your agent's skills folder).- name
- medical-records-request
- description
- Request your medical records and actually get them — what to ask for, the request letter that can't be shuffled aside, the timelines and fee rules to cite (jurisdiction-flagged), and the escalation path for stonewalls. Use when asked how do I get my medical records, write a records request, my doctor's office won't send my records, or what records should I collect. Produces the itemized request letter, the delivery and format choices decoded, the follow-up ladder, and the personal health-file structure for keeping them.
Medical Records Request Skill
Your medical records are, in most places, yours by right — and yet getting them can feel like a heist: unanswered faxes, "we only send to other doctors," fees that materialize, imaging reports sent without the images. The gap is almost never law; it's process friction that a specific, itemized, deadline-aware written request cuts straight through. This skill writes that request, decodes the format choices that matter (images vs. reports, portal vs. complete file), and ladders the follow-up for offices that need reminding.
What This Skill Produces
- The itemized request letter — specific records, date ranges, format, delivery, ready to send
- The what-to-ask-for decode — the difference between the portal view, the "designated record set," imaging images vs. reports, and pathology materials — matched to the user's purpose
- The follow-up ladder — polite check → written reminder citing timelines → complaint paths, with dates
- The personal health-file structure — how to keep what arrives so the next request is smaller
Required Inputs
Ask for these if not provided:
- The purpose — second opinion, new doctor, moving, personal archive, dispute — it determines which records and what format (a consultant needs images; a new PCP needs the summary and problem list)
- The providers involved — each holds its own records; hospital systems and imaging centers are separate requests from the physician's office
- The jurisdiction, loosely — access rights, response timelines, and permissible fees vary by country/state; the letter cites rights generically with a verify-locally flag, and the user can look up specifics
- Any deadline — an appointment date turns the request urgent and belongs in the letter
Framework: The Friction-Cutting Rules
- Itemize or receive a summary: "my records" gets you a visit summary; the letter names each item — clinic notes [date range], lab results, imaging reports and images on disc/transfer, pathology reports (and slides if a consult needs them), medication list, referral letters. Specificity is the whole trick.
- Put it in writing, address it to the records custodian: verbal requests evaporate; the letter creates the clock. Ask the office which channel (portal message, form, fax — yes, still fax) counts as their official intake, then use it and keep proof of the date.
- You, not just your doctors: records offices sometimes claim patient copies aren't available or only provider-to-provider transfer exists — in most jurisdictions patients have direct access rights; the letter's rights sentence (kept generic, flagged verify-locally) exists for exactly this deflection.
- Fees and timelines have rules: most jurisdictions cap copying fees and set response windows. The letter asks for the fee schedule up front and notes the request date; the follow-up ladder cites the elapsed time, not outrage.
- The purpose sets the format: consults need source materials (images, slides); continuity needs the summary set; archives want the complete designated record set once, then incremental updates. Over-requesting has a real cost — a 900-page complete file for a routine handoff buries the signal.
Output Format
Records Request: [providers] — purpose: [purpose]
Show full SKILL.md (328 more words)Show less
The Letter
[Ready to send: patient identifiers · itemized records with date ranges · format and delivery choices · the generic access-rights sentence (verify-locally flagged) · fee-schedule request · the deadline if real · date and signature line]
What You're Asking For, Decoded
| Item | Why this format | Common pitfall |
|---|
The Follow-Up Ladder
Day 0: send via official intake, keep proof · Day ~10: polite status call, note the name · Day ~20: written reminder citing elapsed time and the request date · Beyond the local window: the complaint paths (records custodian's supervisor, the practice manager, and the applicable regulator — named as types, jurisdiction-flagged)
The Health File
[Structure for what arrives: by provider then date · the running summary page · what to hand the next new doctor — so this request is the last big one]
Access rights, timelines, and fee caps are jurisdiction-specific and change — verify the local specifics before citing exact numbers; this skill's letters cite rights generically for exactly that reason.
Quality Checks
- The letter itemizes records with date ranges — no bare "all my records" unless the purpose is a true archive
- Imaging images vs. reports is explicitly chosen per the purpose
- The rights sentence stays generic with the verify-locally flag — no invented statute citations
- The ladder runs on dates and elapsed time, not temperature
- Each provider/facility gets its own request — one letter to the hospital doesn't fetch the imaging center's files
Anti-Patterns
- Do not cite specific statutes, fee caps, or day-counts as fact — jurisdictions differ; generic rights + verify-locally is the honest letter
- Do not accept "we only send provider-to-provider" silently — the direct-access sentence exists for this
- Do not over-request — format follows purpose; the complete file is for archives, not handoffs
- Do not escalate before the clock has actually run — the ladder's power is its reasonableness
- Do not interpret the records' medical content — organize the paper; the medicine belongs to clinicians
Example Trigger Phrases
- "How do I get my medical records?"
- "Write a records request."
- "My doctor's office won't send my records."
- "What records should I collect?"
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/medical-records-request of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Medical Records Request next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Medical Records Request this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Recordingcodewhale-hq/Codewhale | 41k | — | ~540 | Automated safety check: Pass | MIT | |
| Architecture Decision Recordsaffaan-m/ECC | 277k | 4 repos | ~1.8k | Automated safety check: Pass | MIT | |
| Architecture Decision Recordsaffaan-m/ECC | 277k | 1 repos | ~863 | Automated safety check: Pass | MIT | |
| Architecture Decision Recordsaffaan-m/ECC | 276k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Browser Recordruvnet/ruflo | 74k | — | ~735 | Automated safety check: Notes | MIT |
Similar skills
Architecture Decision Records
affaan-m/ECC
Capture architectural decisions as numbered ADR markdown files in docs/adr/ with context, alternatives considered, consequences, and an index README.
Architecture Decision Records
affaan-m/ECC
在Claude Code会话期间，将做出的架构决策捕获为结构化的架构决策记录（ADR）。自动检测决策时刻，记录上下文、考虑的替代方案和理由。维护一个ADR日志，以便未来的开发人员理解代码库为何以当前方式构建。
Architecture Decision Records
affaan-m/ECC
コーディングセッション中にアーキテクチャ決定を構造化ADRとして記録し、自動的に決定の瞬間を検出し、コンテキスト、検討された代替案、根拠を記録します。今後の開発者がコードベースの形成理由を理解するためのADRログを維持します。
Browser Record
ruvnet/ruflo
Open a named, traced browser session into an RVF cognitive container with a ruvector trajectory recording every action
Grill And Record
asgeirtj/system_prompts_leaks
Run an explicitly requested decision interview and record each settled decision in durable project documentation.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Questions about Medical Records Request
What does Medical Records Request do?
Request your medical records and actually get them — what to ask for, the request letter that can't be shuffled aside, the timelines and fee rules to cite (jurisdiction-flagged), and the escalation…. Medical Records Request is an agent skill from mohitagw15856/pm-claude-skills. Request your medical records and actually get them — what to ask for, the request letter that can't be shuffled aside, the timelines and fee rules to cite (jurisdiction-flagged), and the escalation path for stonewalls.
When should I use Medical Records Request?
Medical Records Request fits situations like: asked how do I get my medical records; write a records request; my doctors office wont send my records; what records should I collect.
How do I install Medical Records Request in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill medical-records-request -a claude-code`. Or copy the skill folder (skills/medical-records-request in mohitagw15856/pm-claude-skills) into .claude/skills/medical-records-request in your project. Claude Code loads it when a task matches its description.
How do I install Medical Records Request in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill medical-records-request -a codex`. Or copy the skill folder (skills/medical-records-request in mohitagw15856/pm-claude-skills) into .agents/skills/medical-records-request in your project. Codex loads it when a task matches its description.
Can I use Medical Records Request in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill medical-records-request -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/medical-records-request, .gemini/skills/medical-records-request, .github/skills/medical-records-request and .opencode/skills/medical-records-request in your project.
What does Medical Records Request need to run?
SKILL.md names no scripts, command-line tools or credentials: Medical Records Request is instructions for the agent only.
Does Medical Records Request access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Medical Records Request safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Medical Records Request use?
Medical Records Request is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Medical Records Request use?
About 1.6k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Medical Records Request?
Skills that share tags, products or a category with Medical Records Request: Recording (codewhale-hq/Codewhale, 41k stars), Architecture Decision Records (affaan-m/ECC, 277k stars), Architecture Decision Records (affaan-m/ECC, 277k stars) and Architecture Decision Records (affaan-m/ECC, 276k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Medical Records Request?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.