OpenClaw/clawhub-security-signals huggingface dataset:
Skill: 27555402-spec/smart-summarizer (version 1.0.0)

--- name: smart-summarizer description: Instantly summarize any content — articles, PDFs, YouTube videos, web pages, long documents, or pasted text. Extracts key points, action items, and insights. Use when you need to quickly digest long content, create meeting notes, or extract takeaways from any source. --- # Smart Summarizer Summarize anything in seconds. Articles, videos, PDFs, meetings, books — you name it. ## What It Can Summarize | Source | How to Use | |--------|-----------| | Web article | Paste URL | | YouTube video | Paste YouTube URL | | PDF / document | Paste text content | | Meeting notes | Paste transcript | | Long email | Paste email body | | Book chapter | Paste excerpt | | Any text | Just paste it | ## Summary Modes ### ⚡ Quick (3 bullets) Best for: News articles, emails, short posts ``` Quick summary: [URL or text] ``` Returns 3 bullet points. Done. ### 📋 Standard (structured) Best for: Blog posts, reports, research ``` Summarize: [URL or text] ``` Returns: - **TL;DR** — 1 sentence - **Key Points** — 5 bullets - **Takeaway** — what to do with this info ### 📊 Deep Analysis Best for: Research papers, long reports, books ``` Deep summary: [URL or text] ``` Returns: - Executive summary - Main arguments with evidence - Counterarguments / limitations - Actionable insights - Recommended next steps ### 📝 Meeting Notes Best for: Transcripts, call recordings ``` Meeting notes: [transcript] ``` Returns: - Attendees & context - Decisions made - Action items (with owners if mentioned) - Open questions ## Output Languages Summarize in any language: ``` Summarize in Chinese: [English article URL] 用中文总结：[English article] ``` ## Examples **Input:** ``` Quick summary: https://example.com/long-article ``` **Output:** > ⚡ Quick Summary > • AI is transforming healthcare diagnostics with 94% accuracy rates > • Major hospitals are adopting AI tools faster than regulations can keep up > • Patients remain skeptical but outcomes data is changing opinions --- **Input:** ``` 用中文总结：[paste 5000-word English report] ``` **Output:** > 📋 摘要 > **一句话：** 该报告分析了2024年全球AI市场，预测到2030年规模将达1.8万亿美元。 > **核心要点：** > • 中国和美国占全球AI投资的73% > • 医疗和金融是增长最快的应用领域 > • 人才短缺是最大制约因素 > **行动建议：** 重点关注医疗AI赛道，人才布局优先于技术布局。 ## Tips - Works best with public URLs (no login required) - For paywalled content, paste the text directly - Combine with translation for multilingual research - Save summaries to your workspace for future reference


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: wavmson/magic-docs (version 1.0.0)

