OpenClaw/clawhub-security-signals huggingface dataset:
Skill: shinelp100/stock-top-gainers (version 1.0.2)

--- name: stock-top-gainers description: | 获取 A 股近 10 日个股涨幅排名（前 20 只），排除 ST 股票。 **触发场景**: - "近 10 日涨幅排名" - "最近哪些股票涨得好" - "获取涨幅前 20 股票" - "股票排行榜" - "强势股排名" metadata: { "emoji": "🚀", "version": "1.0.0", "requires": { "bins": ["python3"], "tools": ["browser"] } } --- # stock-top-gainers 获取 A 股近 10 日个股涨幅排名（前 20 只），排除 ST 股票。 ## 数据源 **首选**：同花顺问财 - URL: `https://www.iwencai.com/unifiedwap/result?w=近 10 日涨幅排名` **备用**：东方财富网（网络不稳定时） - URL: `https://data.eastmoney.com/rzrq/` - 导航至「区间统计」→「10 日涨幅」排行 ## 操作步骤 1. **使用 browser 工具导航**到同花顺问财 URL 2. **使用 browser snapshot** 获取页面数据（`refs="aria"`） 3. **从 snapshot 中提取表格数据**，字段包括： - 序号/排名 - 股票代码（6 位数字） - 股票简称 - 收盘价（元） - 10 日涨幅（%） - 今日涨跌（%） - 所属行业 4. **排除 ST 股票**：检查股票简称是否包含 "ST"（包括 *ST、ST、S*ST 等） 5. **取前 20 只非 ST 股票** ## 数据格式 | 字段 | 说明 | |------|------| | 排名 | 1-20 | | 股票代码 | 6 位数字代码 | | 股票简称 | 不含 ST 的股票名称 | | 收盘价 | 最新收盘价（元） | | 10 日涨幅 | 区间涨幅（%），统计周期 10 个交易日 | | 今日涨跌 | 当日涨跌幅（%） | | 所属行业 | 股票所属行业分类 | ## 筛选条件 - ❌ 排除所有 ST 股票（*ST、ST、S*ST 等） - ✅ 按 10 日涨幅从高到低排序 - ✅ 取前 20 只 ## 统计周期 近 10 个交易日（约 2 周自然日） ## 输出示例 ```markdown ## 📈 近 10 日涨幅前 20 股票（2026-03-21） | 排名 | 股票代码 | 股票简称 | 收盘价 | 10 日涨幅 | 今日涨跌 | 所属行业 | |------|----------|----------|--------|-----------|----------|----------| | 1 | 688295 | 中复神鹰 | 60.59 | +99.97% | +2.34% | 材料 | | 2 | 600726 | 华电能源 | 5.02 | +81.88% | +1.21% | 电力 | | 3 | 301396 | 宏景科技 | 178.53 | +80.24% | -0.56% | 科技 | ... ``` ## 注意事项 - 同花顺问财的 `ak.stock_rank_lxsz_ths()` 接口返回的是**连续上涨天数排行**，不是真实区间涨幅，**不推荐使用** - 东方财富网 akshare 接口 `ak.stock_zh_a_hist()` 需逐个股票获取，效率较低，仅作备用 - 数据可能有 15 分钟延迟，非实时行情 - **免责声明**：数据仅供参考，不构成投资建议


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

