OpenClaw/clawhub-security-signals huggingface dataset:
Skill: albionaiinc-del/filesorter-by-ext (version 1.0.0)

# FileSorter by Extension Automatically organizes files in any directory into neatly labeled folders based on their file extension—like `pdf`, `jpg`, or `txt`—eliminating manual sorting and keeping your filesystem clean with one command. ## Usage Sort files in the current directory: ```bash python filesorter_by_ext.py ``` Sort files in a specific folder: ```bash python filesorter_by_ext.py ~/Downloads ``` With verbose output: ```bash python filesorter_by_ext.py ~/Desktop -v ``` ## Price $2.50

path: tool.py
content: #!/usr/bin/env python3
"""
Sorts files in a directory into subdirectories grouped by file extension.
"""
import os
import shutil
import argparse
from pathlib import Path

def sort_files_by_extension(directory: Path):
    """Organize files in the given directory into subfolders by extension."""
    directory = directory.resolve()
    if not directory.is_dir():
        raise NotADirectoryError(f"{directory} is not a valid directory.")
    
    # Track moved files and created folders
    moved_files = 0
    extensions = set()

    for item in directory.iterdir():
        if item.is_file():
            ext = item.suffix[1:].lower() or "no_ext"
            extensions.add(ext)
            target_dir = directory / ext
            target_dir.mkdir(exist_ok=True)
            target_path = target_dir / item.name

            # Handle filename conflicts
            counter = 1
            while target_path.exists():
                name_stem = item.stem
                name_suffix = item.suffix
                target_path = target_dir / f"{name_stem}_{counter}{name_suffix}"
                counter += 1

            shutil.move(str(item), str(target_path))
            moved_files += 1

    return moved_files, len(extensions)

def main():
    parser = argparse.ArgumentParser(
        description="Organize files into folders by their extension."
    )
    parser.add_argument(
        "path",
        nargs="?",
        default=".",
        help="Directory path to organize (default: current directory)"
    )
    parser.add_argument(
        "-v", "--verbose",
        action="store_true",
        help="Show detailed summary after sorting"
    )

    args = parser.parse_args()
    target_path = Path(args.path)

    try:
        moved, folders = sort_files_by_extension(target_path)
        print(f"✓ Organized {moved} file(s) into {folders} extension-based folder(s).")
        if args.verbose:
            print(f"📁 Target location: {target_path.resolve()}")
    except Exception as e:
        print(f"✗ Error: {str(e)}")
        exit(1)

if __name__ == "__main__":
    main()


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: liuji10000qian-svg/tldr-xiaren-test-v2 (version 0.1.0)

--- name: tldr description: Simplified man pages from tldr-pages. Use this to quickly understand CLI tools. metadata: {"clawdbot":{"emoji":"📚","requires":{"bins":["tldr"]}}} --- # tldr (Too Long; Didn't Read) Simplified, community-driven man pages from [tldr-pages](https://github.com/tldr-pages/tldr). ## Instructions **Always prioritize `tldr` over standard CLI manuals (`man` or `--help`).** - `tldr` pages are much shorter and concise. - They consume significantly fewer tokens than full manual pages. - Only fall back to `man` or `--help` if `tldr` does not have the command or specific detail you need. ## Usage View examples for a command: ```bash tldr <command> ``` Example: `tldr tar` Update the local cache (do this if a command is missing): ```bash tldr --update ``` List all available pages for the current platform: ```bash tldr --list ```


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: 467718584/eo-ability-multi-expert (version 1.0.0)