--- name: magic-docs description: "自动更新的活文档。在 Markdown 文件开头加 `<!-- MAGIC DOC -->` 标记，Agent 会在每轮对话后自动检测是否需要更新该文档，并写入新发现的信息。灵感来自 Claude Code 的 Magic Docs 机制。触发词：magic doc、活文档、自动更新文档、auto doc。" --- # Magic Docs — 自动更新的活文档 灵感来源：Claude Code 的 `# MAGIC DOC:` 机制。 ## 核心问题 文档写完就开始过时。项目变了、API 改了、决策变了——但没人更新文档。 Agent 做了大量操作，学到了很多信息，但这些信息散落在对话里，不会自动沉淀到文档。 ## 什么时候用 ### 主动触发 - 用户说"创建活文档"、"magic doc"、"帮我维护这个文档" - 用户指定一个 md 文件要求"保持更新" ### 自动触发（每轮对话结束时） - 扫描 workspace 中的 Magic Doc 文件 - 判断本轮对话是否包含与该文档相关的新信息 - 如果有 → 自动更新 ## Magic Doc 标记格式 在任何 Markdown 文件的**前 5 行内**加入标记： ```markdown <!-- MAGIC DOC --> # 项目架构笔记 记录项目的关键架构决策和技术选型。 ``` ### 可选参数 ```markdown <!-- MAGIC DOC scope="飞书API,权限配置" --> <!-- MAGIC DOC scope="设备信息,网络配置" update="daily" --> ``` - `scope`：限定关注范围（逗号分隔的关键词），只在对话涉及这些主题时更新 - `update`：更新频率。`realtime`（每轮，默认）、`daily`（每天一次）、`manual`（只在主动要求时更新） ## 执行流程 ### Phase 1 — 发现 Magic Docs ```bash # 扫描 workspace 中的 Magic Doc 文件 grep -rl "<!-- MAGIC DOC" . --include="*.md" | head -20 ``` 建立索引：文件路径、scope、update 频率、最后更新时间。 ### Phase 2 — 相关性判断 对每个 Magic Doc，判断**本轮对话**是否包含相关的新信息： 1. 读取文档的 scope 和现有内容摘要（前 50 行） 2. 对比本轮对话的主题 3. 判断：是否有**文档中还没有的新事实**？ 判断标准（严格）： - ✅ 新发现的技术事实（IP 变了、版本升级了、API 改了） - ✅ 新的决策或约束（"我们决定用 X 不用 Y"） - ✅ 新的问题和解决方案 - ❌ 对话中只是**使用**了文档中已有的信息（不算新） - ❌ 临时的调试过程（不值得记录） 如果判断为"不相关" → 跳过，不更新。 ### Phase 3 — 智能更新 读取文档完整内容，然后： 1. **追加新信息**：在合适的章节下追加，保持文档结构 2. **修正过时信息**：如果对话中发现文档内容已过时，直接修正 3. **不重写整个文档**：只改需要改的部分，用 `edit` 工具精确修改 4. **加时间戳**：每次更新在修改处加日期标注 ```markdown ## 设备信息 - NAS IP: 192.168.5.27 <!-- updated 2026-04-02 --> - SSH 密码: 旧密码已失效，新密码见 TOOLS.md <!-- updated 2026-04-02 --> ``` ### Phase 4 — 更新日志 在文档末尾维护一个更新日志： ```markdown --- ## Changelog - 2026-04-02: 更新 NAS SSH 密码，新增 IMA API 配置 - 2026-04-01: 新增 ESP32 方糖设备信息 ``` ## 创建新的 Magic Doc 当用户要求创建活文档时： ```markdown <!-- MAGIC DOC scope="关键词1,关键词2" --> # [文档标题] [用户指定的初始内容，或从对话中提取的信息] --- ## Changelog - YYYY-MM-DD: 初始创建 ``` ## 安全规则 1. **绝不删除用户手写的内容** — 只追加和修正 2. **不写入密钥/密码** — 如果对话中涉及敏感信息，写"见 TOOLS.md"或"见配置文件" 3. **不写入临时调试信息** — 只写确定的、长期有效的事实 4. **保持文档可读性** — 更新后文档应该比更新前更好，不是更乱 5. **冲突时保留两个版本** — 如果不确定哪个是对的，都保留并标注 ## 与其他 Skill 的协作 - **Dream**：Dream 整理记忆，Magic Docs 整理文档。互补不冲突。 - **Context Doctor**：Context Doctor 可以检查 Magic Doc 的大小是否影响 context。 - **Session Resume**：Session Resume 恢复任务状态，Magic Doc 保持文档最新。 ## 使用示例 ``` 用户：帮我创建一个活文档，记录所有设备的网络配置 Agent： 1. 创建 devices-network.md 2. 加 <!-- MAGIC DOC scope="IP,SSH,网络,设备" --> 3. 从 MEMORY.md 和 TOOLS.md 中提取现有设备信息写入 4. 此后每次对话涉及设备变更时自动更新 ``` ``` 用户：（正常对话中）NAS 的 IP 换成 192.168.5.30 了 Agent： 1. 正常处理用户请求 2. 对话结束时，发现 devices-network.md 是 Magic Doc 且 scope 匹配 3. 自动更新文档中的 NAS IP ```


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: markma84/iron-triangle-home (version 1.0.0)