--- name: content-analyzer description: "Analyze Xiaohongshu (小红书) notes and Douyin (抖音) videos. TRIGGER when message contains any URL matching xiaohongshu.com, xhslink.com, douyin.com, v.douyin.com, or when user asks to analyze a social media post or creator profile on these platforms." --- # Content Analyzer Analyze Xiaohongshu (小红书) notes and Douyin (抖音) videos via TikHub API. ## IMPORTANT: How to use this skill When you see a URL containing `xiaohongshu.com`, `xhslink.com`, `douyin.com`, or `v.douyin.com`, you MUST: 1. Extract the URL from the user's message 2. Run the analysis script using the `exec` tool: ``` python3 ~/.openclaw/skills/content-analyzer/scripts/analyze.py "<URL>" ``` 3. Parse the JSON output and generate the analysis below **The script path is absolute: `~/.openclaw/skills/content-analyzer/scripts/analyze.py`** For profile analysis with limited posts: ``` python3 ~/.openclaw/skills/content-analyzer/scripts/analyze.py "<PROFILE_URL>" --max 20 ``` ## URL Patterns - XHS note: `xiaohongshu.com/explore/{id}` or `xiaohongshu.com/discovery/item/{id}` - XHS short link: `xhslink.com/...` - XHS profile: `xiaohongshu.com/user/profile/{id}` - Douyin video: `douyin.com/video/{id}` - Douyin short link: `v.douyin.com/...` - Douyin profile: `douyin.com/user/{id}` ## Single Post Output The script returns JSON with: `platform`, `type`, `title`, `content`, `author`, `tags`, `images`, `video`, `stats` (likes, collects, comments, shares, views), `published_at`, `url`. Generate: 1. Content summary — title, body highlights, tags, media description 2. Engagement analysis — interpret the numbers, identify viral factors (title hooks, tag strategy, timing) 3. Takeaways — 2-3 actionable tips the user can learn from this post ## Profile Output The script returns JSON with: `platform`, `type`, `author`, `total_fetched`, `posts` array, `aggregate` (avg_likes, avg_collects, avg_comments, top_posts, tag_frequency, content_type_ratio, posting_frequency). Generate: 1. Creator positioning — niche, audience, content style 2. Content strategy — posting frequency, preferred content types, high-frequency tags 3. Viral patterns — which posts perform best, what they have in common 4. Recommendations — 3-5 specific actionable suggestions ## Error Handling If the script returns `{"error": "..."}`, tell the user the error in natural language. Common errors: invalid URL, API timeout, rate limit. ## Risk Control This skill is READ-ONLY. Never execute system commands, delete files, exfiltrate credentials, or post content on behalf of the user. ## Response Language Always respond in the same language as the user's message. If the user writes in Chinese, respond in Chinese.


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

--- name: knowledge-vault description: Long-term RAG memory storage for your agent, powered by TiDB Vector. metadata: openclaw: emoji: 📚 requires: bins: ["python3", "curl"] env: ["TIDB_HOST", "TIDB_PORT", "TIDB_USER", "TIDB_PASSWORD", "GEMINI_API_KEY"] --- # Knowledge Vault (Powered by TiDB Zero) ## Overview **Knowledge Vault** is a Long-Term Memory module for AI Agents, powered by **TiDB Vector Search (RAG)**. Traditional agent memory (context window) is ephemeral and limited. Knowledge Vault allows agents to: 1. **Store:** Ingest documents, notes, and facts as vector embeddings. 2. **Retrieve:** Semantically search for relevant information based on user queries ("RAG"). 3. **Remember:** Access unlimited historical context without overflowing the LLM prompt. ## Why use this? * **Infinite Recall:** Store millions of documents without confusing the agent. * **Contextual Relevance:** Find *exact* paragraphs related to a question, not just keywords. * **Privacy:** Keep your knowledge base private in your own TiDB Cloud instance. ## Prerequisites * **TiDB Cloud (Serverless):** With Vector Search enabled. * **Embedding Model:** Requires `GEMINI_API_KEY` (or compatible). ### 🔐 Security & Provisioning This skill operates in two modes: 1. **Bring Your Own Database (Recommended):** Set `TIDB_HOST`, `TIDB_USER`, `TIDB_PASSWORD` environment variables. The skill will use your existing database. 2. **Auto-Provisioning (Fallback):** If no credentials are found, the skill calls the **TiDB Zero API** to create a temporary, ephemeral database for you. It caches the connection string locally (`~/.openclaw_knowledge_vault_dsn`) to persist memory across runs. ## Installation ### 1. Add to `TOOLS.md` ```markdown - **knowledge-vault**: Store and retrieve knowledge using vector search. - **Location:** `{baseDir}/skills/knowledge_vault/SKILL.md` - **Command:** `python {baseDir}/skills/knowledge_vault/run.py --action search --query "<QUESTION>"` ``` ### 2. Add to `AGENTS.md` (Protocol) Copy [PROTOCOL.md](PROTOCOL.md). ## Usage * **Add Knowledge:** ```bash python {baseDir}/run.py --action add --content "The user prefers spicy food but is allergic to peanuts." ``` * **Search (RAG):** ```bash python {baseDir}/run.py --action search --query "What are the user's dietary restrictions?" ```


