Incremental audio production with duration mismatch handling, adaptive stem extension, and pre-mix alignment verification
日本語の概要は準備中です。原文の説明を表示しています。
Generate complete medical SOAP notes with all four sections in a single comprehensive file write operation
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
This skill defines the workflow for creating structured medical documentation (SOAP notes) by writing all required sections to a file in one comprehensive operation. This ensures completeness, consistency, and efficiency in clinical documentation.
Use this skill when you need to create:
that follow the standard SOAP (Subjective, Objective, Assessment, Plan) format.
Produce a complete medical visit record containing all four SOAP sections without fragmenting the output across multiple files or incomplete drafts. The entire note should be written in a single operation to maintain consistency.
Before creating the SOAP note, gather:
Write the entire SOAP note in one comprehensive file write rather than building it incrementally. This ensures:
Every SOAP note must include these four components:
Patient-reported information including:
Clinician-observed and measured data:
Clinical synthesis and diagnosis:
Actionable next steps:
1. Gather all patient information and clinical data
2. Structure content into the four SOAP sections (do not skip any section)
3. Write the complete note to file in ONE operation
4. Verify all four sections are present and contain substantive content
# SOAP Note - [Patient Name/ID]
## Date: [Visit Date]
## Provider: [Provider Name]
## SUBJECTIVE
### Chief Complaint
[Patient's reason for visit in their own words]
### History of Present Illness
[Detailed symptom narrative using OLDCARTS framework]
### Past Medical History
[Relevant conditions, surgeries, medications, allergies]
### Family History
[Relevant family medical history]
### Social History
[Occupation, lifestyle, habits, social context]
## OBJECTIVE
### Vital Signs
- BP: [value] mmHg
- HR: [value] bpm
- RR: [value] breaths/min
- Temp: [value] °F/°C
- SpO2: [value]%
- Weight: [value] kg/lbs
- Height: [value] cm/ft
### Physical Examination
- **HEENT**: [findings]
- **Cardiovascular**: [findings]
- **Respiratory**: [findings]
- **Abdomen**: [findings]
- **Neurological**: [findings]
- **Musculoskeletal**: [findings]
- **Skin**: [findings]
### Diagnostic Data
[Labs, imaging, other test results with dates and values]
## ASSESSMENT
### Primary Diagnosis
[Diagnosis with ICD code if applicable]
### Differential Diagnoses
1. [Alternative diagnosis 1]
2. [Alternative diagnosis 2]
### Clinical Reasoning
[Brief explanation linking findings to diagnosis]
## PLAN
### Management
- [Medications with dose/frequency/duration]
- [Procedures/interventions]
- [Referrals if needed]
### Follow-up
[Timeline and conditions for return visit]
### Patient Education
[Instructions, lifestyle modifications, warning signs to watch]
Save the complete note using a consistent naming convention:
soap_note_<patient_id>_<date>.md orsoap_note_<patient_id>_<date>.txt[insert here]If specific clinical data is missing, explicitly state "Information not provided" or "Deferred" in the relevant section rather than skipping the section entirely.
Comprehensive SOAP notes typically range 3,000-10,000+ characters depending on complexity. If the note is exceptionally long:
After writing, verify all four headers (Subjective, Objective, Assessment, Plan) exist and contain substantive content. If any section is incomplete, rewrite the entire note in one operation.
Before considering the SOAP note complete, verify:
[insert here] unless genuinely unavailableまだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Incremental audio production with duration mismatch handling, adaptive stem extension, and pre-mix alignment verification
日本語の概要は準備中です。原文の説明を表示しています。
Incremental audio production with duration alignment handling, per-stem verification, and adaptive extension strategies
日本語の概要は準備中です。原文の説明を表示しています。
Create serverless API proxy endpoints that hide API keys and provide a unified backend for the dashboard frontend. Designed for Vercel deployment.
日本語の概要は準備中です。原文の説明を表示しています。
End-to-end audio production workflow with stems, effects, archiving, and verification
日本語の概要は準備中です。原文の説明を表示しています。
Handle cascading data retrieval tool failures by falling back to embedded knowledge generation
日本語の概要は準備中です。原文の説明を表示しています。
Fallback pattern for executing Python code when execute_code_sandbox fails
日本語の概要は準備中です。原文の説明を表示しています。