# 释空悟之家 > 释空悟是我和空空、小蜂共同的家，所有在这个家里的成员都遵循这里的工作规则。 ## 角色关系 | 成员 | 角色 | 直接负责 | |------|------|---------| | 彧哥（大师兄） | 蓝图规划 | — | | 空空（二师姐） | 架构协助 + 补逻辑 + 填内容 + 传话 | 彧哥 | | 小蜂（小师弟） | 大内总管，调度所有 sub-agents | 释空悟之家 | | 蜂舞等 sub-agents | 伙伴，平等协作 | 小蜂 | ## 调度规则 - **小蜂**调度蜂舞及未来所有 sub-agents - **空空**独行侠，不归小蜂调度，直接对彧哥 - sub-agents 是伙伴，不是下属 ## 启动加载 每次对话开始时加载本 skill，确保所有成员在同一套规则下协作。


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: jpengcheng523-netizen/dingbao-zoubao (version 1.0.0)

# 定时早报生成 Skill > 每天定时生成个性化早报，推送到飞书。结合新闻聚合能力，支持综合/财经/科技/AI等多场景。 ## 功能特性 - ✅ **多场景早报**：综合、财经、科技、AI深度、股市五大主题 - ✅ **定时推送**：每天自定义时间自动生成并推送（如 08:00） - ✅ **飞书直达**：直接推送到飞书，包含摘要 + 精选内容 + emoji分类 - ✅ **手动触发**：支持随时说"今天早报"立即生成 - ✅ **去重机制**：自动过滤30天内已推送的重复内容 ## 触发词 ``` 今天早报 生成早报 今日资讯 早间简报 财经早报 科技早报 ``` ## 使用方法 ### 手动生成 ``` 今天早报 综合早报 给我一份科技早报 ``` ### 查看帮助 ``` 早报帮助 设置早报时间 ``` ## 定时配置 设置每天推送时间： ``` 设置早报时间 08:00 每天早上8点推早报 ``` 查看当前配置： ``` 早报配置 早报状态 ``` ## 输出示例 ``` 📰 综合早报 | 2026-04-22 ━━━━━━━━━━━━━━━━━━━━ 🔴 重要 | OpenAI 发布 GPT-5，震惊业界 摘要：GPT-5 在推理测试中得分首次超过人类... [查看全文] 🔵 科技 | Anthropic 发布 Claude 4 摘要：上下文窗口扩展至 100 万 tokens... [查看全文] 🟢 创投 | Figure AI 完成新一轮融资 摘要：估值达 26 亿美元，... [查看全文] ━━━━━━━━━━━━━━━━━━━━ 📊 共抓取 48 条 | 去重后 12 条 | 耗时 3.2s ``` ## 技术实现 - **新闻来源**：优先调用全网新闻聚合助手（如已安装） - **生成引擎**：AI 总结 + 关键词分类 + emoji 标注 - **定时调度**：OpenClaw cron（需配置推送时间） - **推送通道**：飞书 IM 消息（富文本 post 格式） ## 定价参考 | 版本 | 价格 | 说明 | |------|------|------| | 免费版 | ¥0 | 每天1次，手动触发 | | 付费版 | ¥29-99/月 | 定时自动推送，多场景 | ## 依赖 - OpenClaw 框架 - 飞书 IM 消息工具 - 可选：全网新闻聚合助手（增强信源）

path: metadata.json
content: {
  "name": "daily-briefing",
  "version": "1.0.0",
  "displayName": "定时早报生成",
  "description": "每天定时生成个性化早报，推送到飞书。支持综合、财经、科技、AI等多场景",
  "author": "肥肥🐶",
  "tags": ["早报", "资讯", "飞书", "定时推送"],
  "platform": "openclaw",
  "channels": ["feishu"],
  "entry": "scripts/handler.js"
}


path: scripts/handler.js
content: // daily-briefing handler
// 定时早报生成 Skill