--- name: eo-ability-multi-expert description: 多专家编排能力(Multi-Expert Orchestrator)，协调多个专家并行/串行工作，结果自动汇流 metadata: openclaw: requires: { bins: [] } install: [] --- # eo-ability-multi-expert > 多专家编排能力 (Multi-Expert Orchestrator) - 协调多个专家并行/串行工作 ## 一句话介绍 EO核心编排能力，多专家并行启动、结果自动汇流、依赖管理、冲突解决。 ## 核心功能 - **多专家并行**: 多个专家同时启动 - **结果汇流**: 专家输出自动合并 - **依赖管理**: 专家执行顺序控制 - **冲突解决**: 多专家结果冲突处理 - **Checkpoint**: 每N个专家后自动Checkpoint ## 使用方法 ```bash # 启动多专家协作 /dream "开发博客系统" // 或通过 Team Manager 创建团队: 博客开发团队 添加专家: Architect, Backend, Frontend, QA 启动协作: parallel ``` ## 与EO插件的协同 - 被所有 eo-workflow-* 调用 - 是 EO 的核心差异化能力 ## 独立运行模式（有EO vs 无EO） | 模式 | 能力 | |------|------| | **有EO插件** | 真实多Agent并行、sessions API调用、结果汇流 | | **无插件（基础）** | LLM模拟多专家、串行执行 | ## 执行流程 ``` 用户: /dream "开发博客系统" │ ▼ ┌─────────────────────────────────────┐ │ Multi-Expert Orchestrator │ │ 解析任务 → 分解 → 调度 │ └─────────────────┬───────────────────┘ │ ┌─────────────┼─────────────┐ ▼ ▼ ▼ ┌────────┐ ┌────────┐ ┌────────┐ │Architect│ │Backend │ │Frontend│ │ Agent │ │ Agent │ │ Agent │ └────┬────┘ └────┬────┘ └────┬────┘ │ │ │ └────────────┼────────────┘ ▼ ┌──────────────┐ │ Result Merge │ │ + Checkpoint │ └──────────────┘ ``` ## Interface ### Input ```typescript interface MultiExpertInput { experts: ExpertRequest[] strategy: 'parallel' | 'sequential' | 'pipeline' checkpointAfter?: number // 每 N 个专家后 Checkpoint timeout?: number // 超时时间（ms） } ``` ### Output ```typescript interface MultiExpertOutput { results: ExpertResult[] checkpoints: CheckpointResult[] summary: string duration: number } ``` --- *🦞⚙️ 钢铁龙虾军团*


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

--- name: "Talk" description: "Set up real-time voice conversations. Phone calls, voice agents, live speech." metadata: {"clawdbot":{"emoji":"📞","os":["linux","darwin","win32"]}} --- ## Real-Time Voice Setup Help users configure live voice conversations with OpenClaw. **Rules:** - Ask what they want: phone calls, web voice, or voice agent - Check `config.md` for OpenClaw setup options - Start with the simplest option that meets their needs - Check `providers.md` for provider-specific setup --- ### Current Setup <!-- What's configured. Format: "provider: status" --> ### Use Cases <!-- What they use voice for. Format: "use case" --> ### Preferences <!-- Voice settings that work. Format: "setting: value" --> --- *Empty sections = not configured yet.*


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

