- 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".
FAQ
게시자에게서 bridgework/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/glebis/claude-skills에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.