[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B1JTHBPKTZ301GPAFC8SWS":3,"skill-same:01M7B1JTHBPKTZ301GPAFC8SWS":49},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7B1JTHBPKTZ301GPAFC8SWS","slack-issue",null,"Create a GitHub issue from one or more Slack post links plus optional extra context, filed against the repository you're working in by default (e.g. `grafana\u002Fdesign` when run there) or another repo you name. Use when someone shares Slack conversation\u002Fmessage links and wants an issue filed about the topic raised.","torkelo\u002Fscenes2","torkelo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10999?v=4","01M7B1G6RRGVK2TZGTJ2813VJ4","Torkel Ödegaard","01M7B1G6SAYVTDC3NWMBPX16TB",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Ftorkelo\u002Fscenes2\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fslack-issue\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: slack-issue\ndescription: Create a GitHub issue from one or more Slack post links plus optional extra context, filed against the repository you're working in by default (e.g. `grafana\u002Fdesign` when run there) or another repo you name. Use when someone shares Slack conversation\u002Fmessage links and wants an issue filed about the topic raised.\nmetadata:\n  generated: hatch@v1.2.0\n  source: .hatch\u002F_skills\u002Fslack-issue\u002FSKILL.md\n---\n\n# Slack → GitHub issue\n\nTurn one or more Slack posts into a well-formed GitHub issue, shaped by any extra\ncontext the user passes as an argument. By default, file the issue against\n**the repository you're working in**; the user can name a different target repo\nin their context.\n\n## Inputs\n\nThe skill argument contains, in any order:\n\n- **One or more Slack message permalinks** (conversation item links) — e.g.\n  `https:\u002F\u002Fgrafana.slack.com\u002Farchives\u002FC09N762DJUE\u002Fp1781001391123456`, copied via\n  Slack's _Copy link_. A link to a reply inside a thread also carries\n  `?thread_ts=…&cid=…`.\n- **Optional additional context** as free text — extra framing, the desired\n  angle or scope, acceptance criteria, a proposed title, a preferred label, and\n  optionally a **target repo** (e.g. \"file this in `grafana\u002Ffoo`\"). Treat this as\n  **authoritative**: let it steer the issue's framing and scope, with the Slack\n  thread supplying the detail and evidence.\n\n## Target repository\n\nUnless the user names a specific repo, file the issue against the **current\nrepository** — the one the working directory belongs to:\n\n```bash\ngh repo view --json nameWithOwner --jq .nameWithOwner\n```\n\nRun inside `grafana\u002Fdesign` this resolves to `grafana\u002Fdesign` (the historical\ndefault); run in any other checkout with `gh` configured it resolves to that\nrepo. If the user's context names a target (e.g. \"open this in `grafana\u002Ffoo`\"),\nthat wins. If neither resolves — no git remote, or `gh` can't determine the\nrepo — stop and ask which `owner\u002Frepo` to file against; don't guess.\n\n## Prerequisites\n\n- The **Slack MCP server** is connected and authenticated (the\n  `mcp__plugin_slack_slack__*` tools resolve). An installed plugin is not enough —\n  its OAuth must be completed. If the tools aren't available, stop and tell the\n  user to connect\u002Fauthorize the Slack plugin (`\u002Freload-plugins` should then\n  report at least one plugin MCP server).\n- **`gh`** is authenticated with access to the target repo\n  (`gh repo view \u003Cowner\u002Frepo>`). If the repo defines issue templates\n  (`.github\u002FISSUE_TEMPLATE\u002F`, surfaced by `gh issue create`), prefer the\n  closest-fitting template; otherwise a clean free-form body is expected.\n  (`grafana\u002Fdesign` has no templates.)\n\n## Steps\n\n1. **Separate the inputs.** Pull the Slack permalink(s) — and any explicit\n   target-repo mention — out of the argument and treat the remaining prose as the\n   user's additional context. If there's no Slack link, stop and ask for at least\n   one (don't invent a topic).\n\n2. **Resolve the target repo** as described under _Target repository_ — an\n   explicit mention from the user wins, otherwise the current repo via\n   `gh repo view`. Confirm it exists and you have access\n   (`gh repo view \u003Cowner\u002Frepo>`) before drafting.\n\n3. **Parse each permalink** into a channel + timestamp:\n   - `…\u002Farchives\u002F\u003CCHANNEL_ID>\u002Fp\u003CDIGITS>` → `channel = \u003CCHANNEL_ID>` and\n     `ts = \u003Cfirst 10 digits>.\u003Cremaining 6 digits>` (insert a `.` six digits from\n     the end of the `p…` number).\n   - If the URL has `?thread_ts=\u003CTS>&cid=\u003CCID>`, the link points at a reply\n     inside a thread — capture `thread_ts` and `cid` as well.\n\n4. **Read the source from Slack.** Use the Slack plugin's read tools (namespace\n   `mcp__plugin_slack_slack__*`) to fetch the message **and its full thread**, so\n   you capture the whole discussion rather than a single line:\n   - Threaded link (has `thread_ts`) → read the thread for `channel` +\n     `thread_ts` (`mcp__plugin_slack_slack__slack_read_thread`, or the plugin's\n     thread-reading tool).\n   - Standalone message → read a small window of channel history around `ts`\n     with `mcp__plugin_slack_slack__slack_read_channel` (bracket the timestamp\n     with `oldest`\u002F`latest`) to get the post plus any immediate replies\u002Fcontext.\n   - If a tool name differs from the above, list the available\n     `mcp__plugin_slack_slack__*` tools and use the closest read\u002Fthread tool.\n   - Resolve author user IDs to display names where it aids attribution\n     (`mcp__plugin_slack_slack__slack_search_users` or the plugin's user-lookup\n     tool).\n   - Read every link provided; note whether they're one topic or several (see\n     Edge cases).\n\n5. **Synthesize the topic.** From the thread(s) plus the user's additional\n   context, work out the actual ask — a bug, a feature\u002Fenhancement, a design\n   question, a token\u002Fcomponent gap, etc. The additional context is authoritative\n   for framing and scope; the thread supplies specifics and evidence.\n\n6. **Draft the issue.** Compose the issue for the target repo:\n   - **Title** — concise and specific. A title proposed in the user's context\n     wins.\n   - **Body** (free-form markdown), roughly:\n     - a one-paragraph **summary** of the problem\u002Fask;\n     - **Context \u002F details** distilled from the thread — paraphrase; quote\n       sparingly, don't dump the whole transcript;\n     - the user's **additional context**, woven in;\n     - a **Source** section linking back to each Slack thread with attribution,\n       e.g. `Raised by \u003Cname> in #\u003Cchannel> on YYYY-MM-DD — \u003Cpermalink>`.\n   - Suggest a **label** only if it already exists in the target repo's label set\n     (`gh label list --repo \u003Cowner\u002Frepo>`); common fits are `bug`, `enhancement`,\n     `question`, `documentation`. Only existing labels can be applied — confirm\n     before adding.\n   - **Do not** copy secrets, tokens, or personal data from Slack into the\n     issue — summarize instead.\n\n7. **Confirm before creating.** Creating a GitHub issue is outward-facing and\n   not cleanly reversible. Show the user the final **title, body, target repo\n   (`\u003Cowner\u002Frepo>`), and any labels**, and get explicit approval (offer to edit).\n   Do not create the issue until they confirm.\n\n8. **Create it.** Run\n   `gh issue create --repo \u003Cowner\u002Frepo> --title \"\u003Ctitle>\" --body \"\u003Cbody>\" [--label \u003Clabel> …]`.\n   Pass the body via a temp file (`--body-file`) or a quoted heredoc so markdown\n   and newlines are preserved.\n\n9. **Report.** Return the new issue URL and a one-line summary. If — and only if\n   — the user asks, offer to post the issue link back into the Slack thread.\n\n## Edge cases\n\n- **No Slack link in the input** → ask for at least one permalink.\n- **Link won't parse \u002F isn't a Slack archive URL** → show what you got and ask\n  for the _Copy link_ permalink.\n- **Can't determine the target repo** (no git remote, `gh` can't resolve the\n  current repo, and no repo named in the context) → ask the user which\n  `owner\u002Frepo` to file against.\n- **Slack read fails** (private channel you're not a member of, deleted message,\n  MCP not connected\u002Fauthenticated) → report which link failed and why; continue\n  with any that succeeded, or stop if none did.\n- **Multiple links** → if they're one topic, fold them into a single issue with\n  multiple Source entries; if they're clearly separate topics, ask whether to\n  open one combined issue or several.\n- **No additional context provided** → proceed from the thread alone, but still\n  confirm the draft before creating.\n- **`gh` not authenticated \u002F no access to the target repo** → stop and tell the\n  user to `gh auth login` or request repo access.\n\n## Notes\n\n- Always keep attribution and the Slack source link in the issue for\n  traceability.\n- Apply only labels that already exist in the target repo (`gh label list`); a\n  repo with no issue templates (like `grafana\u002Fdesign`) takes a clean free-form\n  body as the norm.\n","# Slack → GitHub issue\n\nTurn one or more Slack posts into a well-formed GitHub issue, shaped by any extra\ncontext the user passes as an argument. By default, file the issue against\n**the repository you're working in**; the user can name a different target repo\nin their context.\n\n## Inputs\n\nThe skill argument contains, in any order:\n\n- **One or more Slack message permalinks** (conversation item links) — e.g.\n  `https:\u002F\u002Fgrafana.slack.com\u002Farchives\u002FC09N762DJUE\u002Fp1781001391123456`, copied via\n  Slack's _Copy link_. A link to a reply inside a thread also carries\n  `?thread_ts=…&cid=…`.\n- **Optional additional context** as free text — extra framing, the desired\n  angle or scope, acceptance criteria, a proposed title, a preferred label, and\n  optionally a **target repo** (e.g. \"file this in `grafana\u002Ffoo`\"). Treat this as\n  **authoritative**: let it steer the issue's framing and scope, with the Slack\n  thread supplying the detail and evidence.\n\n## Target repository\n\nUnless the user names a specific repo, file the issue against the **current\nrepository** — the one the working directory belongs to:\n\n```bash\ngh repo view --json nameWithOwner --jq .nameWithOwner\n```\n\nRun inside `grafana\u002Fdesign` this resolves to `grafana\u002Fdesign` (the historical\ndefault); run in any other checkout with `gh` configured it resolves to that\nrepo. If the user's context names a target (e.g. \"open this in `grafana\u002Ffoo`\"),\nthat wins. If neither resolves — no git remote, or `gh` can't determine the\nrepo — stop and ask which `owner\u002Frepo` to file against; don't guess.\n\n## Prerequisites\n\n- The **Slack MCP server** is connected and authenticated (the\n  `mcp__plugin_slack_slack__*` tools resolve). An installed plugin is not enough —\n  its OAuth must be completed. If the tools aren't available, stop and tell the\n  user to connect\u002Fauthorize the Slack plugin (`\u002Freload-plugins` should then\n  report at least one plugin MCP server).\n- **`gh`** is authenticated with access to the target repo\n  (`gh repo view \u003Cowner\u002Frepo>`). If the repo defines issue templates\n  (`.github\u002FISSUE_TEMPLATE\u002F`, surfaced by `gh issue create`), prefer the\n  closest-fitting template; otherwise a clean free-form body is expected.\n  (`grafana\u002Fdesign` has no templates.)\n\n## Steps\n\n1. **Separate the inputs.** Pull the Slack permalink(s) — and any explicit\n   target-repo mention — out of the argument and treat the remaining prose as the\n   user's additional context. If there's no Slack link, stop and ask for at least\n   one (don't invent a topic).\n\n2. **Resolve the target repo** as described under _Target repository_ — an\n   explicit mention from the user wins, otherwise the current repo via\n   `gh repo view`. Confirm it exists and you have access\n   (`gh repo view \u003Cowner\u002Frepo>`) before drafting.\n\n3. **Parse each permalink** into a channel + timestamp:\n   - `…\u002Farchives\u002F\u003CCHANNEL_ID>\u002Fp\u003CDIGITS>` → `channel = \u003CCHANNEL_ID>` and\n     `ts = \u003Cfirst 10 digits>.\u003Cremaining 6 digits>` (insert a `.` six digits from\n     the end of the `p…` number).\n   - If the URL has `?thread_ts=\u003CTS>&cid=\u003CCID>`, the link points at a reply\n     inside a thread — capture `thread_ts` and `cid` as well.\n\n4. **Read the source from Slack.** Use the Slack plugin's read tools (namespace\n   `mcp__plugin_slack_slack__*`) to fetch the message **and its full thread**, so\n   you capture the whole discussion rather than a single line:\n   - Threaded link (has `thread_ts`) → read the thread for `channel` +\n     `thread_ts` (`mcp__plugin_slack_slack__slack_read_thread`, or the plugin's\n     thread-reading tool).\n   - Standalone message → read a small window of channel history around `ts`\n     with `mcp__plugin_slack_slack__slack_read_channel` (bracket the timestamp\n     with `oldest`\u002F`latest`) to get the post plus any immediate replies\u002Fcontext.\n   - If a tool name differs from the above, list the available\n     `mcp__plugin_slack_slack__*` tools and use the closest read\u002Fthread tool.\n   - Resolve author user IDs to display names where it aids attribution\n     (`mcp__plugin_slack_slack__slack_search_users` or the plugin's user-lookup\n     tool).\n   - Read every link provided; note whether they're one topic or several (see\n     Edge cases).\n\n5. **Synthesize the topic.** From the thread(s) plus the user's additional\n   context, work out the actual ask — a bug, a feature\u002Fenhancement, a design\n   question, a token\u002Fcomponent gap, etc. The additional context is authoritative\n   for framing and scope; the thread supplies specifics and evidence.\n\n6. **Draft the issue.** Compose the issue for the target repo:\n   - **Title** — concise and specific. A title proposed in the user's context\n     wins.\n   - **Body** (free-form markdown), roughly:\n     - a one-paragraph **summary** of the problem\u002Fask;\n     - **Context \u002F details** distilled from the thread — paraphrase; quote\n       sparingly, don't dump the whole transcript;\n     - the user's **additional context**, woven in;\n     - a **Source** section linking back to each Slack thread with attribution,\n       e.g. `Raised by \u003Cname> in #\u003Cchannel> on YYYY-MM-DD — \u003Cpermalink>`.\n   - Suggest a **label** only if it already exists in the target repo's label set\n     (`gh label list --repo \u003Cowner\u002Frepo>`); common fits are `bug`, `enhancement`,\n     `question`, `documentation`. Only existing labels can be applied — confirm\n     before adding.\n   - **Do not** copy secrets, tokens, or personal data from Slack into the\n     issue — summarize instead.\n\n7. **Confirm before creating.** Creating a GitHub issue is outward-facing and\n   not cleanly reversible. Show the user the final **title, body, target repo\n   (`\u003Cowner\u002Frepo>`), and any labels**, and get explicit approval (offer to edit).\n   Do not create the issue until they confirm.\n\n8. **Create it.** Run\n   `gh issue create --repo \u003Cowner\u002Frepo> --title \"\u003Ctitle>\" --body \"\u003Cbody>\" [--label \u003Clabel> …]`.\n   Pass the body via a temp file (`--body-file`) or a quoted heredoc so markdown\n   and newlines are preserved.\n\n9. **Report.** Return the new issue URL and a one-line summary. If — and only if\n   — the user asks, offer to post the issue link back into the Slack thread.\n\n## Edge cases\n\n- **No Slack link in the input** → ask for at least one permalink.\n- **Link won't parse \u002F isn't a Slack archive URL** → show what you got and ask\n  for the _Copy link_ permalink.\n- **Can't determine the target repo** (no git remote, `gh` can't resolve the\n  current repo, and no repo named in the context) → ask the user which\n  `owner\u002Frepo` to file against.\n- **Slack read fails** (private channel you're not a member of, deleted message,\n  MCP not connected\u002Fauthenticated) → report which link failed and why; continue\n  with any that succeeded, or stop if none did.\n- **Multiple links** → if they're one topic, fold them into a single issue with\n  multiple Source entries; if they're clearly separate topics, ask whether to\n  open one combined issue or several.\n- **No additional context provided** → proceed from the thread alone, but still\n  confirm the draft before creating.\n- **`gh` not authenticated \u002F no access to the target repo** → stop and tell the\n  user to `gh auth login` or request repo access.\n\n## Notes\n\n- Always keep attribution and the Slack source link in the issue for\n  traceability.\n- Apply only labels that already exist in the target repo (`gh label list`); a\n  repo with no issue templates (like `grafana\u002Fdesign`) takes a clean free-form\n  body as the norm.\n",{"name":5,"metadata":24,"description":7},{"source":25,"generated":26},".hatch\u002F_skills\u002Fslack-issue\u002FSKILL.md","hatch@v1.2.0","main","9b85ba995139627c15a6ef1cec1daec64659cf75",".agents\u002Fskills\u002Fslack-issue","https:\u002F\u002Fgithub.com\u002Ftorkelo\u002Fscenes2","https:\u002F\u002Fgithub.com\u002Ftorkelo","https:\u002F\u002Fgrafana.com","Grafana Labs Co-Founder, Grafana Creator & product manager & lead architect.  ","2026-11-14 19:30:54",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add torkelo\u002Fscenes2 --skill slack-issue",{"tool":41,"command":42},"bunx","bunx skills add torkelo\u002Fscenes2 --skill slack-issue",{"tool":44,"command":45},"pnpm","pnpm dlx skills add torkelo\u002Fscenes2 --skill slack-issue","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftorkelo\u002Fscenes2\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fslack-issue\u002FSKILL.md",true,[],[50,57,64,69,74,81],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7B1QT196EFM12F7737ZFBJ3","validate-plugin","validate a Grafana plugin using the official Grafana plugin validator","https:\u002F\u002Fgithub.com\u002Ftorkelo\u002Fscenes2\u002Fblob\u002Fmain\u002Fapps\u002Fdemo-app\u002F.codex\u002Fskills\u002Fvalidate-plugin\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7B1QQGHG8JJ9MK4BY2V8879","build-plugin","build a Grafana plugin using the standard build process (frontend and backend if applicable)","https:\u002F\u002Fgithub.com\u002Ftorkelo\u002Fscenes2\u002Fblob\u002Fmain\u002Fapps\u002Fdemo-app\u002F.codex\u002Fskills\u002Fbuild-plugin\u002FSKILL.md",[],[],{"skillNo":65,"name":52,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7B1QPP9RN7E1KNMRK9D8V6M","https:\u002F\u002Fgithub.com\u002Ftorkelo\u002Fscenes2\u002Fblob\u002Fmain\u002Fapps\u002Fdemo-app\u002F.claude\u002Fskills\u002Fvalidate-plugin\u002FSKILL.md",[],[],{"skillNo":70,"name":59,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7B1QN3V9SQ7H6WXNZDMQ57Q","https:\u002F\u002Fgithub.com\u002Ftorkelo\u002Fscenes2\u002Fblob\u002Fmain\u002Fapps\u002Fdemo-app\u002F.claude\u002Fskills\u002Fbuild-plugin\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7B1QJEW06858M7GC4EM46B5","stop-slop","Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells.","https:\u002F\u002Fgithub.com\u002Ftorkelo\u002Fscenes2\u002Fblob\u002Fmain\u002F.hatch\u002F_skills\u002Fstop-slop\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7B1QGEPPZQQNRJRXTQVZAKC","snag-fixer","Lightweight agent for quick fixes, tweaks, and small improvements. Optimized for single-task focused work without bloating context. Used by snag workflow for sequential fix processing.","https:\u002F\u002Fgithub.com\u002Ftorkelo\u002Fscenes2\u002Fblob\u002Fmain\u002F.hatch\u002F_skills\u002Fsnag-fixer\u002FSKILL.md",[],[]]