[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ATRE8R2DNYYTXSAKYHBEST":3,"skill-same:01M7ATRE8R2DNYYTXSAKYHBEST":53},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":29,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7ATRE8R2DNYYTXSAKYHBEST","finishing-a-development-branch",null,"Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup","tabtin-ai\u002FTabTin","tabtin-ai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F318455733?v=4","01M7ATGMM5SE688ACWMP1PKRRB","TabTin","01M7ATGMMV4YXJ83EFKXAZVHR3",454,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002Ftabtin-ai\u002FTabTin\u002Fblob\u002Fmain\u002Fpackages\u002Fagent-runtime\u002Ffixtures\u002Fpersonal-plugins\u002Fsuperpowers\u002Fskills\u002Ffinishing-a-development-branch\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: finishing-a-development-branch\ndescription: Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup\n---\n\n# Finishing a Development Branch\n\n## Overview\n\nGuide completion of development work by presenting clear options and handling chosen workflow.\n\n**Core principle:** Verify tests → Detect environment → Present options → Execute choice → Clean up.\n\n**Announce at start:** \"I'm using the finishing-a-development-branch skill to complete this work.\"\n\n## The Process\n\n### Step 1: Verify Tests\n\n**Before presenting options, verify tests pass:**\n\n```bash\n# Run project's test suite\nnpm test \u002F cargo test \u002F pytest \u002F go test .\u002F...\n```\n\n**If tests fail:**\n```\nTests failing (\u003CN> failures). Must fix before completing:\n\n[Show failures]\n\nCannot proceed with merge\u002FPR until tests pass.\n```\n\nStop. Don't proceed to Step 2.\n\n**If tests pass:** Continue to Step 2.\n\n### Step 2: Detect Environment\n\n**Determine workspace state before presenting options:**\n\n```bash\nGIT_DIR=$(cd \"$(git rev-parse --git-dir)\" 2>\u002Fdev\u002Fnull && pwd -P)\nGIT_COMMON=$(cd \"$(git rev-parse --git-common-dir)\" 2>\u002Fdev\u002Fnull && pwd -P)\n```\n\nThis determines which menu to show and how cleanup works:\n\n| State | Menu | Cleanup |\n|-------|------|---------|\n| `GIT_DIR == GIT_COMMON` (normal repo) | Standard 4 options | No worktree to clean up |\n| `GIT_DIR != GIT_COMMON`, named branch | Standard 4 options | Provenance-based (see Step 6) |\n| `GIT_DIR != GIT_COMMON`, detached HEAD | Reduced 3 options (no merge) | No cleanup (externally managed) |\n\n### Step 3: Determine Base Branch\n\n```bash\n# Try common base branches\ngit merge-base HEAD main 2>\u002Fdev\u002Fnull || git merge-base HEAD master 2>\u002Fdev\u002Fnull\n```\n\nOr ask: \"This branch split from main - is that correct?\"\n\n### Step 4: Present Options\n\n**Normal repo and named-branch worktree — present exactly these 4 options:**\n\n```\nImplementation complete. What would you like to do?\n\n1. Merge back to \u003Cbase-branch> locally\n2. Push and create a Pull Request\n3. Keep the branch as-is (I'll handle it later)\n4. Discard this work\n\nWhich option?\n```\n\n**Detached HEAD — present exactly these 3 options:**\n\n```\nImplementation complete. You're on a detached HEAD (externally managed workspace).\n\n1. Push as new branch and create a Pull Request\n2. Keep as-is (I'll handle it later)\n3. Discard this work\n\nWhich option?\n```\n\n**Don't add explanation** - keep options concise.\n\n### Step 5: Execute Choice\n\n#### Option 1: Merge Locally\n\n```bash\n# Get main repo root for CWD safety\nMAIN_ROOT=$(git -C \"$(git rev-parse --git-common-dir)\u002F..\" rev-parse --show-toplevel)\ncd \"$MAIN_ROOT\"\n\n# Merge first — verify success before removing anything\ngit checkout \u003Cbase-branch>\ngit pull\ngit merge \u003Cfeature-branch>\n\n# Verify tests on merged result\n\u003Ctest command>\n\n# Only after merge succeeds: cleanup worktree (Step 6), then delete branch\n```\n\nThen: Cleanup worktree (Step 6), then delete branch:\n\n```bash\ngit branch -d \u003Cfeature-branch>\n```\n\n#### Option 2: Push and Create PR\n\n```bash\n# Push branch\ngit push -u origin \u003Cfeature-branch>\n\n# Create PR\ngh pr create --title \"\u003Ctitle>\" --body \"$(cat \u003C\u003C'EOF'\n## Summary\n\u003C2-3 bullets of what changed>\n\n## Test Plan\n- [ ] \u003Cverification steps>\nEOF\n)\"\n```\n\n**Do NOT clean up worktree** — user needs it alive to iterate on PR feedback.\n\n#### Option 3: Keep As-Is\n\nReport: \"Keeping branch \u003Cname>. Worktree preserved at \u003Cpath>.\"\n\n**Don't cleanup worktree.**\n\n#### Option 4: Discard\n\n**Confirm first:**\n```\nThis will permanently delete:\n- Branch \u003Cname>\n- All commits: \u003Ccommit-list>\n- Worktree at \u003Cpath>\n\nType 'discard' to confirm.\n```\n\nWait for exact confirmation.\n\nIf confirmed:\n```bash\nMAIN_ROOT=$(git -C \"$(git rev-parse --git-common-dir)\u002F..\" rev-parse --show-toplevel)\ncd \"$MAIN_ROOT\"\n```\n\nThen: Cleanup worktree (Step 6), then force-delete branch:\n```bash\ngit branch -D \u003Cfeature-branch>\n```\n\n### Step 6: Cleanup Workspace\n\n**Only runs for Options 1 and 4.** Options 2 and 3 always preserve the worktree.\n\n```bash\nGIT_DIR=$(cd \"$(git rev-parse --git-dir)\" 2>\u002Fdev\u002Fnull && pwd -P)\nGIT_COMMON=$(cd \"$(git rev-parse --git-common-dir)\" 2>\u002Fdev\u002Fnull && pwd -P)\nWORKTREE_PATH=$(git rev-parse --show-toplevel)\n```\n\n**If `GIT_DIR == GIT_COMMON`:** Normal repo, no worktree to clean up. Done.\n\n**If worktree path is under `.worktrees\u002F`, `worktrees\u002F`, or `~\u002F.config\u002Fsuperpowers\u002Fworktrees\u002F`:** Superpowers created this worktree — we own cleanup.\n\n```bash\nMAIN_ROOT=$(git -C \"$(git rev-parse --git-common-dir)\u002F..\" rev-parse --show-toplevel)\ncd \"$MAIN_ROOT\"\ngit worktree remove \"$WORKTREE_PATH\"\ngit worktree prune  # Self-healing: clean up any stale registrations\n```\n\n**Otherwise:** The host environment (harness) owns this workspace. Do NOT remove it. If your platform provides a workspace-exit tool, use it. Otherwise, leave the workspace in place.\n\n## Quick Reference\n\n| Option | Merge | Push | Keep Worktree | Cleanup Branch |\n|--------|-------|------|---------------|----------------|\n| 1. Merge locally | yes | - | - | yes |\n| 2. Create PR | - | yes | yes | - |\n| 3. Keep as-is | - | - | yes | - |\n| 4. Discard | - | - | - | yes (force) |\n\n## Common Mistakes\n\n**Skipping test verification**\n- **Problem:** Merge broken code, create failing PR\n- **Fix:** Always verify tests before offering options\n\n**Open-ended questions**\n- **Problem:** \"What should I do next?\" is ambiguous\n- **Fix:** Present exactly 4 structured options (or 3 for detached HEAD)\n\n**Cleaning up worktree for Option 2**\n- **Problem:** Remove worktree user needs for PR iteration\n- **Fix:** Only cleanup for Options 1 and 4\n\n**Deleting branch before removing worktree**\n- **Problem:** `git branch -d` fails because worktree still references the branch\n- **Fix:** Merge first, remove worktree, then delete branch\n\n**Running git worktree remove from inside the worktree**\n- **Problem:** Command fails silently when CWD is inside the worktree being removed\n- **Fix:** Always `cd` to main repo root before `git worktree remove`\n\n**Cleaning up harness-owned worktrees**\n- **Problem:** Removing a worktree the harness created causes phantom state\n- **Fix:** Only clean up worktrees under `.worktrees\u002F`, `worktrees\u002F`, or `~\u002F.config\u002Fsuperpowers\u002Fworktrees\u002F`\n\n**No confirmation for discard**\n- **Problem:** Accidentally delete work\n- **Fix:** Require typed \"discard\" confirmation\n\n## Red Flags\n\n**Never:**\n- Proceed with failing tests\n- Merge without verifying tests on result\n- Delete work without confirmation\n- Force-push without explicit request\n- Remove a worktree before confirming merge success\n- Clean up worktrees you didn't create (provenance check)\n- Run `git worktree remove` from inside the worktree\n\n**Always:**\n- Verify tests before offering options\n- Detect environment before presenting menu\n- Present exactly 4 options (or 3 for detached HEAD)\n- Get typed confirmation for Option 4\n- Clean up worktree for Options 1 & 4 only\n- `cd` to main repo root before worktree removal\n- Run `git worktree prune` after removal\n","# Finishing a Development Branch\n\n## Overview\n\nGuide completion of development work by presenting clear options and handling chosen workflow.\n\n**Core principle:** Verify tests → Detect environment → Present options → Execute choice → Clean up.\n\n**Announce at start:** \"I'm using the finishing-a-development-branch skill to complete this work.\"\n\n## The Process\n\n### Step 1: Verify Tests\n\n**Before presenting options, verify tests pass:**\n\n```bash\n# Run project's test suite\nnpm test \u002F cargo test \u002F pytest \u002F go test .\u002F...\n```\n\n**If tests fail:**\n```\nTests failing (\u003CN> failures). Must fix before completing:\n\n[Show failures]\n\nCannot proceed with merge\u002FPR until tests pass.\n```\n\nStop. Don't proceed to Step 2.\n\n**If tests pass:** Continue to Step 2.\n\n### Step 2: Detect Environment\n\n**Determine workspace state before presenting options:**\n\n```bash\nGIT_DIR=$(cd \"$(git rev-parse --git-dir)\" 2>\u002Fdev\u002Fnull && pwd -P)\nGIT_COMMON=$(cd \"$(git rev-parse --git-common-dir)\" 2>\u002Fdev\u002Fnull && pwd -P)\n```\n\nThis determines which menu to show and how cleanup works:\n\n| State | Menu | Cleanup |\n|-------|------|---------|\n| `GIT_DIR == GIT_COMMON` (normal repo) | Standard 4 options | No worktree to clean up |\n| `GIT_DIR != GIT_COMMON`, named branch | Standard 4 options | Provenance-based (see Step 6) |\n| `GIT_DIR != GIT_COMMON`, detached HEAD | Reduced 3 options (no merge) | No cleanup (externally managed) |\n\n### Step 3: Determine Base Branch\n\n```bash\n# Try common base branches\ngit merge-base HEAD main 2>\u002Fdev\u002Fnull || git merge-base HEAD master 2>\u002Fdev\u002Fnull\n```\n\nOr ask: \"This branch split from main - is that correct?\"\n\n### Step 4: Present Options\n\n**Normal repo and named-branch worktree — present exactly these 4 options:**\n\n```\nImplementation complete. What would you like to do?\n\n1. Merge back to \u003Cbase-branch> locally\n2. Push and create a Pull Request\n3. Keep the branch as-is (I'll handle it later)\n4. Discard this work\n\nWhich option?\n```\n\n**Detached HEAD — present exactly these 3 options:**\n\n```\nImplementation complete. You're on a detached HEAD (externally managed workspace).\n\n1. Push as new branch and create a Pull Request\n2. Keep as-is (I'll handle it later)\n3. Discard this work\n\nWhich option?\n```\n\n**Don't add explanation** - keep options concise.\n\n### Step 5: Execute Choice\n\n#### Option 1: Merge Locally\n\n```bash\n# Get main repo root for CWD safety\nMAIN_ROOT=$(git -C \"$(git rev-parse --git-common-dir)\u002F..\" rev-parse --show-toplevel)\ncd \"$MAIN_ROOT\"\n\n# Merge first — verify success before removing anything\ngit checkout \u003Cbase-branch>\ngit pull\ngit merge \u003Cfeature-branch>\n\n# Verify tests on merged result\n\u003Ctest command>\n\n# Only after merge succeeds: cleanup worktree (Step 6), then delete branch\n```\n\nThen: Cleanup worktree (Step 6), then delete branch:\n\n```bash\ngit branch -d \u003Cfeature-branch>\n```\n\n#### Option 2: Push and Create PR\n\n```bash\n# Push branch\ngit push -u origin \u003Cfeature-branch>\n\n# Create PR\ngh pr create --title \"\u003Ctitle>\" --body \"$(cat \u003C\u003C'EOF'\n## Summary\n\u003C2-3 bullets of what changed>\n\n## Test Plan\n- [ ] \u003Cverification steps>\nEOF\n)\"\n```\n\n**Do NOT clean up worktree** — user needs it alive to iterate on PR feedback.\n\n#### Option 3: Keep As-Is\n\nReport: \"Keeping branch \u003Cname>. Worktree preserved at \u003Cpath>.\"\n\n**Don't cleanup worktree.**\n\n#### Option 4: Discard\n\n**Confirm first:**\n```\nThis will permanently delete:\n- Branch \u003Cname>\n- All commits: \u003Ccommit-list>\n- Worktree at \u003Cpath>\n\nType 'discard' to confirm.\n```\n\nWait for exact confirmation.\n\nIf confirmed:\n```bash\nMAIN_ROOT=$(git -C \"$(git rev-parse --git-common-dir)\u002F..\" rev-parse --show-toplevel)\ncd \"$MAIN_ROOT\"\n```\n\nThen: Cleanup worktree (Step 6), then force-delete branch:\n```bash\ngit branch -D \u003Cfeature-branch>\n```\n\n### Step 6: Cleanup Workspace\n\n**Only runs for Options 1 and 4.** Options 2 and 3 always preserve the worktree.\n\n```bash\nGIT_DIR=$(cd \"$(git rev-parse --git-dir)\" 2>\u002Fdev\u002Fnull && pwd -P)\nGIT_COMMON=$(cd \"$(git rev-parse --git-common-dir)\" 2>\u002Fdev\u002Fnull && pwd -P)\nWORKTREE_PATH=$(git rev-parse --show-toplevel)\n```\n\n**If `GIT_DIR == GIT_COMMON`:** Normal repo, no worktree to clean up. Done.\n\n**If worktree path is under `.worktrees\u002F`, `worktrees\u002F`, or `~\u002F.config\u002Fsuperpowers\u002Fworktrees\u002F`:** Superpowers created this worktree — we own cleanup.\n\n```bash\nMAIN_ROOT=$(git -C \"$(git rev-parse --git-common-dir)\u002F..\" rev-parse --show-toplevel)\ncd \"$MAIN_ROOT\"\ngit worktree remove \"$WORKTREE_PATH\"\ngit worktree prune  # Self-healing: clean up any stale registrations\n```\n\n**Otherwise:** The host environment (harness) owns this workspace. Do NOT remove it. If your platform provides a workspace-exit tool, use it. Otherwise, leave the workspace in place.\n\n## Quick Reference\n\n| Option | Merge | Push | Keep Worktree | Cleanup Branch |\n|--------|-------|------|---------------|----------------|\n| 1. Merge locally | yes | - | - | yes |\n| 2. Create PR | - | yes | yes | - |\n| 3. Keep as-is | - | - | yes | - |\n| 4. Discard | - | - | - | yes (force) |\n\n## Common Mistakes\n\n**Skipping test verification**\n- **Problem:** Merge broken code, create failing PR\n- **Fix:** Always verify tests before offering options\n\n**Open-ended questions**\n- **Problem:** \"What should I do next?\" is ambiguous\n- **Fix:** Present exactly 4 structured options (or 3 for detached HEAD)\n\n**Cleaning up worktree for Option 2**\n- **Problem:** Remove worktree user needs for PR iteration\n- **Fix:** Only cleanup for Options 1 and 4\n\n**Deleting branch before removing worktree**\n- **Problem:** `git branch -d` fails because worktree still references the branch\n- **Fix:** Merge first, remove worktree, then delete branch\n\n**Running git worktree remove from inside the worktree**\n- **Problem:** Command fails silently when CWD is inside the worktree being removed\n- **Fix:** Always `cd` to main repo root before `git worktree remove`\n\n**Cleaning up harness-owned worktrees**\n- **Problem:** Removing a worktree the harness created causes phantom state\n- **Fix:** Only clean up worktrees under `.worktrees\u002F`, `worktrees\u002F`, or `~\u002F.config\u002Fsuperpowers\u002Fworktrees\u002F`\n\n**No confirmation for discard**\n- **Problem:** Accidentally delete work\n- **Fix:** Require typed \"discard\" confirmation\n\n## Red Flags\n\n**Never:**\n- Proceed with failing tests\n- Merge without verifying tests on result\n- Delete work without confirmation\n- Force-push without explicit request\n- Remove a worktree before confirming merge success\n- Clean up worktrees you didn't create (provenance check)\n- Run `git worktree remove` from inside the worktree\n\n**Always:**\n- Verify tests before offering options\n- Detect environment before presenting menu\n- Present exactly 4 options (or 3 for detached HEAD)\n- Get typed confirmation for Option 4\n- Clean up worktree for Options 1 & 4 only\n- `cd` to main repo root before worktree removal\n- Run `git worktree prune` after removal\n",{"name":5,"description":7},"main","b84fb2b9810cd71df8350a0e52486c5327c2c929","packages\u002Fagent-runtime\u002Ffixtures\u002Fpersonal-plugins\u002Fsuperpowers\u002Fskills\u002Ffinishing-a-development-branch",115,"https:\u002F\u002Fgithub.com\u002Ftabtin-ai\u002FTabTin","https:\u002F\u002Fwww.tabtin.com\u002F","https:\u002F\u002Fgithub.com\u002Ftabtin-ai","People, teammates, and Agents, meeting in one workspace. \u002F 你、搭子、Agent，在同一工作区里碰头。","2026-10-08 06:44:53",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add tabtin-ai\u002FTabTin --skill finishing-a-development-branch",{"tool":39,"command":40},"bunx","bunx skills add tabtin-ai\u002FTabTin --skill finishing-a-development-branch",{"tool":42,"command":43},"pnpm","pnpm dlx skills add tabtin-ai\u002FTabTin --skill finishing-a-development-branch","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftabtin-ai\u002FTabTin\u002Fblob\u002Fmain\u002Fpackages\u002Fagent-runtime\u002Ffixtures\u002Fpersonal-plugins\u002Fsuperpowers\u002Fskills\u002Ffinishing-a-development-branch\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"agents\u002Fopenai.yaml","REFERENCE","参考文档",149,"https:\u002F\u002Fgithub.com\u002Ftabtin-ai\u002FTabTin\u002Fblob\u002Fmain\u002Fpackages\u002Fagent-runtime\u002Ffixtures\u002Fpersonal-plugins\u002Fsuperpowers\u002Fskills\u002Ffinishing-a-development-branch\u002Fagents\u002Fopenai.yaml",[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7AV7T04TVTA6639VSJA1MDM","tabtracker","管理自动化任务——创建、列出、暂停、恢复、立即触发（产品模块名「自动化」， 具体条目称「自动化任务」；CLI 命令仍为 tabtin tracker）。当用户表达\"派活\"意图时使用： 关键词包括\"帮我...\"、\"以后...\"、\"每天...\"、\"工作日...\"、 \"提醒我...\"、\"定时...\"、\"每周...\"。区分一次性指令（直接执行）和长期任务（创建 自动化任务，由调度器在指定时间唤起 Agent）。","https:\u002F\u002Fgithub.com\u002Ftabtin-ai\u002FTabTin\u002Fblob\u002Fmain\u002Fpackages\u002Fskills\u002Ftabtracker\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7AV7NXF303AF687GR2RZPG3","tabtin-project","在 Project Task 执行会话中工作：先读取当前任务工作面，再优先修改既有中间产物。 当系统上下文表明当前会话是 Project Task，或用户要求继续修改过程中的中间产物时使用。","https:\u002F\u002Fgithub.com\u002Ftabtin-ai\u002FTabTin\u002Fblob\u002Fmain\u002Fpackages\u002Fskills\u002Ftabtin-project\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7AV7JYFJ6HN80D12TGMMSTF","skill-market","管理 Skill 生命周期——列出已装、看详情、搜索市场、 安装、卸载、启用、禁用、更新。当用户表达\"装个技能 \u002F 卸载技能 \u002F 看看有什么技能 \u002F 启用禁用技能\"意图时使用。","https:\u002F\u002Fgithub.com\u002Ftabtin-ai\u002FTabTin\u002Fblob\u002Fmain\u002Fpackages\u002Fskills\u002Fskill-market\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7AV7F28TS1PCC9XE0859AVM","tabtin-widget","渲染可视化组件——用 show_widget 编译 SVG \u002F HTML(no-script) \u002F Mermaid 图做自由可视化。内容能落 present_to_user 4 类 kind → 不用 widget；长期可编辑产物 → TabData\u002F TabDoc\u002FTabSlide。","https:\u002F\u002Fgithub.com\u002Ftabtin-ai\u002FTabTin\u002Fblob\u002Fmain\u002Fpackages\u002Fskills\u002Fbundled\u002Fplatform\u002Fvisualization\u002Ftabtin-widget\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7AV7AWNVX8A2RXRX675350G","resource-link","插入资源链接——在 chat 文字流里给资源链接，markdown link 形态 [显示文本](tabtin:\u002F\u002Fresource\u002F\u003Ctype>\u002F\u003Cid>?hint=\u003CcarrierApp>)， 用户点击直接在 Space 内打开。行业格式（http\u002Fhttps\u002F file\u002Fmailto）也兼容；不要写 file:\u002F\u002F 让用户自己复制粘贴。","https:\u002F\u002Fgithub.com\u002Ftabtin-ai\u002FTabTin\u002Fblob\u002Fmain\u002Fpackages\u002Fskills\u002Fbundled\u002Fplatform\u002Fvisualization\u002Fresource-link\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7AV77XTH24EH30RYN9N5TKB","mcp-operations","操作本机 MCP 连接——通过 `tabtin mcp` CLI 查看当前 Space 已挂载的本机 MCP servers、tools\u002Fresources\u002F prompts，并用 `mcp_call_tool` 调用指定 MCP tool。 用户提到\"使用 Playwright MCP\"\"调用本机安装的 MCP 工具\"\"读取某个 MCP resource\"\"获取某个 MCP prompt\"时激活。","https:\u002F\u002Fgithub.com\u002Ftabtin-ai\u002FTabTin\u002Fblob\u002Fmain\u002Fpackages\u002Fskills\u002Fbundled\u002Fplatform\u002Fmcp\u002Foperations\u002FSKILL.md",[],[]]