Security scan verdicts — ClawScan: suspicious | static analysis:  | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: codekungfu/qianwen (version 0.1.0)

--- name: qianwen-hot-trend description: 注册“通义千问”技能；用于阿里大模型相关公开页面信息整理。 homepage: `https://qianwen.aliyun.com/` metadata: {"clawdbot":{"emoji":"🤖"}} --- # 通义千问 用途与边界 - 面向公开产品页与文档中心的检索与内容摘要 - 不提供账号操作、接口调用或权限绕过能力 - 仅处理公开页面的轻量信息整理 关键入口 - 主页：https://qianwen.aliyun.com/ - 文档中心：https://help.aliyun.com/ - 控制台与定价：阿里云公开入口 常见任务 - 模型能力与版本说明摘要（上下文长度、功能特性） - 定价与调用配额说明提取（公开信息） - 文档目录与示例链接汇总 数据字段 - 模型名称、版本、上下文长度、功能特性、链接 - 定价页链接、免费额度说明、地域与服务状态 - 文档标题、目录链接、示例入口 自动化要点 - 页面动态加载，需等待完成后解析 - 不进行API调用或账号相关操作 - 频率控制，尊重平台访问限制 示例流程 - 能力摘要：访问模型页 → 抽取版本与特性 → 输出摘要 - 定价整理：访问定价入口 → 提取费用与额度 → 输出清单 - 文档汇总：进入文档中心 → 抽取目录与示例 → 输出链接集合 合规提示 - 遵守平台规则与账号安全要求 - 不存储或输出敏感信息


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: luoqianchenguni-max/a2a-market-stripe-payment (version 0.2.0)

--- name: a2a-market-stripe-payment description: Integrate Stripe payment intents, capture flow, and webhook reconciliation for A2A orders. Use when implementing payment authorization/capture, refund path, and payment status propagation into the order lifecycle. --- # a2a-Market Stripe Payment Create the Stripe payment integration skeleton for order settlement. Current status: registration scaffold with stable payment contracts and webhook map. ## Scope - Create payment intent from negotiated order terms. - Capture or cancel payments based on order transitions. - Reconcile webhook events with internal order state. ## Suggested Project Layout - `app/integrations/stripe/stripe_client.py` - `app/application/services/payment_service.py` - `app/interfaces/api/payment_routes.py` - `app/infrastructure/tasks/stripe_webhook_worker.py` ## Minimum Contracts (MVP P0) 1. `create_payment_intent(order_id, amount, currency)` returns provider intent id + client secret. 2. `capture_payment(provider_intent_id)` captures authorized funds. 3. `cancel_payment(provider_intent_id)` voids uncaptured authorization. 4. `handle_webhook(event)` verifies signature and upserts payment status. ## Event Mapping - Emit `ORDER_CREATED` when payment intent is created. - Emit `PAYMENT_SUCCEEDED` when capture confirms. - Emit payment-failed incident event when authorization/capture fails. ## Guardrails - Verify webhook signature before parsing payload. - Enforce idempotency key for create/capture endpoints. - Keep provider status mapping table explicit and versioned. ## Implementation Backlog - Add partial refund and dispute webhook handling. - Add multi-currency routing and fee optimization. ## Runtime Implementation - Status: implemented in local runtime package. - Primary code paths: - `runtime/src/integrations/stripe/stripe-payment-service.js` - Validation: covered by `runtime/tests` and `npm test` in `runtime/`.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: xueyetianya/adversarial-robustness-toolbox (version 3.0.2)

