Claude-Guardian
Claude Guardian is an all-in-one Claude account safety and risk prevention skill. It intelligently assesses your device, account history, network environment, and payment options, then provides person
翻譯準備中
尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證Let Claude Code or Codex draw real Excalidraw diagrams — flowcharts, wireframes, slide decks, SWOT, Lean Canvas & 17 official use cases. Install: npx skills add NicholasSpisak/excalidraw
翻譯準備中
取自儲存庫 README
正在載入完整 README。 以下為已儲存的摘錄。
Create and edit Excalidraw diagrams from Claude Code, Codex, or any agent
harness — flowcharts, architecture diagrams, sequence diagrams, UML, Gantt
charts, mind maps, wireframes, slide decks, roadmaps, personas,
brainstorming boards, Lean Canvas, SWOT and competitor analyses, and
game-design boards, aligned with the official
Excalidraw use cases.
Backed by the official Excalidraw+ MCP server — scenes are created in your
Excalidraw+ workspace, verified by screenshot, and returned as links.
Works with the Vercel skills framework;
installs for Claude Code, Codex, and other supported agents.檢視完整 README ↗Create and edit Excalidraw diagrams from Claude Code, Codex, or any agent harness — flowcharts, architecture diagrams, sequence diagrams, UML, Gantt charts, mind maps, wireframes, slide decks, roadmaps, personas, brainstorming boards, Lean Canvas, SWOT and competitor analyses, and game-design boards, aligned with the official Excalidraw use cases.
Backed by the official Excalidraw+ MCP server
(https://api.excalidraw.com/api/v1/mcp) — scenes are created in your
Excalidraw+ workspace, verified by screenshot, and returned as links.
npx skills add NicholasSpisak/excalidraw
Works with the Vercel skills framework; installs for Claude Code, Codex, and other supported agents.
You need an Excalidraw+ API key (Excalidraw+ → Settings → API keys). Never commit it. Provide it one of two ways:
# environment variable (works for the bundled CLI and Codex MCP config)
export EXCALIDRAW_API_KEY=sk-...
# or a key file the bundled CLI falls back to
mkdir -p ~/.config/excalidraw
printf '%s\n' 'sk-...' > ~/.config/excalidraw/api_key
chmod 600 ~/.config/excalidraw/api_key
The skill works out of the box through its bundled CLI. For native MCP tool calling, add the official server config:
Claude Code (~/.claude.json or .mcp.json):
{
"mcpServers": {
"excalidraw": {
"type": "http",
"url": "https://api.excalidraw.com/api/v1/mcp",
"headers": {
"Authorization": "Bearer <API_KEY>"
}
}
}
}
Codex (~/.codex/config.toml):
[mcp_servers.excalidraw]
url = "https://api.excalidraw.com/api/v1/mcp"
env_http_headers = { Authorization = "EXCALIDRAW_API_KEY" }
With env_http_headers, the env var's value is injected verbatim as the
header — set EXCALIDRAW_API_KEY="Bearer sk-...". (Codex's
bearer_token_env_var alternative takes the raw key and adds Bearer
itself. The bundled CLI accepts either form.)
node scripts/excal.mjs tools # list available tools
node scripts/excal.mjs help create_diagram # print a tool's input schema
node scripts/excal.mjs call create_diagram --json '{"sceneId":"...","nodes":[...],"edges":[...]}'
Zero dependencies; Node ≥ 18.
SKILL.md the skill: transport choice, workflow, rules
scripts/excal.mjs MCP-over-HTTP CLI (auth via env var or key file)
references/use-cases.md layout playbook per Excalidraw use case
references/api.md tool catalog notes and sharp edges
MIT
Enjoy putting AI to work like this? It's what we teach business owners every day inside AI Operator Academy — practical AI systems, no engineering degree required.