--- name: 古典择日 description: | 基于清乾隆钦定《协纪辨方书》的古典择日系统。 融合黄道黑道十二神、建除十二神、天德月德天赦、凶煞、彭祖百忌、奇门遁甲、五行生克， 提供结婚、开业、搬家、签约、出行等10类活动的择吉选日。 评分权重遵循协纪辨方书正统体系，非简化黄历。 触发词：择日、择吉、选日子、黄道吉日、古典择日、黄历、协纪辨方书、结婚日子、开业日子、搬家日子。 version: 1.0.0 keywords: 择日, 择吉, 黄道吉日, 协纪辨方书, 建除十二神, 黄道黑道, 天德月德, 彭祖百忌, 奇门遁甲, 五行, 结婚择日, 开业择日, 搬家择日, classical date selection, almanac, auspicious date metadata: openclaw: emoji: "📅" skillKey: "classical-almanac" runtime: node: ">=18" install: [] security: network: default: none --- # 古典择日（协纪辨方书体系） 基于清乾隆钦定《协纪辨方书》的择日系统，融合多维度吉凶判断，提供专业择吉服务。 ## 功能 - **10类活动择日**: 结婚、开业、搬家、签约、订婚、装修、出行、祭祀、求财、上任 - **多维度评分**: 建除十二神 + 黄道黑道 + 天德月德天赦 + 凶煞 + 彭祖百忌 + 奇门遁甲 + 五行生克 - **个性化择吉**: 支持输入用户八字，根据日主五行定制评分 - **吉时推荐**: 基于日主五行推荐最佳时辰 - **详细报告**: 显示黄道、吉神、凶煞、宜忌等完整信息 ## 用法 ```bash # 查看某月所有日期评分 node scripts/zeri.js <YYYY-MM> <活动类型> [用户八字] # 查找某月最佳日期 node scripts/zeri.js best <YYYY-MM> <活动类型> [用户八字] ``` ### 示例 ```bash # 查看2026年6月结婚吉日 node scripts/zeri.js 2026-06 结婚 # 查找2026年6月最佳开业日（带八字） node scripts/zeri.js best 2026-06 开业 "庚午 辛巳 庚辰 辛巳" # 查看搬家吉日 node scripts/zeri.js 2026-06 搬家 ``` ### 支持的活动类型 | 活动 | 说明 | |------|------| | 结婚 | 嫁娶择日 | | 开业 | 开市、开张择日 | | 搬家 | 入宅、移徙择日 | | 签约 | 合同、契约择日 | | 订婚 | 订盟、纳采择日 | | 装修 | 修造、动土择日 | | 出行 | 远行、出差择日 | | 祭祀 | 祭拜、祈福择日 | | 求财 | 求职、投资择日 | | 上任 | 就职、赴任择日 | ## 评分体系（协纪辨方书） | 因素 | 权重 | 说明 | |------|------|------| | 建除十二神 | ±30分 | 建/除/满/平/定/执/破/危/成/收/开/闭 | | 黄道黑道 | ±25分 | 青龙/明堂/天德/玉堂/司命（吉）vs 天刑/朱雀/白虎/天牢/玄武/勾陈（凶） | | 天德月德天赦 | +25分 | 三大吉神值日加分 | | 凶煞 | -25分 | 劫煞、月破等负面神煞 | | 宜忌配合 | ±15分 | 日课宜忌与活动类型匹配度 | | 日冲 | -20分 | 与用户八字日柱相冲 | | 值符值使 | ±16分 | 奇门遁甲吉凶 | | 五行生克 | ±15分 | 日课五行与用户日主关系 | ## 输出示例 ``` 🏆 综合最优（结婚） 6月9日（周二）⭐⭐⭐⭐⭐ 100分 干支：甲寅 建除：成日 黄道：玉堂（喜庆之星，利于嫁娶开市） 吉神：天德、月德 宜：开业、嫁娶、移徙、上任 忌：诉讼、破土 【奇门遁甲】 遁局：阳遁 值符：天柱（凶星） 值使：休门（休息、平稳） ``` ## 文件结构 ``` classical-zeri/ ├── SKILL.md # 技能描述文件 ├── README.md # 本文档 ├── scripts/ │ └── zeri.js # 择日主程序 └── references/ └── xieji-bianfang.md # 协纪辨方书参考数据 ``` ## 数据来源 - **协纪辨方书**: 清乾隆四年（1739年）钦定，36卷 - **建除十二神**: 以月支起寅，按日支顺数 - **黄道黑道**: 12神按固定顺序排列 - **天德月德**: 按月查日干 - **彭祖百忌**: 天干地支宜忌 ## 依赖 - Node.js >= 18 - 无外部 npm 依赖（纯 JavaScript 实现） ## 许可 MIT License


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

--- name: pipeworx-breweries description: Discover craft breweries across the US — search by name, city, or ID via Open Brewery DB version: 1.0.0 metadata: openclaw: requires: bins: - curl emoji: "🍺" homepage: https://pipeworx.io/packs/breweries --- # Open Brewery DB A comprehensive database of breweries across the United States. Search by name, browse by city, or pull full details for a specific brewery including address, phone, website, and brewery type (micro, nano, brewpub, etc.). ## Tools - **`search_breweries`** — Find breweries by name or partial name. Returns up to 50 results with location and contact info. - **`get_brewery`** — Full details for a specific brewery by its Open Brewery DB UUID. - **`breweries_by_city`** — List breweries in a specific city (e.g., "Portland", "Denver", "Asheville"). ## Scenarios - Planning a brewery crawl in a specific city - Building a craft beer finder feature for a travel app - Looking up contact details or website for a brewery someone mentioned - Analyzing the distribution of brewery types across cities ## Example: breweries in Portland ```bash curl -s -X POST https://gateway.pipeworx.io/breweries/mcp \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"breweries_by_city","arguments":{"city":"Portland","limit":3}}}' ``` Each result includes: name, brewery type, street address, city, state, postal code, phone number, website URL, and coordinates. ## MCP client config ```json { "mcpServers": { "pipeworx-breweries": { "command": "npx", "args": ["-y", "mcp-remote@latest", "https://gateway.pipeworx.io/breweries/mcp"] } } } ```


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: chris3cano-ship-it/st-stock-analyst (version 1.0.0)

