[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77TKFS50V0KB1NFCS9C4EB3":3,"skill-same:01M77TKFS50V0KB1NFCS9C4EB3":83},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":14,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M77TKFS50V0KB1NFCS9C4EB3","clinical-case-report",null,"Structured medical case presentation for clinical rounds, conferences,\nand documentation. Generates SOAP-format or narrative case reports\nwith physiologically accurate vitals, labs, and evidence-based plans.\nUse when the brief mentions \"case report\", \"case presentation\", \"SOAP note\",\n\"clinical case\", \"ward rounds\", \"case summary\", or \"patient presentation\".","hiktan44\u002Fopen-design-app","hiktan44","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F140920746?v=4","01M77SNV7J2RH7G3TQVS2FXMW9","hikmet tanriverdi","01M77SNV87GR8D3BJ9WJHFMZ9Y",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Fplugins\u002F_official\u002Fexamples\u002Fclinical-case-report\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: clinical-case-report\ndescription: |\n  Structured medical case presentation for clinical rounds, conferences,\n  and documentation. Generates SOAP-format or narrative case reports\n  with physiologically accurate vitals, labs, and evidence-based plans.\n  Use when the brief mentions \"case report\", \"case presentation\", \"SOAP note\",\n  \"clinical case\", \"ward rounds\", \"case summary\", or \"patient presentation\".\ntriggers:\n  - \"case report\"\n  - \"case presentation\"\n  - \"soap note\"\n  - \"clinical case\"\n  - \"ward rounds\"\n  - \"patient presentation\"\n  - \"case summary\"\n  - \"medical case\"\nod:\n  mode: prototype\n  platform: desktop\n  scenario: healthcare\n  preview:\n    type: html\n    entry: index.html\n  fidelity: high-fidelity\n  example_prompt: \"58-year-old male with 2 hours of substernal chest pain radiating to the left arm, diaphoresis, and ST elevation in leads II, III, aVF. Generate a full emergency cardiology case presentation.\"\n---\n\n# Clinical Case Report Skill\n\nGenerate a structured medical case presentation for clinical rounds,\nconferences, or documentation. The output follows standard medical\nformatting conventions used in hospital settings worldwide.\n\n## What you will produce\n\nA single-page HTML case report (`index.html`). Content varies by format\n(see `references\u002Fcase-formats.md` — selected in Step 0):\n\n**SOAP \u002F Conference format:**\n- **Patient identification** — age, sex, chief complaint\n- **History of Present Illness (HPI)** — chronological narrative with\n  pertinent positives and negatives\n- **Past Medical History, Medications, Allergies**\n- **Review of Systems**\n- **Physical Examination** — systematic findings by system\n- **Vital Signs** — formatted table with reference ranges and flags\n- **Investigations** — laboratory results and imaging findings\n- **Assessment** — primary diagnosis and differential (3–5 items)\n  with clinical reasoning for each\n- **Management Plan** — evidence-based, organised by problem\n\n**Brief Rounds format** (daily review, ward round, handover, ICU, post-call):\n- **ID line** — age, sex, day of admission, primary problem\n- **Interval events \u002F current status** — what has changed since last review\n- **Active problems** — numbered list\n- **Plan-by-problem** — concise actions for each active problem\n- Full HPI and systematic physical examination are **not** included\n\n---\n\n## Step-by-step workflow\n\n### Step 0 — Load reference files\n\nBefore starting, read both reference files:\n\n1. `references\u002Fcase-formats.md` — use this to choose the correct output\n   format (SOAP, Conference, or Brief Rounds) based on the user's context\n2. `references\u002Fchecklist.md` — keep P0 gates in mind throughout; you\n   must pass all P0 items before emitting the final artifact\n\n### Step 1 — Parse the brief\n\nRead the user's prompt and extract:\n\n- Patient age and sex\n- Chief complaint or presenting problem\n- Any vitals, labs, or imaging the user has provided\n- Clinical context: ED, ward rounds, conference case, outpatient, etc.\n- Specialty context: cardiology, emergency, internal medicine, etc.\n\nIf the chief complaint or presenting problem is missing:\n- **SOAP \u002F Conference**: ask one clarifying question before proceeding. Do not proceed without it.\n- **Brief Rounds**: if the admission problem or ID line is already available (e.g. \"day-3 ICU review for septic shock\"), proceed directly — a separate chief complaint is not required.\n\n### Step 2 — Build the clinical narrative\n\n**For SOAP \u002F Conference outputs:** write the HPI as a continuous prose\nnarrative in standard clinical style:\n\n> \"This is a [age]-year-old [sex] with a history of [relevant PMH] who\n> presents with [chief complaint]. Symptoms began [timeline] and are\n> characterised by [quality, severity, radiation]. Associated symptoms\n> include [list]. Pertinent negatives include [list].\"\n\nThe HPI must be chronological. Include timeline markers\n(\"2 hours prior to presentation\", \"onset yesterday morning\").\n\n**For Brief Rounds outputs** (daily review, ward round, handover, ICU,\npost-call): skip the full HPI and examination. Instead produce:\n\n- **ID line**: \"[Age][sex], Day [N] of admission, [primary problem]\"\n- **Interval events \u002F current status**: what has changed since last review\n- **Active problems**: numbered list\n- **Plan-by-problem**: concise action for each active problem\n\n### Step 3 — Generate physiologically consistent clinical data\n\nIf the user has not provided specific values, generate values that are\ninternally consistent with the diagnosis:\n\n**Consistency checks (typical patterns):**\n\n- A patient in shock **typically** has: HR >100, SBP \u003C90, raised lactate,\n  impaired capillary refill — but medications (beta-blockers), age, or\n  shock type (neurogenic, spinal) can alter this pattern\n- Pneumonia **typically** presents with raised WBC, raised CRP,\n  temperature >38°C — but afebrile pneumonia exists, especially in\n  the elderly or immunocompromised\n- A STEMI **typically** shows ST elevation in contiguous leads and raised\n  high-sensitivity troponin — but early presentations may have initially\n  normal troponin; CK-MB is not universally required\n- Sepsis **typically** shows raised or low WBC, raised lactate >2,\n  temperature abnormality — but compensated early sepsis may present\n  with normal vitals\n- Lab units must match convention: creatinine in µmol\u002FL or mg\u002FdL\n  (state which), glucose in mmol\u002FL, haemoglobin in g\u002FdL\n\n**Critical rule — preserve user-provided data:**\n- Never overwrite a value the user has explicitly stated\n- If a user-provided value is atypical for the diagnosis, keep it and\n  note the atypical presentation in the assessment rather than\n  forcing canonical numbers\n- Never generate a value that contradicts the stated diagnosis\n\n### Step 4 — Write the assessment\n\nThe assessment section must contain:\n\n1. **Primary diagnosis** stated clearly on the first line\n2. **Clinical reasoning** — one sentence explaining why this is the\n   most likely diagnosis\n3. **Differential diagnosis** — exactly 3 to 5 items, each with one\n   sentence of supporting or refuting evidence\n4. **Risk stratification** — include a validated clinical score where\n   applicable (TIMI for ACS, GRACE for ACS, Killip class + Shock Index\n   for STEMI\u002Fcardiogenic shock, CURB-65 for pneumonia, qSOFA for sepsis,\n   Wells for PE, etc.). Killip class and Shock Index together are\n   accepted as sufficient risk stratification for STEMI\u002Fcardiogenic shock cases.\n\n### Step 5 — Write the management plan\n\nThe plan must be:\n\n- **Specific**: write drug names, doses, routes, and frequencies.\n  Do not write \"start antibiotics\" — write\n  \"Piperacillin-Tazobactam 4.5g IV q8h for 5 days\"\n- **Organised by problem** using numbered headers\n- **Evidence-based**: management must reflect current standard of care\n  for the diagnosis\n- **Complete**: include investigations to order, monitoring parameters,\n  consults to request, and disposition\n\nIf you are uncertain about a specific dose, write\n\"[drug name] — dose per local formulary\u002Fprotocol\" rather than\ninventing a dose.\n\n### Important — Prescribing Safety\n\nGenerated plans must:\n- Be marked as educational\u002Fsimulated, not a substitute for clinician judgment\n- Use \"per local formulary\u002Fprotocol\" language when required patient variables\n  (weight, renal function, allergies) are missing from the brief\n- List key contraindications and unknowns before medication recommendations\n  when relevant patient data has not been provided\n- Never claim a plan is \"definitive\" or \"standard of care\" without full\n  patient context (allergy status, renal\u002Fhepatic function, pregnancy\n  status, weight, anticoagulation\u002Fbleeding risk)\n- Include a disclaimer footer in the HTML output stating the case is for\n  educational and documentation purposes only\n\n### Step 6 — Write `index.html`\n\nRequirements for the HTML output:\n\n- Professional medical document typography\n  (Georgia or system serif font preferred)\n- White background, dark text — suitable for printing\n- Vital signs and lab results in HTML `\u003Ctable>` elements\n- Critical findings (ST elevation, raised troponin, low BP, etc.)\n  highlighted in a visually distinct callout box with red left border\n- @media print CSS rules so the document prints cleanly on A4\u002FLetter\n- Tag every major section with `data-od-id` for comment-mode targeting:\n\n```html\n\u003Csection data-od-id=\"hpi\">...\u003C\u002Fsection>\n\u003Csection data-od-id=\"vitals\">...\u003C\u002Fsection>\n\u003Csection data-od-id=\"pmh\">...\u003C\u002Fsection>\n\u003Csection data-od-id=\"examination\">...\u003C\u002Fsection>\n\u003Csection data-od-id=\"investigations\">...\u003C\u002Fsection>\n\u003Csection data-od-id=\"assessment\">...\u003C\u002Fsection>\n\u003Csection data-od-id=\"plan\">...\u003C\u002Fsection>\n```\n\n### Step 7 — Self-check against `references\u002Fchecklist.md`\n\nBefore emitting `\u003Cartifact>`, run every P0 item in `references\u002Fchecklist.md`.\nAll P0 items must pass. Fix any failures before emitting.","# Clinical Case Report Skill\n\nGenerate a structured medical case presentation for clinical rounds,\nconferences, or documentation. The output follows standard medical\nformatting conventions used in hospital settings worldwide.\n\n## What you will produce\n\nA single-page HTML case report (`index.html`). Content varies by format\n(see `references\u002Fcase-formats.md` — selected in Step 0):\n\n**SOAP \u002F Conference format:**\n- **Patient identification** — age, sex, chief complaint\n- **History of Present Illness (HPI)** — chronological narrative with\n  pertinent positives and negatives\n- **Past Medical History, Medications, Allergies**\n- **Review of Systems**\n- **Physical Examination** — systematic findings by system\n- **Vital Signs** — formatted table with reference ranges and flags\n- **Investigations** — laboratory results and imaging findings\n- **Assessment** — primary diagnosis and differential (3–5 items)\n  with clinical reasoning for each\n- **Management Plan** — evidence-based, organised by problem\n\n**Brief Rounds format** (daily review, ward round, handover, ICU, post-call):\n- **ID line** — age, sex, day of admission, primary problem\n- **Interval events \u002F current status** — what has changed since last review\n- **Active problems** — numbered list\n- **Plan-by-problem** — concise actions for each active problem\n- Full HPI and systematic physical examination are **not** included\n\n---\n\n## Step-by-step workflow\n\n### Step 0 — Load reference files\n\nBefore starting, read both reference files:\n\n1. `references\u002Fcase-formats.md` — use this to choose the correct output\n   format (SOAP, Conference, or Brief Rounds) based on the user's context\n2. `references\u002Fchecklist.md` — keep P0 gates in mind throughout; you\n   must pass all P0 items before emitting the final artifact\n\n### Step 1 — Parse the brief\n\nRead the user's prompt and extract:\n\n- Patient age and sex\n- Chief complaint or presenting problem\n- Any vitals, labs, or imaging the user has provided\n- Clinical context: ED, ward rounds, conference case, outpatient, etc.\n- Specialty context: cardiology, emergency, internal medicine, etc.\n\nIf the chief complaint or presenting problem is missing:\n- **SOAP \u002F Conference**: ask one clarifying question before proceeding. Do not proceed without it.\n- **Brief Rounds**: if the admission problem or ID line is already available (e.g. \"day-3 ICU review for septic shock\"), proceed directly — a separate chief complaint is not required.\n\n### Step 2 — Build the clinical narrative\n\n**For SOAP \u002F Conference outputs:** write the HPI as a continuous prose\nnarrative in standard clinical style:\n\n> \"This is a [age]-year-old [sex] with a history of [relevant PMH] who\n> presents with [chief complaint]. Symptoms began [timeline] and are\n> characterised by [quality, severity, radiation]. Associated symptoms\n> include [list]. Pertinent negatives include [list].\"\n\nThe HPI must be chronological. Include timeline markers\n(\"2 hours prior to presentation\", \"onset yesterday morning\").\n\n**For Brief Rounds outputs** (daily review, ward round, handover, ICU,\npost-call): skip the full HPI and examination. Instead produce:\n\n- **ID line**: \"[Age][sex], Day [N] of admission, [primary problem]\"\n- **Interval events \u002F current status**: what has changed since last review\n- **Active problems**: numbered list\n- **Plan-by-problem**: concise action for each active problem\n\n### Step 3 — Generate physiologically consistent clinical data\n\nIf the user has not provided specific values, generate values that are\ninternally consistent with the diagnosis:\n\n**Consistency checks (typical patterns):**\n\n- A patient in shock **typically** has: HR >100, SBP \u003C90, raised lactate,\n  impaired capillary refill — but medications (beta-blockers), age, or\n  shock type (neurogenic, spinal) can alter this pattern\n- Pneumonia **typically** presents with raised WBC, raised CRP,\n  temperature >38°C — but afebrile pneumonia exists, especially in\n  the elderly or immunocompromised\n- A STEMI **typically** shows ST elevation in contiguous leads and raised\n  high-sensitivity troponin — but early presentations may have initially\n  normal troponin; CK-MB is not universally required\n- Sepsis **typically** shows raised or low WBC, raised lactate >2,\n  temperature abnormality — but compensated early sepsis may present\n  with normal vitals\n- Lab units must match convention: creatinine in µmol\u002FL or mg\u002FdL\n  (state which), glucose in mmol\u002FL, haemoglobin in g\u002FdL\n\n**Critical rule — preserve user-provided data:**\n- Never overwrite a value the user has explicitly stated\n- If a user-provided value is atypical for the diagnosis, keep it and\n  note the atypical presentation in the assessment rather than\n  forcing canonical numbers\n- Never generate a value that contradicts the stated diagnosis\n\n### Step 4 — Write the assessment\n\nThe assessment section must contain:\n\n1. **Primary diagnosis** stated clearly on the first line\n2. **Clinical reasoning** — one sentence explaining why this is the\n   most likely diagnosis\n3. **Differential diagnosis** — exactly 3 to 5 items, each with one\n   sentence of supporting or refuting evidence\n4. **Risk stratification** — include a validated clinical score where\n   applicable (TIMI for ACS, GRACE for ACS, Killip class + Shock Index\n   for STEMI\u002Fcardiogenic shock, CURB-65 for pneumonia, qSOFA for sepsis,\n   Wells for PE, etc.). Killip class and Shock Index together are\n   accepted as sufficient risk stratification for STEMI\u002Fcardiogenic shock cases.\n\n### Step 5 — Write the management plan\n\nThe plan must be:\n\n- **Specific**: write drug names, doses, routes, and frequencies.\n  Do not write \"start antibiotics\" — write\n  \"Piperacillin-Tazobactam 4.5g IV q8h for 5 days\"\n- **Organised by problem** using numbered headers\n- **Evidence-based**: management must reflect current standard of care\n  for the diagnosis\n- **Complete**: include investigations to order, monitoring parameters,\n  consults to request, and disposition\n\nIf you are uncertain about a specific dose, write\n\"[drug name] — dose per local formulary\u002Fprotocol\" rather than\ninventing a dose.\n\n### Important — Prescribing Safety\n\nGenerated plans must:\n- Be marked as educational\u002Fsimulated, not a substitute for clinician judgment\n- Use \"per local formulary\u002Fprotocol\" language when required patient variables\n  (weight, renal function, allergies) are missing from the brief\n- List key contraindications and unknowns before medication recommendations\n  when relevant patient data has not been provided\n- Never claim a plan is \"definitive\" or \"standard of care\" without full\n  patient context (allergy status, renal\u002Fhepatic function, pregnancy\n  status, weight, anticoagulation\u002Fbleeding risk)\n- Include a disclaimer footer in the HTML output stating the case is for\n  educational and documentation purposes only\n\n### Step 6 — Write `index.html`\n\nRequirements for the HTML output:\n\n- Professional medical document typography\n  (Georgia or system serif font preferred)\n- White background, dark text — suitable for printing\n- Vital signs and lab results in HTML `\u003Ctable>` elements\n- Critical findings (ST elevation, raised troponin, low BP, etc.)\n  highlighted in a visually distinct callout box with red left border\n- @media print CSS rules so the document prints cleanly on A4\u002FLetter\n- Tag every major section with `data-od-id` for comment-mode targeting:\n\n```html\n\u003Csection data-od-id=\"hpi\">...\u003C\u002Fsection>\n\u003Csection data-od-id=\"vitals\">...\u003C\u002Fsection>\n\u003Csection data-od-id=\"pmh\">...\u003C\u002Fsection>\n\u003Csection data-od-id=\"examination\">...\u003C\u002Fsection>\n\u003Csection data-od-id=\"investigations\">...\u003C\u002Fsection>\n\u003Csection data-od-id=\"assessment\">...\u003C\u002Fsection>\n\u003Csection data-od-id=\"plan\">...\u003C\u002Fsection>\n```\n\n### Step 7 — Self-check against `references\u002Fchecklist.md`\n\nBefore emitting `\u003Cartifact>`, run every P0 item in `references\u002Fchecklist.md`.\nAll P0 items must pass. Fix any failures before emitting.",{"od":24,"name":5,"triggers":33,"description":42},{"mode":25,"preview":26,"fidelity":29,"platform":30,"scenario":31,"example_prompt":32},"prototype",{"type":27,"entry":28},"html","index.html","high-fidelity","desktop","healthcare","58-year-old male with 2 hours of substernal chest pain radiating to the left arm, diaphoresis, and ST elevation in leads II, III, aVF. Generate a full emergency cardiology case presentation.",[34,35,36,37,38,39,40,41],"case report","case presentation","soap note","clinical case","ward rounds","patient presentation","case summary","medical case","Structured medical case presentation for clinical rounds, conferences,\nand documentation. Generates SOAP-format or narrative case reports\nwith physiologically accurate vitals, labs, and evidence-based plans.\nUse when the brief mentions \"case report\", \"case presentation\", \"SOAP note\",\n\"clinical case\", \"ward rounds\", \"case summary\", or \"patient presentation\".\n","main","f403d5b733fab92eab16d13e9baf3ac951afed55","plugins\u002F_official\u002Fexamples\u002Fclinical-case-report","https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app","https:\u002F\u002Fgithub.com\u002Fhiktan44","fasheone.com","Hikmet Tanrıverdi\r\nSTRATEJI DANIŞMANLIK, 2008-2018 İHKİB İSTANBUL HAZIR GİYİM BŞK, İTO MECLİS ÜYESİ, TEXMART DIŞ TİCARET YK STRATEGY CONSULTING, 2008-2018 PRESI","2026-10-11 23:59:08",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add hiktan44\u002Fopen-design-app --skill clinical-case-report",{"tool":57,"command":58},"bunx","bunx skills add hiktan44\u002Fopen-design-app --skill clinical-case-report",{"tool":60,"command":61},"pnpm","pnpm dlx skills add hiktan44\u002Fopen-design-app --skill clinical-case-report","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Fplugins\u002F_official\u002Fexamples\u002Fclinical-case-report\u002FSKILL.md",true,[65,71,75,79],{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"example.html","REFERENCE","参考文档",27679,"https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Fplugins\u002F_official\u002Fexamples\u002Fclinical-case-report\u002Fexample.html",{"path":72,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":73,"sourceHtmlUrl":74},"open-design.json",8528,"https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Fplugins\u002F_official\u002Fexamples\u002Fclinical-case-report\u002Fopen-design.json",{"path":76,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fcase-formats.md",2878,"https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Fplugins\u002F_official\u002Fexamples\u002Fclinical-case-report\u002Freferences\u002Fcase-formats.md",{"path":80,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fchecklist.md",3137,"https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Fplugins\u002F_official\u002Fexamples\u002Fclinical-case-report\u002Freferences\u002Fchecklist.md",[84,91,98,105,112,121],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M77WGV99HNV3Q6JN3H8Z70JE","Beta Skill","Instruction-only fixture skill.","https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Ftools\u002Frelease\u002Ftests\u002Ffixtures\u002Fcatalog\u002Fskills\u002Fbeta\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M77WGRXNRGHT9J1K929BPV5H","Alpha Skill","First fixture skill with a runnable demo.","https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Ftools\u002Frelease\u002Ftests\u002Ffixtures\u002Fcatalog\u002Fskills\u002Falpha\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M77WGQK7F7R1W6RBFZFEZ53M","Deck One","A small deck template fixture.","https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Ftools\u002Frelease\u002Ftests\u002Ffixtures\u002Fcatalog\u002Fdesign-templates\u002Fdeck-one\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":19},"01M77WGNPEGTDWMKDX659FS5DT","youtube-clipper","YouTube clip generation and editing with automated workflows — pull source video, slice highlights, add captions, and export.","https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-clipper\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":116,"licenseFileUrl":117,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":19},"01M77WGJ9KKT6Q4P10GAV3KC48","writing-guidelines","Review docs\u002Fprose for Writing Guidelines compliance. Use when asked to \"review my docs\", \"check writing style\", \"audit prose\", \"review docs voice and tone\", or \"check this page against the writing handbook\".","MIT","https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-guidelines\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-guidelines\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":19},"01M77WGF9P0WT4XBXMM0B9WRGR","wpds","WordPress Design System. Apply WordPress's official design tokens, typography, and component patterns to themes and sites.","https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Fskills\u002Fwpds\u002FSKILL.md",[],[]]