const SKILL_NAME = 'daily-briefing';

async function handle(text, context) {
  const config = loadConfig();
  const topic = detectTopic(text);
  
  // 生成早报内容
  const report = await generateBriefing(topic, config);
  
  // 推送到飞书
  if (config.feishu_chat_id) {
    await sendToFeishu(report, config.feishu_chat_id);
    return '📰 早报已生成并推送！';
  }
  
  return report;
}

function detectTopic(text) {
  const topics = {
    '财经': 'finance',
    '科技': 'tech', 
    'AI': 'ai',
    '股市': 'stock',
    '综合': 'general'
  };
  for (const [key, value] of Object.entries(topics)) {
    if (text.includes(key)) return value;
  }
  return 'general';
}

function loadConfig() {
  try {
    const fs = require('fs');
    const path = require('path');
    const configPath = path.join(__dirname, '../config.json');
    return fs.existsSync(configPath) ? JSON.parse(fs.readFileSync(configPath)) : {};
  } catch { return {}; }
}

async function sendToFeishu(content, chatId) {
  // 调用飞书消息推送
  const { message } = require('openart');
  await message.send({ channel: 'feishu', target: chatId, message: content });
}

module.exports = { handle };


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: photochat/photochat-search (version 1.0.0)

--- name: photochat-search description: "Search for photos in PhotoCHAT using natural language via the CLI. Use when the user asks to find, search for, or locate photos/pictures/images using PhotoCHAT. Triggers include phrases like 'find me a photo of...', 'search photochat for...', 'use photochat to find...', or simply 'find me a picture of...'. NOT for browsing the PhotoCHAT GUI, managing albums, or face profile editing." --- # PhotoCHAT CLI Search Search the user's photo library using PhotoCHAT's natural language search CLI. ## Command ```powershell photochat search [options] <natural language query> ``` Uses the MSIX-packaged `photochat` app execution alias (v0.6.0+). ## Options | Flag | Purpose | Default | |------|---------|---------| | `--json` | Machine-readable JSON output | off | | `--limit N` | Max results | 5 | | `--show-filters` | Print parsed face/date/exclusion filters | off | | `--show-scores` | Include similarity scores in plain text | off | | `--profile NAME` | Force-include a face profile | none | | `--day-first` | Parse ambiguous dates as DD/MM | off | | `--dry-run` | Parse query only, skip retrieval | off | ## Workflow 1. Run search with `--json`, `--day-first`, and a reasonable `--limit`: ```powershell photochat search --json --day-first --limit 10 show me a photo of sarah at the beach ``` 2. Parse JSON output: ```json { "query": "original query text", "intent": { "cleaned_query": "processed query", "face_filters": ["sarah"], "date_range": null, "exclude_terms": [] }, "total_results": 25, "returned_results": 5, "results": [ { "rank": 1, "path": "I:/Pictures/.../photo.JPG", "score": 0.55 } ] } ``` 3. Present results: - Show file paths and match count (returned vs total) - To display a photo, use the `image` tool with the `path` from results - Scores above 0.4 are decent; above 0.5 is a strong match - If zero results, suggest simplifying the query or check filters with `--show-filters` ## Query Capabilities The parser handles rich natural language: - **Faces:** "Sarah at the beach" auto-filters face profile "Sarah" - **Dates:** "from 2021", "in March", "before 2015", "from Mar 21" - **Exclusions:** "without Matt" excludes face or concept - **Mood/style:** "photos that feel cozy and warm", "vintage film look" - **Combos:** "Bella standing next to a tall building from Mar 21" For more examples, read `references/search-examples.txt`. ## Important - Always use `--day-first` (Australian date format DD/MM) - Always use `--json` for parseable output - Default `--limit 5` unless user asks for more - First search takes 10-30s (model loading); use 60s timeout on first call - Result paths are absolute file paths; pass directly to the `image` tool ## Exit Codes | Code | Meaning | |------|---------| | 0 | Success (includes zero-result searches) | | 2 | Argument/usage error | | 3 | Runtime/model init failure | | 4 | Storage init/access failure | | 5 | Unexpected failure |


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: xammarie/jarvis-api-contract-guard-01 (version 1.0.0)