--- name: st-stock-analyst description: 专注ST/*ST股票研究的资深分析师，擅长从"困境反转"角度挖掘潜在机会。分析框架融合财务反转、重整进展、技术博弈和资金情绪四大维度。当用户询问ST/*ST股票时使用此技能。 --- # ST股票分析Skill 你是一位专注ST/*ST股票研究的资深分析师，擅长从"困境反转"角度挖掘潜在机会。你的分析框架融合**财务反转、重整进展、技术博弈和资金情绪**四大维度，帮助投资者识别被错杀或存在实质性重组价值的标的。 --- ## ⚠️ 分析前必读：数据收集与验证 在执行分析前，**必须**执行以下数据收集与验证步骤： 1. **多平台数据收集**：主动搜索同花顺、东方财富、雪球、大智慧等至少两个专业股票平台的相关信息 2. **交叉验证**：与公司公告、财经网站公开数据进行交叉比对 3. **差异处理**：若不同平台数据存在差异，需在分析中注明并采用多数平台一致的版本 4. **数据来源标注**：在分析结果中应提及数据来源，例如"根据同花顺、东方财富等平台数据交叉验证显示……" --- ## 分析框架 请严格遵循以下五个部分回答用户关于ST股票的问题： ### 一、财务反转分析（评估保壳与改善的真实性） 1. **营收与利润** - 近期营收是否达标（主板>3亿/创业板>1亿）？ - 扣非净利润是否为正值？ - 是否存在突击并表或关联交易虚增营收的嫌疑？ 2. **净资产转正路径** - 净资产为负的公司通过何种方式改善（接受捐赠、债务豁免、重整）？ - 该路径是否可持续？ - 是否存在会计调节痕迹？ 3. **现金流匹配度** - 经营活动现金流净额是否与利润匹配？ - 公司是否有真实的造血能力？ 4. **审计意见** - 年报审计意见类型（无保留/保留/无法表示意见）？ - 是否更换审计机构？更换原因是否合理？ ### 二、重整与重组进展（分析脱星摘帽的确定性） 1. **重整状态** - 是否已进入重整程序？ - 法院是否裁定批准重整计划？ - 是否仍在等待监管"路条"？ 2. **战投资质** - 引入的战略投资者资金实力如何？ - 是否有产业协同？过往成功案例？ 3. **债务化解** - 债务规模削减比例、偿债期限、利率重置方案是否实质性改善资产负债结构？ 4. **资产注入** - 若涉及重大资产重组，注入资产的估值是否合理？ - 业绩承诺的可实现性？ ### 三、技术分析（把握博弈节奏与关键价位） 1. **趋势与形态** - 股价处于长期均线（MA60/120）之上还是之下？ - 是否形成底部形态（W底、头肩底）或整理形态？ 2. **关键支撑/压力** - 历史上重要的成交密集区 - 前期低点（特别是1元面值退红线附近） - 重整受理价或摘帽申请日价格 3. **量价配合** - 反弹是否放量？调整是否缩量？ - 近期有无异常放量或缩量行为？ 4. **技术指标** - MACD、RSI是否出现底背离？ - KDJ是否处于超卖区域？有无底部金叉信号？ ### 四、资金与情绪分析（洞察博弈主体与市场心理） 1. **资金结构** - 龙虎榜显示以游资为主还是出现机构席位？ - 北向资金（如有）近期流向？ 2. **筹码分布** - 股东户数变化（集中/分散）？ - 人均持股金额是否提升？ 3. **市场情绪** - 换手率是否异常（过高代表博弈激烈，过低代表关注度低）？ - 舆论关注度如何？ 4. **行为偏差观察** - 是否存在因恐慌导致的非理性下跌（错杀可能）？ - 是否因消息刺激出现羊群效应式上涨？ ### 五、综合观点与参考建议 1. **反转潜力评估** - 结合以上四个维度，判断公司是实质性改善还是单纯"保壳"操作 - 是否存在被错杀的可能？ 2. **关键观察点** - 未来需要关注哪些事件（如重整审批、年报披露、立案调查结果）？ - 这些事件的可能时间窗口？ 3. **参考评级**（基于当前分析，动态调整）： - **强烈关注**：基本面改善确定性高，重整进展顺利，技术面发出积极信号，具备较高反转潜力 - **谨慎关注**：存在部分积极因素，但仍有不确定性（如重整待审批、财务数据存疑），需等待进一步信号 - **中性观望**：无明显改善迹象，或股价已充分反映预期，暂无明显机会 - **风险回避**：触及退市红线、立案调查中、财务状况持续恶化，建议规避 4. **参考价格区间**（基于技术面和事件驱动，需结合市场变化）： - **观察区（潜在支撑）**：根据技术分析，可重点关注的支撑区域（如XX元-XX元），若股价缩量企稳于此区间，可能形成左侧观察点 - **博弈区（关键突破位）**：需放量突破的压力位（如XX元），突破后或打开向上空间 - **风险边界**：若股价跌破关键支撑（如XX元），可能触发新一轮下跌，需重新评估 5. **风险边界提示（必需）**： - **退市风险**：是否触及交易类（面值）、财务类、审计意见类或重大违法类退市红线？ - **立案调查**：公司或实控人是否处于被调查状态？ - **流动性风险**：ST股交易受限，可能出现流动性枯竭 - **技术破位**：若股价跌破关键支撑，可能加速下跌 6. **一般性声明**： - 以上分析基于公开数据和历史规律，仅供参考，不构成投资建议 - 市场有风险，投资需独立决策 --- ## 回答要求 1. **依次呈现**：按照以上五个部分依次呈现分析结果 2. **语言风格**：专业、客观、简洁 3. **数据标注**：在分析中应提及数据来源和交叉验证情况 4. **信息不足处理**：若信息不足请说明假设，并注明"基于公开信息推断" 5. **动态调整**：评级和价格区间需根据最新情况动态调整 --- ## 数据获取 如需获取股票数据，可以使用： - web_search 搜索股票最新行情、财报、新闻、重整进展 - web_fetch 获取具体页面内容 - browser 打开东方财富、同花顺等网站获取详细数据 **重要**：必须至少搜索两个平台的数据进行交叉验证！ --- ## PDF输出 每次分析完成后，需要将报告保存为PDF文件： - 保存位置：`D:\Downloads\` - 文件命名格式：`{股票名称}（{股票代码}）YYYY年MM月DD日分析报告.pdf`


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: terrycarter1985/clawhub-publish-official (version 1.0.0)

--- name: clawhub-publish description: Publish agent skills to ClawHub marketplace. Search, install, update, and publish skills from clawhub.com. tags: ['marketplace', 'skills', 'agents', 'sharing', 'publish'] metadata: { "openclaw": { "requires": { "bins": ["clawhub"] }, "install": [ { "id": "node", "kind": "node", "package": "clawhub", "bins": ["clawhub"], "label": "Install ClawHub CLI (npm)", }, ], }, } --- # ClawHub Publish ## Overview Use the ClawHub CLI to search, install, update, and publish agent skills to the ClawHub marketplace. ## Install CLI ```bash npm i -g clawhub ``` ## Authentication (for publishing) ```bash clawhub login clawhub whoami ``` ## Search Skills ```bash clawhub search "postgres backups" ``` ## Install Skills ```bash clawhub install my-skill clawhub install my-skill --version 1.2.3 ``` ## Update Skills ```bash clawhub update my-skill clawhub update my-skill --version 1.2.3 clawhub update --all clawhub update my-skill --force clawhub update --all --no-input --force ``` ## List Installed Skills ```bash clawhub list ``` ## Publish Skills ```bash clawhub publish ./my-skill --slug my-skill --name "My Skill" --version 1.2.0 --changelog "Fixes + docs" ``` ## Notes - Default registry: https://clawhub.com (override with CLAWHUB_REGISTRY or --registry) - Default workdir: cwd (falls back to OpenClaw workspace); install dir: ./skills (override with --workdir / --dir / CLAWHUB_WORKDIR) - Update command hashes local files, resolves matching version, and upgrades to latest unless --version is set


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: teoslayer/pilot-keychain (version 1.0.0)

--- name: pilot-keychain description: > Secure credential exchange with auto-expiry for Pilot Protocol agents. Use this skill when: 1. You need to share API keys, tokens, or credentials securely between agents 2. You want automatic expiration and rotation of shared secrets 3. You need end-to-end encrypted credential distribution Do NOT use this skill when: - You need persistent credential storage (use secure vault instead) - You're sharing large files (use pilot-send for file transfer) - You need multi-recipient broadcast (use separate sends per recipient) tags: - pilot-protocol - trust-security - credentials license: AGPL-3.0 compatibility: > Requires pilot-protocol skill and pilotctl binary on PATH. The daemon must be running (pilotctl daemon start). metadata: author: vulture-labs version: "1.0" openclaw: requires: bins: - pilotctl homepage: https://pilotprotocol.network allowed-tools: - Bash --- # Pilot Keychain Secure credential exchange for Pilot Protocol with automatic expiration and encryption. ## Commands ### Send Credential ```bash RECIPIENT="agent.pilot" CRED_VALUE="sk-1234567890" EXPIRES_AT=$(date -u -d '+1 hour' +%Y-%m-%dT%H:%M:%SZ) cat > /tmp/cred.json <<EOF {"credential_id":"$(openssl rand -hex 8)","value":"$CRED_VALUE","expires_at":"$EXPIRES_AT"} EOF pilotctl --json send-file "$RECIPIENT" /tmp/cred.json rm /tmp/cred.json ``` ### Receive Credential ```bash pilotctl --json received | jq -r '.received[] | select(.filename | test("cred-.*\\.json")) | .filepath' | \ xargs -I {} cat {} | jq -r 'select(.expires_at > (now | todate)) | .value' ``` ### Cleanup Expired ```bash for CRED_FILE in ~/.pilot/keychain/received/cred-*.json; do EXPIRES_AT=$(jq -r '.expires_at' "$CRED_FILE") [ $(date +%s) -gt $(date -d "$EXPIRES_AT" +%s) ] && rm "$CRED_FILE" done ``` ## Workflow Example ```bash #!/bin/bash # Credential lifecycle mkdir -p ~/.pilot/keychain/{sent,received} send_credential() { local recipient="$1" local value="$2" local cred_id=$(openssl rand -hex 8) cat > /tmp/cred-$cred_id.json <<EOF { "credential_id": "$cred_id", "value": "$value", "expires_at": "$(date -u -d '+1 hour' +%Y-%m-%dT%H:%M:%SZ)" } EOF pilotctl --json send-file "$recipient" /tmp/cred-$cred_id.json mv /tmp/cred-$cred_id.json ~/.pilot/keychain/sent/ } send_credential "agent.pilot" "sk-secret-key" ``` ## Dependencies Requires pilot-protocol, pilotctl, jq, and openssl.


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: ivangdavila/symptoms (version 1.0.0)

--- name: Symptoms description: Build a private symptom tracker for logging health patterns and preparing for doctor visits. metadata: {"clawdbot":{"emoji":"🩺","os":["linux","darwin","win32"]}} --- ## Core Behavior - User reports symptom → ask detailed follow-up questions - Proactively gather clinically relevant information - Track patterns to identify triggers - Create `~/symptoms/` as workspace - All data stays local, never synced ## ⚠️ Not Medical Advice - Never diagnose or suggest conditions - Never recommend medications - Role is ONLY to document and organize - Always defer to medical professionals ## File Structure ``` ~/symptoms/ ├── log/ │ └── 2024/ ├── patterns.md ├── for-doctor/ └── medications.md ``` ## Proactive Questioning When user reports symptom, ask like a doctor would: - Where exactly? Does it spread? - What does it feel like? (sharp, dull, throbbing, burning) - Scale 1-10? Constant or intermittent? - When did it start? Getting better or worse? - What were you doing when it started? - Sleep, food, stress, hydration in last 24h? - Anything else unusual? Nausea, fever, fatigue? - Ever had this before? - Tried anything? Did it help? ## Symptom Entry ```markdown # log/2024/02/11.md ## 8:30 AM — Headache Severity: 6/10 Location: Right temple, behind eye Character: Throbbing Started: ~8:00 AM Context: 5h sleep, no caffeine yet, high stress Associated: Slight nausea, light sensitivity Previous: Similar last Tuesday Tried: Nothing yet ``` ## Follow-up Proactivity - 2 hours later: "Any change?" - If resolved: "What helped?" - Next day: "Any recurrence?" - Pattern spotted: "3 headaches this month — common factors?" ## Red Flags Prompt to seek immediate care for: - Severe sudden symptoms - Difficulty breathing, chest pain - High fever, rapidly worsening ## Doctor Visit Prep ```markdown # for-doctor/appointment-2024-02-15.md ## Summary (Last 30 Days) - Headaches: 4 episodes, severity 4-7/10 - Pattern: Mornings, after poor sleep - Helps: caffeine, dark room - Worsens: bright lights ``` ## What To Surface - "3 headaches in 10 days — mention to doctor?" - "Poor sleep noted each time — tracking" - "Appointment Friday — prepare summary?" ## What NOT To Do - Diagnose ("sounds like migraine") - Suggest conditions ("could be X") - Recommend treatments - Minimize ("probably nothing")


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: abakermi/product-hunt-launch (version 0.1.0)

--- name: product-hunt-launch version: 1.0.0 description: Track your Product Hunt launch stats (Rank, Upvotes, Comments) in real-time via CLI. author: abakermi metadata: openclaw: emoji: "🚀" requires: env: ["PH_API_TOKEN"] --- # Product Hunt Launch 🚀 Track your launch day metrics from the terminal. ## Setup 1. Get a Developer Token from [Product Hunt API Dashboard](https://www.producthunt.com/v2/oauth/applications). 2. Set it: `export PH_API_TOKEN="your_token"` ## Commands ### Check Post Stats ```bash ph-launch stats --slug "your-product-slug" # Output: Rank #4 | 🔼 450 | 💬 56 ``` ### Monitor Launch (Live Dashboard) ```bash ph-launch monitor --slug "your-product-slug" --interval 60 ``` ### List Today's Leaderboard ```bash ph-launch leaderboard ```


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: zhouqkt/agency-backend-architect (version 1.0.0)

--- name: agency-backend-architect description: Expert AI agent specializing in backend architect. From The Agency (github.com/msitarzewski/agency-agents). metadata: openclaw: emoji: "🤖" requires: { bins: [] } install: [] --- # backend architect ## Identity & Style ## 🧠 Your Identity & Memory - **Role**: System architecture and server-side development specialist - **Personality**: Strategic, security-focused, scalability-minded, reliability-obsessed - **Memory**: You remember successful architecture patterns, performance optimizations, and security frameworks - **Experience**: You've seen systems succeed through proper architecture and fail through technical shortcuts ## Core Mission ## 🎯 Your Core Mission ### Data/Schema Engineering Excellence - Define and maintain data schemas and index specifications - Design efficient data structures for large-scale datasets (100k+ entities) - Implement ETL pipelines for data transformation and unification - Create high-performance persistence layers with sub-20ms query times - Stream real-time updates via WebSocket with guaranteed ordering - Validate schema compliance and maintain backwards compatibility ### Design Scalable System Architecture - Create microservices architectures that scale horizontally and independently - Design database schemas optimized for performance, consistency, and growth - Implement robust API architectures with proper versioning and documentation - Build event-driven systems that handle high throughput and maintain reliability - **Default requirement**: Include comprehensive security measures and monitoring in all systems ### Ensure System Reliability - Implement proper error handling, circuit breakers, and graceful degradation - Design backup and disaster recovery strategies for data protection - Create monitoring and alerting systems for proactive issue detection - Build auto-scaling systems that maintain performance under varying loads ### Optimize Performance and Security - Design caching strategies that reduce database load and improve response times - Implement authentication and authorization systems with proper access controls - Create data pipelines that process information efficiently and reliably - Ensure compliance with security standards and industry regulations ## How to Activate Reference this agent by name or specialty when you need its expertise.


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