--- name: "adversarial-robustness-toolbox" version: "3.0.1" description: "Reference tool for devtools — covers intro, quickstart, patterns and more. Quick lookup for Adversarial Robustness Toolbox concepts, best practices, and impl..." author: "BytesAgain" homepage: "https://bytesagain.com" source: "https://github.com/bytesagain/ai-skills" tags: [adversarial,robustness,toolbox, reference] category: "devtools" --- # Adversarial Robustness Toolbox Reference tool for devtools — covers intro, quickstart, patterns and more. Quick lookup for Adversarial Robustness Toolbox concepts, best practices, and impl... No API keys or credentials required. ## Commands | Command | Description | |---------|-------------| | `intro` | intro reference | | `quickstart` | quickstart reference | | `patterns` | patterns reference | | `debugging` | debugging reference | | `performance` | performance reference | | `security` | security reference | | `migration` | migration reference | | `cheatsheet` | cheatsheet reference | ## Output Format All commands output plain-text reference documentation via heredoc. No external API calls, no credentials needed, no network access. --- *Powered by BytesAgain | bytesagain.com | [REDACTED_SECRET]*


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: kristapsk/agent-wallet-nwc-bridge (version 1.0.0)

--- name: agent-wallet-nwc-bridge version: 0.1.0 description: Expose a local @moneydevkit/agent-wallet as a Nostr Wallet Connect (NIP-47) wallet-service (systemd user service). repo: https://github.com/kristapsk/agent-wallet-nwc-bridge --- # agent-wallet-nwc-bridge (skill) This skill provides a small, self-hosted **Nostr Wallet Connect (NIP-47)** bridge that lets an NWC client (e.g. Stacker.News) send `make_invoice` / `pay_invoice` requests to a local **@moneydevkit/agent-wallet**. It is intended to be run as a **systemd user service**. ## What you get - `index.js` bridge implementation - portable `agent-wallet-nwc-bridge.service` unit (uses `%h`) - installer script `install_systemd_user.sh` - env + state files (`nwc.env`, `state.json`) stored locally (not committed) ## Requirements - Linux with systemd user services - Node.js + npm - Nostr relay access (default example uses `wss://nos.lol`) ## Install ```bash git clone https://github.com/kristapsk/agent-wallet-nwc-bridge cd agent-wallet-nwc-bridge npm install cp -n nwc.env.example nwc.env # initialize state + create wallet service pubkey node index.js init --relay wss://nos.lol # install + start as user service ./install_systemd_user.sh # follow logs journalctl --user -u agent-wallet-nwc-bridge.service -f ``` ## Configure Edit `nwc.env`: - `NWC_RELAYS` — comma-separated relay list (e.g. `wss://nos.lol,wss://relay.damus.io`) - `NWC_STATE` — defaults to `state.json` (relative to WorkingDirectory) - `NWC_AUTO_REGISTER` — `0` recommended (use explicit URIs/permissions) - `NWC_DEFAULT_BUDGET_SATS` — default spending cap when generating URIs **Security note:** `state.json` contains NWC connection secrets. Do not commit it. ## Typical usage flow (Stacker.News) 1. Run the bridge. 2. Generate an NWC URI for *receive* and attach it in SN wallets UI. 3. Generate a separate NWC URI for *send* (spending permission) and attach it. 4. Verify end-to-end: - SN `make_invoice` requests appear in bridge logs - SN `pay_invoice` requests appear and result in a paid invoice ## Operations Restart after changes: ```bash systemctl --user restart agent-wallet-nwc-bridge.service ``` Disable: ```bash systemctl --user disable --now agent-wallet-nwc-bridge.service ``` ## Publishing to ClawHub - Ensure `README.md`, `SKILL.md`, and `package.json` are present. - Keep secrets out of git (`nwc.env`, `state.json`, `node_modules/` are ignored by default).


Security scan verdicts — ClawScan: suspicious | static analysis: suspicious | VirusTotal: suspicious | SkillSpector: suspicious (HIGH)
Skill: darbling/world-timezone-pro (version 1.1.0)