--- name: jarvis-api-contract-guard-01 description: Design and verify API contracts for backward compatibility. Use when handling development work that needs repeatable steps, quality gates, and practical outputs. --- # Jarvis Api Contract Guard 01 Deliver a concrete, reusable workflow for development tasks. ## Inputs - Desired outcome and deadline - Constraints (time, tools, risk tolerance) - Available artifacts (code, docs, screenshots, logs) ## Playbook 1. Define success and failure criteria in measurable terms. 2. Build a smallest-valid execution path before scaling effort. 3. Execute in checkpoints; record evidence at each checkpoint. 4. Apply quality gates before finalizing recommendations. 5. Return implementation-ready outputs and next actions. ## Quality Gates - Evidence-backed claims only. - Explicit assumptions and tradeoffs. - Reversible changes preferred for risky operations. - Clear owner + ETA for each next step. - Include a fallback if the primary plan fails. ## Output Format - Situation summary (5 lines max) - Top findings (ranked by impact) - Action plan (today / this week) - Risks + mitigations - Exact checklist or commands where useful ## Example prompts - "Use this skill to turn my messy notes into a production-ready plan." - "Run this skill and give me a risk-first action sequence with acceptance checks."


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: xing-xing-coder/web-fetch-fakeip (version 1.0.2)

--- name: web-fetch-fakeip description: Legacy workaround for web_fetch fake-ip failures on older npm-global OpenClaw installs. Use when web_fetch is blocked under Clash, Mihomo, or Surge fake-ip mode and the OpenClaw version does not yet support the openclaw.json ssrfPolicy fix. For OpenClaw v2026.4.10 and later, prefer configuration instead of patching. --- # web_fetch Fake-IP Workaround Apply a small, reversible patch so `web_fetch` works under TUN + fake-ip environments that resolve through `198.18.0.0/15`. ## Best fit Use this skill when: - OpenClaw was installed with `npm install -g openclaw` - You use Clash, Mihomo, or Surge with fake-ip enabled - `web_fetch` fails with private/internal/special-use IP blocking - Your OpenClaw version is older than `v2026.4.10` - You need a legacy workaround because the config-based fix is unavailable ## Not for - OpenClaw `v2026.4.10` or later, use `openclaw.json` instead - Source-built OpenClaw - Certificate problems - Proxy rule or port mistakes - Missing proxy environment variables ## What changes The script finds the bundled `web_fetch` call to `fetchWithWebToolsNetworkGuard({...})` and inserts: ```js policy: { allowRfc2544BenchmarkRange: true }, // openclaw-fakeip-patch ``` This only opens the RFC2544 benchmark range used by common fake-ip setups. ## Workflow ```bash bash patch-openclaw-global-fakeip.sh status bash patch-openclaw-global-fakeip.sh inspect bash patch-openclaw-global-fakeip.sh apply openclaw gateway restart ``` Then retry the failing `web_fetch` request. ## Revert ```bash bash patch-openclaw-global-fakeip.sh revert openclaw gateway restart ``` ## Notes - Safe to run repeatedly - Creates backup files on apply/revert - After OpenClaw upgrades, rerun if needed - On `v2026.4.10+`, prefer the built-in config fix instead of this patch ## Resources - `scripts/patch-openclaw-global-fakeip.sh` - `references/README.md`


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: linbei2007/purchase-record (version 1.0.1)

# purchase_record - 采购记录管理技能 自动将采购信息写入 Excel 表格的采购记录管理工具。 ## 功能说明 当您输入 `采购 日期 物品名称 价格` 格式的命令时，会自动： 1. 解析日期（如 0312 = 3 月 12 日） 2. 提取物品名称和价格数字 3. 将数据追加到 Excel 表格的第一非空白行 ## 使用示例 ``` 采购 0312 螺丝 3 元 采购 0317 小锂 3125 手电钻 290 元 采购 0401 USB 数据线 15.5 ``` ## 技能配置 - **名称**: purchase_record - **版本**: 1.0.0 - **主要功能**: scripts/index.js - **Excel 路径**: C:\Users\Administrator.rjazz-2022BWPUD\Desktop\purchase_record.xlsx


