*p5.brush
p5.js 환경에서 자연스러운 텍스처를 탐구하는 아티스트·디자이너·취미자를 위한 다목적 라이브러리
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기The official SDRPilot plugin for Claude Code: a playbook skill plus the MCP connection to your own workspace, with live help docs.
저장소 README에서 가져옴
README 전체를 불러오는 중입니다. 아래는 저장된 발췌입니다.
Let Claude work inside your own SDRPilot workspace, and know what it is doing while it is there.
1. The connection. The MCP server for your workspace, authenticated with your own API key.
2. A skill. The playbook Claude reads first: how SDRPilot is put together (your ICP, scoring, the connection queue, conversations), the common workflows step by step, and what it must ask you before doing.
3. Live help docs. The server gives Claude docs_search, docs_read and docs_list, which read the help site as it is today. When we ship a feature and document it, Claude can look it up the same day.README 전문 보기 ↗Let Claude work inside your own SDRPilot workspace, and know what it is doing while it is there.
The plugin bundles three things:
docs_search, docs_read and docs_list, which read the help site as it is today. When we ship a feature and document it, Claude can look it up the same day.You need Claude Code, an SDRPilot workspace and your API key. In SDRPilot, open Settings, then API and AI assistants.
claude plugin marketplace add sdrpilot/claude-plugin
claude plugin install sdrpilot@sdrpilot
Then give the plugin your key. Start claude and run:
/plugin configure sdrpilot@sdrpilot
Paste the key when it asks. It is stored in your system keychain, not in a file. Restart Claude Code afterwards so the connection picks it up.
Check that it works: start claude, run /mcp and look for the server marked connected, then ask something like "how is my outreach doing this week?".
The skill tells Claude to preview before it applies, to show you what will change, and to get your explicit go before anything that reaches a real person on LinkedIn (a connection request, a message, accepting a request, publishing a post), anything that cannot be undone, and anything that spends credits. It is also told to put the safety of your LinkedIn account first: no switching off warm-up, no raising limits unless you ask.
Your API key is the access control: Claude can do what the key can do.
claude plugin marketplace update sdrpilot, then claude plugin update sdrpilot@sdrpilot. The help docs need no update, Claude reads them live.claude plugin uninstall sdrpilot@sdrpilot.python3 scripts/check.py --live # wording rules, every tool name the skill mentions exists on the live server
claude plugin validate . --strict # the marketplace
claude plugin validate ./plugins/sdrpilot --strict # the plugin
Every statement in the skill must be backed by the help docs, and anything that can change (limits, prices, what is in beta) belongs in the docs, not in the skill. Bump version in plugins/sdrpilot/.claude-plugin/plugin.json when the skill or the MCP config changes, otherwise installed copies do not update.