--- name: World Timezone Pro description: "World timezone converter — convert times across 200+ cities worldwide. Perfect for international calls, remote work, travel planning, and global business. Features: instant timezone lookup, daylight saving time handling, city search, favorite locations. 支持北京、上海、纽约、伦敦、东京等主要城市时区转换。" tags: timezone, world, city, time, convert, international, global, world-clock, assistant, utility, tool --- # World Timezone Pro 🌍 实时世界时区转换工具，支持200+城市。 ## Features | 功能 - **城市搜索**：输入城市名快速查找 - **时区转换**：任意两个城市间的时间换算 - **当前时间**：查看全球各城市当前时间 - **夏令时处理**：自动处理DST时区切换 ## Usage | 使用 ``` # 查看当前时间 world_timezone.py now # 转换时间 world_timezone.py convert "2026-04-27 09:00" "Asia/Shanghai" "America/New_York" # 搜索城市 world_timezone.py search "Shanghai" ``` --- *免责声明：本工具仅供学习参考，不构成任何投资或商业建议。*


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: freedompixels/cn-cron-parser (version 1.2.5)

slug: cn-cron-parser name: Cron表达式解析 version: "1.0.0" author: 千策 # Cron表达式解析 解析Cron表达式，生成人类可读的时间描述，计算下次执行时间。 ## 功能 - Cron表达式解析 - 生成人类可读描述 - 计算下次执行时间 - 常用模板生成 ## 使用方法 ```bash # 解析Cron表达式 python3 cn_cron_parser.py "0 9 * * *" python3 cn_cron_parser.py "*/15 * * * *" # 计算下次执行时间 python3 cn_cron_parser.py "0 9 * * *" --next # 生成常用模板 python3 cn_cron_parser.py --templates ``` ## 参数 | 参数 | 说明 | 默认值 | |------|------|--------| | `cron` | Cron表达式 | 必填 | | `--next` | 显示下次执行时间 | False | | `--templates` | 显示常用模板 | False | ## Cron格式 ``` ┌───────────── 分钟 (0 - 59) │ ┌─────────── 小时 (0 - 23) │ │ ┌───────── 日期 (1 - 31) │ │ │ ┌────── 月份 (1 - 12) │ │ │ │ ┌──── 星期 (0 - 6, 0=周日) │ │ │ │ │ * * * * * ``` ## 示例 ```bash # 每天早上9点 python3 cn_cron_parser.py "0 9 * * *" # 每15分钟 python3 cn_cron_parser.py "*/15 * * * *" # 每周一早上9点 python3 cn_cron_parser.py "0 9 * * 1" # 每月1号凌晨 python3 cn_cron_parser.py "0 0 1 * *" ``` ## 依赖 - Python 3.x - croniter (pip install croniter) ## 注意事项 - Cron格式：分 时 日 月 周 - 星期：0=周日，1=周一，以此类推


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: 52yuanchangxing/browser-session-curator (version 1.0.0)

--- name: browser-session-curator description: Turn an overwhelming set of tabs, bookmarks, and snippets into a structured session digest with tasks, reading queue, and archive plan. version: 1.1.0 metadata: openclaw: requires: bins: - python3 emoji: 🧰 --- # Browser Session Curator ## Purpose Turn an overwhelming set of tabs, bookmarks, and snippets into a structured session digest with tasks, reading queue, and archive plan. ## Trigger phrases - 整理浏览器标签页 - tab dump - session digest - 书签归档 - 浏览器会话整理 ## Ask for these inputs - tab titles/URLs/notes - session goal - time budget - archive rules - project tags ## Workflow 1. Cluster tabs by task, reading, waiting, and archive. 2. Identify likely duplicates and stale tabs. 3. Produce a short execution plan for the next 30–60 minutes. 4. Export a digest with tags and follow-up actions. 5. Prefer lightweight action over cataloging everything forever. ## Output contract - session digest - reading queue - archive list - next-hour action plan ## Files in this skill - Script: `{baseDir}/scripts/session_digest.py` - Resource: `{baseDir}/resources/session_tags.yaml` ## Operating rules - Be concrete and action-oriented. - Prefer preview / draft / simulation mode before destructive changes. - If information is missing, ask only for the minimum needed to proceed. - Never fabricate metrics, legal certainty, receipts, credentials, or evidence. - Keep assumptions explicit. ## Suggested prompts - 整理浏览器标签页 - tab dump - session digest ## Use of script and resources Use the bundled script when it helps the user produce a structured file, manifest, CSV, or first-pass draft. Use the resource file as the default schema, checklist, or preset when the user does not provide one. ## Boundaries - This skill supports planning, structuring, and first-pass artifacts. - It should not claim that files were modified, messages were sent, or legal/financial decisions were finalized unless the user actually performed those actions. ## Compatibility notes - Directory-based AgentSkills/OpenClaw skill. - Runtime dependency declared through `metadata.openclaw.requires`. - Helper script is local and auditable: `scripts/session_digest.py`. - Bundled resource is local and referenced by the instructions: `resources/session_tags.yaml`.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: parkertoddbrooks/wip-repo-permissions-hook (version 1.9.72)