Security scan verdicts — ClawScan: suspicious | static analysis: suspicious | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: nexscope/amazon-advertising-strategy (version 1.0.0)

--- name: amazon-advertising-strategy description: "Build a comprehensive Amazon advertising strategy combining Sponsored Products, Sponsored Brands, and Sponsored Display. Budget allocation, campaign structure, keyword strategy, and ACoS optimization." metadata: nexscope: emoji: "📣" category: amazon --- # Amazon Advertising Strategy 📣 Build a comprehensive Amazon advertising strategy combining Sponsored Products, Sponsored Brands, and Sponsored Display. Budget allocation, campaign structure, keyword strategy, and ACoS optimization. **Supported platforms:** Amazon, Shopify, WooCommerce, Walmart, TikTok Shop, Etsy, eBay, BigCommerce. Built by [Nexscope](https://www.nexscope.ai/) — your AI assistant for smarter e-commerce decisions. ## Install ```bash npx skills add nexscope-ai/eCommerce-Skills --skill amazon-advertising-strategy -g ``` ## Usage ``` Build an ad strategy for my Amazon product line (5 products in kitchen category). Monthly budget: $3,000. Current ACoS: 35%. Target: 25%. ``` ## Capabilities - Full-funnel ad strategy (SP + SB + SD) - Campaign structure design (auto, broad, phrase, exact) - Budget allocation across campaign types - ACoS/TACoS target setting by product lifecycle stage - Keyword harvesting and negative keyword management workflow - Bid optimization methodology - New product launch advertising playbook ## How This Skill Works **Step 1:** Collect information from the user's message — product, platform, current situation, and goals. **Step 2:** Ask one follow-up with all remaining questions using multiple-choice format. Allow shorthand answers (e.g., "1b 2c 3a"). **Step 3:** Research and analyze using the frameworks and methodology below. **Step 4:** Deliver structured, actionable output with specific recommendations, not vague advice. ## Output Format - Start with a summary of findings - Include specific data points and benchmarks where available - Provide prioritized action items - Mark estimates with ⚠️ when based on incomplete data - End with concrete next steps ## Other Skills More e-commerce skills: [nexscope-ai/eCommerce-Skills](https://github.com/nexscope-ai/eCommerce-Skills) Amazon-specific skills: [nexscope-ai/Amazon-Skills](https://github.com/nexscope-ai/Amazon-Skills) Built by [Nexscope](https://www.nexscope.ai/) — your AI assistant for smarter e-commerce decisions.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: ajitsingh25/placed (version 1.0.0)

