[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FE8JMMVYP23YHD3KQ43SH4":3,"skill-same:01M7FE8JMMVYP23YHD3KQ43SH4":63},{"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":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":36,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M7FE8JMMVYP23YHD3KQ43SH4","write-pr",null,"Writes a PR or MR from a fixed template: the tickets it closes, a summary sketch, before and after evidence that proves each acceptance criterion (screenshots for visible changes), and merge danger (one-way or two-way door, blast radius). Use when opening, writing or updating a pull request or merge request.","Med-Karim-Ben-Boubaker\u002Fkarim-skills","Med-Karim-Ben-Boubaker","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F63352044?v=4","01M7FE4PT628J1M137P2SH4M5M","Karim Ben Boubaker","01M7FE4PV4JZRQT69G3TNBR5D0",1,"MIT","https:\u002F\u002Fgithub.com\u002FMed-Karim-Ben-Boubaker\u002Fkarim-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-pr\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: write-pr\ndescription: \"Writes a PR or MR from a fixed template: the tickets it closes, a summary sketch, before and after evidence that proves each acceptance criterion (screenshots for visible changes), and merge danger (one-way or two-way door, blast radius). Use when opening, writing or updating a pull request or merge request.\"\nmetadata:\n  credits:\n    skill: show-me\n    author: Dex Horthy\n    organisation: Humanlayer\n    url: \"https:\u002F\u002Fgithub.com\u002Fhumanlayer\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fshow-me\u002Fskills\u002Fshow-me\u002FSKILL.md\"\n---\n\n## Before you write\n\n- **Read the tickets** this change finishes, with the fetch command in `docs\u002Fagents\u002Fissue-tracker.md`. Their `## Brief` acceptance criteria are what the evidence must prove; a bug's `## Diagnosis` names the command that went red.\n- **Get the evidence** from the Demo that `review-code` ran: its folder, `.sandbox\u002Fdemo-\u003Cshort sha>\u002F`, holds `demo.sh`, `before\u002F` and `after\u002F`. When `HEAD` has moved since, rerun `demo.sh` on `HEAD` into `.sandbox\u002Fdemo-\u003Cnew short sha>\u002Fafter\u002F`, keep the first `before\u002F`, and look at every new screenshot and output before you use it. When no Demo ran, call the Skill tool with `review-code` first. A ticket PR inside an `implement-spec` run is the exception: that run's one Demo comes at the end, so the ticket PR shows its author's own run of the software.\n- **Title** the PR as the change, in the repo's commit format under `### Commits` in `AGENTS.md` or `CLAUDE.md`. The ticket's title says the problem; the PR's says what was done.\n- **Open it as a draft** with the first pushed commit, so the ticket shows work in progress, and mark it ready once the evidence is in. The commands are under **Pull requests** in `docs\u002Fagents\u002Fissue-tracker.md`.\n\nUse this template for writing the PR body:\n\n```markdown\nCloses #\u003Cticket>\n\n## Summary\n\n\u003Cdiagram, diff-sketch, or tree>\n\n## Evidence\n\n`\u003Cshort sha>` against `\u003Cfixed point's short sha>` · \u003Coffline or live> demo\n\n\u003Cone entry per acceptance criterion>\n\n**1. \u003Ccriterion, as a person sees it>**\n`\u003Ccommand that was run>`\n~~~diff\n- \u003Coutput before>\n+ \u003Coutput after>\n~~~\n\n**2. \u003Ccriterion a person sees on screen>**\n\n| Before | After |\n|---|---|\n| ![before](\u003Clink>) | ![after](\u003Clink>) |\n\n**3. \u003Ccriterion>** Unproven: \u003Cwhy>\n\n\u003Cdetails>\u003Csummary>Rerun the demo\u003C\u002Fsummary>\n\n~~~sh\n\u003Cdemo.sh>\n~~~\n\n\u003C\u002Fdetails>\n\n## Merge Danger\n\n**Door:** \u003Cone-way or two-way>\n\n\u003Coptional: description>\n\n**Blast Radius:** \u003Cone-word description>\n\n\u003Coptional: potential ramifications of merge>\n```\n\n## Sections\n\nSkip all preambles and keep prose brief. Use the user's domain language from `GLOSSARY.md`.\n\n### Closes\n\nOne line per ticket this PR finishes: `Closes #12` (GitHub needs the keyword before each number; GitLab takes `Closes #12, #13`). The tracker closes them when the PR merges into the default branch. A ticket the PR only touches gets `Refs #12`. Never put `Closes` in a commit message.\n\n### Summary\n\nPick the smallest view that makes the key point clear.\n\n- Show logic or an algorithm as pseudocode:\n\n```text\non(save)\n  if content is unchanged\n    return cached result\n  write new content\n  return fresh result\n```\n\n- Show runtime control flow as a call tree:\n\n```text\nsubmitForm\n  createSession\n    persistPrompt\n    launchAgent\n  navigateToSession\n```\n\n- Show UI structure as a component tree, including state and module boundaries that matter:\n\n```text\n\u003CSessionPage> (apps\u002Fexample\u002Fsrc\u002Froutes\u002Fsession.tsx)\n  useSessionEvents()\n  \u003CSessionToolbar>\n    \u003CRunSkillButton> (packages\u002Fui)\n```\n\n- Show file responsibility or a broad refactor as a shallow file tree:\n\n```text\nsrc\u002F\n├── commands\u002F       # parses user actions\n├── sessions\u002F       # owns session state\n└── transport\u002F      # sends API requests\n```\n\n- Show component interaction, control flow, or data flow with Mermaid:\n\n```mermaid\nsequenceDiagram\n    participant User\n    participant UI\n    participant Daemon\n    User->>UI: choose command\n    UI->>Daemon: send expanded prompt\n    Daemon-->>UI: stream result\n```\n\n- Use `diff` when the point is what changes and the surrounding shape already exists. Match the diff shape to the topic.\n\nFor a component change:\n\n```diff\n \u003CSessionPage>\n   useSessionEvents()\n   \u003CSessionToolbar>\n+    \u003CRunSkillButton \u002F>\n   \u003CSessionTimeline>\n+    \u003CSkillResultCard \u002F>\n```\n\nFor a file-layout change:\n\n```diff\n src\u002F\n ├── commands\u002F\n+│   └── show-me.ts       # expands the slash command\n ├── sessions\u002F\n-└── transport.ts\n+└── transport\u002F\n+    ├── client.ts\n+    └── stream.ts\n```\n\nFor a call-tree or call-stack change:\n\n```diff\n submitForm\n   createSession\n     persistPrompt\n+    expandSkillMention\n     launchAgent\n-  navigateToSession\n+  navigateToSession\n+    subscribeToEvents\n```\n\nFor a state or control-flow change:\n\n```diff\n on(save)\n-  write content\n+  if content is unchanged\n+    return cached result\n+  write new content\n+  invalidate cache\n```\n\n- Show the whole block when most of it is new, when omitted context would hide ownership or order, or when the user needs a copyable target shape:\n\n```ts\nfunction expandSkill(command: string): string {\n  const skillName = command.slice(1);\n  return `use the ${skillName} skill`;\n}\n```\n\n#### Guidance\n\nPlace each visual next to the short text it supports. Keep only the calls, files, props, states, and boundaries needed to answer the user's current question or the options to resolve the current discussion point.\n\nYou may use one of these, you may use several, it is unlikely you will use all of them. Use your judgement and don't overwhelm the user.\n\n### Evidence\n\nA person reads this section to see the change working: make the proof loud and the text short. Give one entry per acceptance criterion in the tickets' `## Brief`: the criterion in bold, as a person sees it, then the command that was run and one thing the Demo captured on the commit the PR points at. The first line names that commit, the commit it is compared against, and whether the demo ran offline or live.\n\n- **Proof is a demo run**: the real command with its real output, or a screenshot. Tests stay out of the PR: a criterion only a test covers is **Unproven**.\n- **Text output**: before and after in one `diff` block, as the script saved it, cut to the lines that prove the criterion (about eight, `…` marking each cut, secrets redacted). Something new shows only the after.\n- **Anything on screen**: before and after screenshots side by side, uploaded as **Upload a screenshot** in `docs\u002Fagents\u002Fissue-tracker.md` says. Without a screenshot it is **Unproven**.\n- **The entry is the proof**: at most one caption line under it. A criterion the Summary's diff already proves reads \"shown in the Summary\".\n- **Unproven and Failed**: a criterion the Demo could not show stays in the list, marked **Unproven** with the reason. One the Demo saw fail blocks ready until it's fixed.\n- **`demo.sh` alone** goes in the collapsed block, so a reviewer can rerun the demo.\n\n### Merge Danger\n\nDescribe whether it's a one-way or two-way door. You can walk back through two-way doors, but not one-way doors. A PR that is cheap to roll back is lower risk. Changes that involve destructive actions or hard-to-reverse decisions are one-way doors.\n\nEvery merge waits for the user's approval; name a one-way door plainly, so that approval is given knowing it.\n\nThe blast radius is the potential impact or scope of the changes introduced by this PR. Consider all possibilities. Examples are layout shift, breakages for consumers, mobile responsiveness, etc.\n","## Before you write\n\n- **Read the tickets** this change finishes, with the fetch command in `docs\u002Fagents\u002Fissue-tracker.md`. Their `## Brief` acceptance criteria are what the evidence must prove; a bug's `## Diagnosis` names the command that went red.\n- **Get the evidence** from the Demo that `review-code` ran: its folder, `.sandbox\u002Fdemo-\u003Cshort sha>\u002F`, holds `demo.sh`, `before\u002F` and `after\u002F`. When `HEAD` has moved since, rerun `demo.sh` on `HEAD` into `.sandbox\u002Fdemo-\u003Cnew short sha>\u002Fafter\u002F`, keep the first `before\u002F`, and look at every new screenshot and output before you use it. When no Demo ran, call the Skill tool with `review-code` first. A ticket PR inside an `implement-spec` run is the exception: that run's one Demo comes at the end, so the ticket PR shows its author's own run of the software.\n- **Title** the PR as the change, in the repo's commit format under `### Commits` in `AGENTS.md` or `CLAUDE.md`. The ticket's title says the problem; the PR's says what was done.\n- **Open it as a draft** with the first pushed commit, so the ticket shows work in progress, and mark it ready once the evidence is in. The commands are under **Pull requests** in `docs\u002Fagents\u002Fissue-tracker.md`.\n\nUse this template for writing the PR body:\n\n```markdown\nCloses #\u003Cticket>\n\n## Summary\n\n\u003Cdiagram, diff-sketch, or tree>\n\n## Evidence\n\n`\u003Cshort sha>` against `\u003Cfixed point's short sha>` · \u003Coffline or live> demo\n\n\u003Cone entry per acceptance criterion>\n\n**1. \u003Ccriterion, as a person sees it>**\n`\u003Ccommand that was run>`\n~~~diff\n- \u003Coutput before>\n+ \u003Coutput after>\n~~~\n\n**2. \u003Ccriterion a person sees on screen>**\n\n| Before | After |\n|---|---|\n| ![before](\u003Clink>) | ![after](\u003Clink>) |\n\n**3. \u003Ccriterion>** Unproven: \u003Cwhy>\n\n\u003Cdetails>\u003Csummary>Rerun the demo\u003C\u002Fsummary>\n\n~~~sh\n\u003Cdemo.sh>\n~~~\n\n\u003C\u002Fdetails>\n\n## Merge Danger\n\n**Door:** \u003Cone-way or two-way>\n\n\u003Coptional: description>\n\n**Blast Radius:** \u003Cone-word description>\n\n\u003Coptional: potential ramifications of merge>\n```\n\n## Sections\n\nSkip all preambles and keep prose brief. Use the user's domain language from `GLOSSARY.md`.\n\n### Closes\n\nOne line per ticket this PR finishes: `Closes #12` (GitHub needs the keyword before each number; GitLab takes `Closes #12, #13`). The tracker closes them when the PR merges into the default branch. A ticket the PR only touches gets `Refs #12`. Never put `Closes` in a commit message.\n\n### Summary\n\nPick the smallest view that makes the key point clear.\n\n- Show logic or an algorithm as pseudocode:\n\n```text\non(save)\n  if content is unchanged\n    return cached result\n  write new content\n  return fresh result\n```\n\n- Show runtime control flow as a call tree:\n\n```text\nsubmitForm\n  createSession\n    persistPrompt\n    launchAgent\n  navigateToSession\n```\n\n- Show UI structure as a component tree, including state and module boundaries that matter:\n\n```text\n\u003CSessionPage> (apps\u002Fexample\u002Fsrc\u002Froutes\u002Fsession.tsx)\n  useSessionEvents()\n  \u003CSessionToolbar>\n    \u003CRunSkillButton> (packages\u002Fui)\n```\n\n- Show file responsibility or a broad refactor as a shallow file tree:\n\n```text\nsrc\u002F\n├── commands\u002F       # parses user actions\n├── sessions\u002F       # owns session state\n└── transport\u002F      # sends API requests\n```\n\n- Show component interaction, control flow, or data flow with Mermaid:\n\n```mermaid\nsequenceDiagram\n    participant User\n    participant UI\n    participant Daemon\n    User->>UI: choose command\n    UI->>Daemon: send expanded prompt\n    Daemon-->>UI: stream result\n```\n\n- Use `diff` when the point is what changes and the surrounding shape already exists. Match the diff shape to the topic.\n\nFor a component change:\n\n```diff\n \u003CSessionPage>\n   useSessionEvents()\n   \u003CSessionToolbar>\n+    \u003CRunSkillButton \u002F>\n   \u003CSessionTimeline>\n+    \u003CSkillResultCard \u002F>\n```\n\nFor a file-layout change:\n\n```diff\n src\u002F\n ├── commands\u002F\n+│   └── show-me.ts       # expands the slash command\n ├── sessions\u002F\n-└── transport.ts\n+└── transport\u002F\n+    ├── client.ts\n+    └── stream.ts\n```\n\nFor a call-tree or call-stack change:\n\n```diff\n submitForm\n   createSession\n     persistPrompt\n+    expandSkillMention\n     launchAgent\n-  navigateToSession\n+  navigateToSession\n+    subscribeToEvents\n```\n\nFor a state or control-flow change:\n\n```diff\n on(save)\n-  write content\n+  if content is unchanged\n+    return cached result\n+  write new content\n+  invalidate cache\n```\n\n- Show the whole block when most of it is new, when omitted context would hide ownership or order, or when the user needs a copyable target shape:\n\n```ts\nfunction expandSkill(command: string): string {\n  const skillName = command.slice(1);\n  return `use the ${skillName} skill`;\n}\n```\n\n#### Guidance\n\nPlace each visual next to the short text it supports. Keep only the calls, files, props, states, and boundaries needed to answer the user's current question or the options to resolve the current discussion point.\n\nYou may use one of these, you may use several, it is unlikely you will use all of them. Use your judgement and don't overwhelm the user.\n\n### Evidence\n\nA person reads this section to see the change working: make the proof loud and the text short. Give one entry per acceptance criterion in the tickets' `## Brief`: the criterion in bold, as a person sees it, then the command that was run and one thing the Demo captured on the commit the PR points at. The first line names that commit, the commit it is compared against, and whether the demo ran offline or live.\n\n- **Proof is a demo run**: the real command with its real output, or a screenshot. Tests stay out of the PR: a criterion only a test covers is **Unproven**.\n- **Text output**: before and after in one `diff` block, as the script saved it, cut to the lines that prove the criterion (about eight, `…` marking each cut, secrets redacted). Something new shows only the after.\n- **Anything on screen**: before and after screenshots side by side, uploaded as **Upload a screenshot** in `docs\u002Fagents\u002Fissue-tracker.md` says. Without a screenshot it is **Unproven**.\n- **The entry is the proof**: at most one caption line under it. A criterion the Summary's diff already proves reads \"shown in the Summary\".\n- **Unproven and Failed**: a criterion the Demo could not show stays in the list, marked **Unproven** with the reason. One the Demo saw fail blocks ready until it's fixed.\n- **`demo.sh` alone** goes in the collapsed block, so a reviewer can rerun the demo.\n\n### Merge Danger\n\nDescribe whether it's a one-way or two-way door. You can walk back through two-way doors, but not one-way doors. A PR that is cheap to roll back is lower risk. Changes that involve destructive actions or hard-to-reverse decisions are one-way doors.\n\nEvery merge waits for the user's approval; name a one-way door plainly, so that approval is given knowing it.\n\nThe blast radius is the potential impact or scope of the changes introduced by this PR. Consider all possibilities. Examples are layout shift, breakages for consumers, mobile responsiveness, etc.\n",{"name":5,"metadata":24,"description":7},{"credits":25},{"url":26,"skill":27,"author":28,"organisation":29},"https:\u002F\u002Fgithub.com\u002Fhumanlayer\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fshow-me\u002Fskills\u002Fshow-me\u002FSKILL.md","show-me","Dex Horthy","Humanlayer","main","03f9278801a451ca8b532ae5be7195296143861a","skills\u002Fwrite-pr",0,"https:\u002F\u002Fgithub.com\u002FMed-Karim-Ben-Boubaker\u002Fkarim-skills","https:\u002F\u002Fgithub.com\u002FMed-Karim-Ben-Boubaker","https:\u002F\u002Fkarimbenboubaker.me\u002F","AI Engineer","2026-11-10 22:54:19",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add Med-Karim-Ben-Boubaker\u002Fkarim-skills --skill write-pr",{"tool":45,"command":46},"bunx","bunx skills add Med-Karim-Ben-Boubaker\u002Fkarim-skills --skill write-pr",{"tool":48,"command":49},"pnpm","pnpm dlx skills add Med-Karim-Ben-Boubaker\u002Fkarim-skills --skill write-pr","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMed-Karim-Ben-Boubaker\u002Fkarim-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-pr\u002FSKILL.md",true,[53,59],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"agents\u002Fopenai.yaml","REFERENCE","参考文档",99,"https:\u002F\u002Fgithub.com\u002FMed-Karim-Ben-Boubaker\u002Fkarim-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-pr\u002Fagents\u002Fopenai.yaml",{"path":60,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":61,"sourceHtmlUrl":62},"CREDITS.md",610,"https:\u002F\u002Fgithub.com\u002FMed-Karim-Ben-Boubaker\u002Fkarim-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-pr\u002FCREDITS.md",[64,71,78,85,92,99],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7FE8Y56P42CZS85V5NWGQ0B","write-walkthrough","Guide you through running a demo yourself that shows a fix or a new feature working: a few numbered steps in the chat, each a command to copy or a click to make, with what you should see.","https:\u002F\u002Fgithub.com\u002FMed-Karim-Ben-Boubaker\u002Fkarim-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-walkthrough\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7FE8SY1WVS77ZM15VSX9H08","write-spec","Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.","https:\u002F\u002Fgithub.com\u002FMed-Karim-Ben-Boubaker\u002Fkarim-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-spec\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7FE8Q2ZBJ61N6CEVFCVQPHR","write-questionnaire","Turn a decision you can't fully answer into a questionnaire for someone else to fill in.","https:\u002F\u002Fgithub.com\u002FMed-Karim-Ben-Boubaker\u002Fkarim-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-questionnaire\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7FE8EEG42Z95804TK2KT89R","write-issue","Files and moves issues on the repo's tracker (GitLab, GitHub or local files): one kind (bug, feature, chore) and one stage each, a title, the kind's template, and what each later stage needs. Use when filing, relabelling, moving or closing an issue, when work should be recorded instead of done now, or to split big work into child tickets.","https:\u002F\u002Fgithub.com\u002FMed-Karim-Ben-Boubaker\u002Fkarim-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-issue\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7FE8AJW55TTN9R3KFHBC9T5","write-for-agents","How to write documents an agent reads: context pointers, information hierarchy, completion criteria, leading words and pruning, plus skill frontmatter and invocation mechanics. Use when creating or editing a skill, AGENTS.md, CLAUDE.md, or any doc an agent reaches through a pointer.","https:\u002F\u002Fgithub.com\u002FMed-Karim-Ben-Boubaker\u002Fkarim-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-for-agents\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7FE89234W1JQ5ZN3DKAVNN7","wait-what","Stop. That last message did not land: re-pitch it.","https:\u002F\u002Fgithub.com\u002FMed-Karim-Ben-Boubaker\u002Fkarim-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwait-what\u002FSKILL.md",[],[]]