- name
SKILL.md
技能文件保留在发布者的仓库中。
在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add glebis/claude-skills --skill bridgework -a cursor -y在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add glebis/claude-skills --skill bridgework -a claude-code -y在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add glebis/claude-skills --skill bridgework -a codex -y在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add glebis/claude-skills --skill bridgework -a grok -y在 Grok Bot 聊天中发送复制的消息。Bot 会从 GitHub 获取这个 SKILL.md,并添加到你所有 Bot 共享的技能中。
Install this skill: https://github.com/glebis/claude-skills/tree/HEAD/bridgework来自发布者
Two phases: audit the person's stack into a stack file, then serve the Bridgework canvas on it. The canvas runs locally, connects to nothing and calls no model. Every step in it can produce a prompt (Sources, Ideas or Build) to paste into an agent.
Everything about the person lives in ~/.bridgework/, never in this skill folder. The skill's own demo is synthetic.
audit.py with a category the person has not agreed to in this conversation. Show the plan first.e2e-verified unless the person ran it.scripts/serve.sh demo (port 4174) in the background and open it. Skip if the person wants their own stack straight away.python3 scripts/audit.py --plan and show the person what each category reads. Then ask, with a multi-select question, which categories to allow: apps, clis, mcp, models, keys, or none (interview only). Explain that keys lists variable names such as OPENAI_API_KEY and never their values.python3 scripts/audit.py --categories <agreed> writes ~/.bridgework/audit.json and prints a summary. Without --categories it reads nothing.references/interview.md: confirm the matches, pick relevant unmatched items, then ask about what a scan cannot see (phone and watch data, hosted accounts, other machines, known dead ends). Keep it short: three or four questions per round, two rounds at most.~/.bridgework/stack.json. Catalog tools use {"use": "<id>"} and keep the audit's signals. Anything else becomes a custom part, classified with the types, domains and places in references/stack-format.md. Record known dead ends as gaps so they are drawn broken, never as working arrows.python3 scripts/build_stack.py ~/.bridgework/stack.json builds ~/.bridgework/site. It validates everything first; on errors it lists each problem and writes nothing. Fix the stack file and rerun.scripts/serve.sh serves the site on http://localhost:4175 (run it in the background). The demo uses 4174, so the two keep separate saved trails.To update later, rerun the audit (with permission again) and the interview for what changed, edit stack.json, and rebuild. The builder only replaces a folder it created.
scripts/audit.py: consent-gated, read-only scan. --plan reads nothing. --home and --root point it at a test folder.scripts/catalog.json: about 50 known tools, each with read-only detection rules and a takes/does/gives template. Add a tool here when the same unknown keeps coming up.scripts/build_stack.py: stack file to site, with validation. Keeps built-in examples and unlocks only when all their parts exist.scripts/serve.sh: local server. demo, your site, or any folder and port.references/interview.md: interview questions, consent wording, and how to read the audit.references/stack-format.md: stack file format and the allowed types, domains, places and evidence levels.assets/app/: the canvas, with the synthetic demo in data/. assets/app/INTERACTION.md explains the interaction design. Tests: npm test there, and PORT=4174 sh tests/run-browser.sh with the demo served (needs Playwright and Chrome).This skill should be used when someone wants to see what their tech stack could do in combination. It first audits the stack (an optional, consent-gated, read-only scan of this Mac plus a short interv
---name: bridgeworkdescription: This skill should be used when someone wants to see what their tech stack could do in combination. It first…---# bridgework/SKILL.md概览
This skill should be used when someone wants to see what their tech stack could do in combination. It first audits the stack (an optional, consent-gated, read-only scan of this Mac plus a short interview), then builds and serves Bridgework, a local canvas for practising "what could these two capabilities do together?", with a prompt for an agent at every step. Triggers on "audit my stack", "what could my tools do together", "map my tech stack", "find combinations in my stack", "bridgework", "open the bridgework canvas", or "show the bridgework demo".
常见问题
从发布者处下载 bridgework/SKILL.md,或复制路径后打开仓库。PlugMCP 只收录该技能,不托管文件。
发布者将它存放在 https://github.com/glebis/claude-skills。
Claude、Cursor、Codex 和 Grok Build 可以读取你从发布者仓库添加的 SKILL.md。在聊天中发送技能的 GitHub 文件夹链接,Grok Bot 就会安装它。