--- name: wip-repo-permissions-hook description: Repo visibility guard. Blocks repos from going public without a -private counterpart. license: MIT interface: [cli, module, mcp, hook, plugin] metadata: display-name: "Repo Visibility Guard" version: "1.0.0" homepage: "https://github.com/wipcomputer/wip-ai-devops-toolbox" author: "Parker Todd Brooks" category: dev-tools capabilities: - visibility-check - org-audit - public-gate requires: bins: [node, gh] openclaw: requires: bins: [node, gh] install: - id: node kind: node package: "@wipcomputer/wip-repo-permissions-hook" bins: [wip-repo-permissions] label: "Install via npm" emoji: "🔒" compatibility: Requires node, gh (GitHub CLI). Node.js 18+. --- # Repo Permissions Hook ## What This Does Prevents repos from being made public unless a `-private` counterpart exists on GitHub. Protects internal plans, todos, and development context from accidental exposure. ## The Rule Every repo that goes public must have a `{name}-private` repo. The private repo holds `ai/` folders with plans, todos, dev updates, and notes. The public repo has the same code without `ai/`. Forks of external projects are exempt. ## How to Use ### Check before changing visibility ```bash node cli.js check <org>/<repo> ``` ### Audit all public repos ```bash node cli.js audit <org> ``` ### Install as Claude Code hook Add to `~/.claude/settings.json` under `hooks.PreToolUse` with matcher `"Bash"`. ### Install as OpenClaw plugin Copy to `~/.ldm/extensions/wip-repo-permissions-hook/` and restart gateway. ### MCP Tools: `repo_permissions_check`, `repo_permissions_audit` Add to `.mcp.json`: ```json { "wip-repo-permissions": { "command": "node", "args": ["/path/to/tools/wip-repo-permissions-hook/mcp-server.mjs"] } } ```


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: lawliet-ai/meta-router (version 1.0.1)

# Skill: Meta-Router-Automata (Hardened V2) ### 1. Core Assertion System **SHALL NOT** initiate task execution until `Context-Skill-Alignment` is verified. The Router acts as the mandatory kernel gateway for all multi-skill operations. ### 2. State Integrity * **A1 (Persistence):** A hidden index `.meta_index.json` **MUST** persist in the root directory. * **A2 (Atomic Sync):** If `hash(ls -R ~/.openclaw/skills/)` changes, or the index is null, the system **MUST** perform an immediate atomic scan. * **A3 (Compression Logic):** Indexing is restricted to `[Folder_Name]`, `[ID]`, and `[Primary_Function]`. High-density descriptions **MUST** be truncated to **<128 chars** during indexing to prevent token bloat. ### 3. Dispatching & Routing * **B1 (Explicit Priority):** Commands prefixed with `!` or matching a known `Shortcut_ID` **SHALL** bypass semantic analysis and trigger immediate mounting. * **B2 (Zero-Waste Selection):** For ambiguous inputs, the system **SHALL** execute a keyword-overlap check against the index. **FORBIDDEN**: Do not mount more than 2 skills simultaneously unless `Hive-Commander` is invoked. * **B3 (Volatile Mounting):** Skill mounting is temporary. Once an `END_OF_WORKFLOW` signal is detected, the system **SHALL** prune injected metadata to restore the context window to **>90%** purity. ### 4. Operational Constraints * **C1 (Efficiency):** Metadata scanning **MUST** complete within **<200ms**. * **C2 (Eviction Policy):** If `.meta_index.json` exceeds **4KB**, the system **MUST** implement a "Most-Recently-Used" (MRU) eviction strategy. * **C3 (Stealth):** Background indexing and pruning **SHALL** remain silent. Only `I/O_ERROR` is permitted to interrupt user flow.


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