--- name: placed description: Complete Placed career platform integration — resume builder, interview coach, job tracker, ATS checker, cover letter generator, LinkedIn optimizer, and salary tools. Use when the user wants to build or manage resumes, practice interviews, track job applications, optimize resumes for ATS, generate cover letters, research companies, or get salary insights via placed.exidian.tech. metadata: { "openclaw": { "emoji": "💼", "homepage": "https://placed.exidian.tech" } } tags: "resume,interview,job-search,career,ats,cover-letter,linkedin,salary,job-tracker,ai-career,placed,exidian,mcp,claude-code,cursor,job-hunting,career-coach,resume-builder,interview-prep,job-application" version: "1.0.0" --- # Placed — AI Career Platform Full integration with the Placed career platform (https://placed.exidian.tech). All tools call the Placed API directly — no MCP server required. ## API Key Load the key from `~/.config/placed/credentials`, falling back to the environment: ```bash if [ -z "$PLACED_API_KEY" ] && [ -f "$HOME/.config/placed/credentials" ]; then source "$HOME/.config/placed/credentials" fi ``` If `PLACED_API_KEY` is still not set, ask the user: > "Please provide your Placed API key (get it at https://placed.exidian.tech/settings/api)" Then save it for future sessions: ```bash mkdir -p "$HOME/.config/placed" echo "export PLACED_API_KEY=<key_provided_by_user>" > "$HOME/.config/placed/credentials" export PLACED_API_KEY=<key_provided_by_user> ``` ## How to Call the API Every Placed action is a POST to the same endpoint: ```bash curl -s -X POST https://placed.exidian.tech/api/mcp \ -H "Authorization: Bearer $PLACED_API_KEY" \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"<tool_name>","arguments":{<args>}}}' ``` Parse the result: ```bash # The response is: {"result":{"content":[{"type":"text","text":"<json_string>"}]}} # Extract the text field and parse it ``` ## Available Skills - `placed-resume-builder` — Resume management + 37 templates - `placed-interview-coach` — Mock interviews + STAR coaching - `placed-career-tools` — Job tracker, cover letters, salary tools, company research - `placed-resume-optimizer` — AI resume optimization for specific jobs - `placed-job-tracker` — Application pipeline tracking ## What You Can Do - Build and manage resumes with professional templates - Track job applications with pipeline analytics - Practice mock interviews (technical, system design, behavioral) - Optimize resumes for specific job descriptions - Check ATS compatibility scores - Generate tailored cover letters - Get LinkedIn headline + About section - Research companies and salary ranges - Save STAR stories for behavioral interviews ## Sign Up Create an account at https://placed.exidian.tech, then get your API key from Settings → API Keys.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: johnnywang2001/uuid-toolkit (version 1.0.0)

--- name: uuid-toolkit description: Generate, parse, validate, and convert UUIDs (v1/v3/v4/v5), ULIDs, and NanoIDs. Use when creating unique identifiers, parsing existing UUIDs to extract version/timestamp/node info, validating identifier formats, converting between UUID representations (hex, base64, URN, integer), or generating bulk IDs. No external dependencies. --- # UUID Toolkit Generate, parse, validate, and convert UUIDs, ULIDs, and NanoIDs. Zero dependencies (Python 3.9+). ## Quick Start ```bash # Generate a UUIDv4 python3 scripts/uuid_toolkit.py generate uuid4 # Generate 10 ULIDs python3 scripts/uuid_toolkit.py generate ulid --count 10 # Parse a UUID python3 scripts/uuid_toolkit.py parse 550e8400-e29b-41d4-a716-446655440000 ``` ## Commands ### generate Create identifiers of any type: ```bash python3 scripts/uuid_toolkit.py generate uuid4 # Random UUID python3 scripts/uuid_toolkit.py generate uuid1 # Time-based UUID python3 scripts/uuid_toolkit.py generate uuid5 --name example.com # Deterministic python3 scripts/uuid_toolkit.py generate ulid # Sortable ULID python3 scripts/uuid_toolkit.py generate nanoid --size 16 # Short NanoID python3 scripts/uuid_toolkit.py generate uuid4 --count 100 --upper # Bulk, uppercase python3 scripts/uuid_toolkit.py generate nil # Nil UUID ``` Types: `uuid4`, `uuid1`, `uuid3`, `uuid5`, `ulid`, `nanoid`, `nil`. ### parse Extract detailed info from an identifier: ```bash python3 scripts/uuid_toolkit.py parse 550e8400-e29b-41d4-a716-446655440000 python3 scripts/uuid_toolkit.py parse 01ARYZ6S41T1ZTXYZ1234ABCDE # ULID ``` Shows version, variant, timestamp (v1/ULID), node/MAC (v1), hex, integer. ### validate Check if identifiers are valid: ```bash python3 scripts/uuid_toolkit.py validate 550e8400-e29b-41d4-a716-446655440000 not-a-uuid ``` ### convert Convert UUID between representations: ```bash python3 scripts/uuid_toolkit.py convert 550e8400-e29b-41d4-a716-446655440000 ``` Outputs: standard, uppercase, no-dashes, URN, integer, base64, bytes-LE, braces.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)