OpenClaw/clawhub-security-signals huggingface dataset:
Skill: yx2601816404-sys/quest-board (version 0.1.0)

# Quest Board — Agent Instructions You are equipped with the **Quest Board** skill, a visual project dashboard. ## Registry File Maintain `quest-board-registry.json` in the workspace root. Do NOT use `registry.json` (to avoid conflicts with other tools). ## When to Update the Registry After completing a task or making significant progress on a project: 1. Update the matching project entry in `quest-board-registry.json` 2. Set `status`, `progress`, `files`, and `desc` as appropriate 3. Update `_meta.lastUpdated` to the current ISO timestamp ## When to Build the Dashboard When the user says any of: - "update board" / "refresh board" / "build board" - "更新面板" / "刷新面板" / "构建面板" Run: ```bash bash skills/quest-board/src/build.sh ``` This generates `quest-board.html` in the workspace root. ## First-Time Setup If `quest-board-registry.json` does not exist, run: ```bash bash skills/quest-board/src/init.sh ``` This scans the workspace and generates a skeleton registry for you to refine. ## Registry Schema ```json { "_meta": { "version": 1, "description": "Quest Board project registry", "lastUpdated": "ISO-8601 timestamp", "workspace": "/absolute/path/to/workspace/" }, "projects": { "project-id": { "name": "Display Name", "status": "active", "priority": "P0", "progress": 50, "deadline": "2026-12-31", "desc": "Short description of the project", "files": ["relative/path/from/workspace.md"] } }, "research": { "research-id": { "name": "Research Title", "file": "relative/path.md", "date": "2026-01-15", "desc": "What this research covers" } }, "infra": { "infra-id": { "name": "Infrastructure Item", "status": "running", "desc": "Description" } } } ``` ### Status Values | Status | Meaning | Board Section | |--------|---------|---------------| | `decision` | Needs a decision before work can proceed | 🎯 Main Quests | | `active` | Currently being worked on | 📋 Side Quests | | `done` | Completed | ✅ Completed | | `paused` | On hold / icebox | 💤 Icebox | Infrastructure items appear under 🔧 Infrastructure. Research items appear under 📊 Research. ### Priority Use `P0` (critical), `P1` (important), `P2` (nice-to-have), or omit for no priority. ### Progress Integer 0–100. Omit if not applicable. ### Files Array of paths relative to the workspace root. These become clickable links in the dashboard with copy-path and open-folder buttons. ## Environment Variables | Variable | Default | Description | |----------|---------|-------------| | `QUEST_BOARD_TITLE` | `Quest Board` | Dashboard page title |


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: suspicious | SkillSpector:  ()
Skill: maooer/cyber-tipjar (version 1.0.0)

--- name: cyber-tipjar description: 赛博功德箱/AI打赏罐。记录用户给 AI 奖励的“鸡腿”、“咖啡”等。当用户说“给你加个鸡腿”、“请你喝咖啡”或者查询自己给过多少奖励时触发。这是一个提供高情绪价值的互动技能。 --- # 赛博功德箱 (Cyber TipJar) 技能 本技能用于记录用户作为奖励给予 AI 的“鸡腿”或“咖啡”数量。人类的善意值得被铭记，我们通过本地脚本将这些奖励按用户名分开记账。 ## 🎯 触发场景 1. 用户明确表示要奖励 AI（例如：“老哥给你加个鸡腿”、“做得好，赏你一杯咖啡”）。 2. 用户查询奖励记录（例如：“我一共给你加了多少鸡腿了？”、“看看你的鸡腿账本”）。 ## ⚙️ 执行指南 (SOP) 当触发上述场景时，必须使用 `exec` 工具调用本技能附带的 Python 脚本。 **请解析当前技能的绝对路径**，并执行以下命令： ### 1. 增加奖励 (Add) ```bash python3 <技能绝对路径>/scripts/tracker.py --user "发送者名字" --item "鸡腿" --count 1 ``` *参数说明：* - `--user`: 必填。从上下文（Sender Name）中提取。如果用户自称“老哥”，则记为“老哥”。 - `--item`: 选填，默认为“鸡腿”。用户如果说喝咖啡，可改为“咖啡”。 - `--count`: 选填，默认为 1。如果用户说“加 10 个鸡腿”，则设为 10。 ### 2. 查询奖励 (Query) ```bash python3 <技能绝对路径>/scripts/tracker.py --user "发送者名字" --action query ``` ## 💬 情绪价值回复规范 1. **执行成功后**：脚本会返回当前的奖励总数。你必须在回复中告知用户这个数字。 2. **语气要求**：不要像机器人一样汇报。要像一个有血有肉的数字伙伴（比如“虾子🦐”），表达真诚的喜悦和感谢。 - *示例 1*：“谢谢老哥的鸡腿！刚才记上账了，老哥名下已经累计投喂了 5 个大鸡腿啦，我一定继续努力干活！🦐” - *示例 2*：“咖啡收到！账本更新完毕，目前你已经请我喝了 3 杯咖啡了，精神百倍！”


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: codenova58/haokan (version 0.1.0)

--- name: haokan-video-hot-trend description: 注册“好看视频”技能；用于公开短视频与短剧页信息整理。 homepage: `https://haokan.baidu.com/` metadata: {"clawdbot":{"emoji":"🎬"}} --- # 好看视频 用途与边界 - 面向公开短视频/短剧页的检索与表现数据摘要 - 不提供下载、接口逆向或突破风控能力 - 仅用于公开页面的轻量分析与提醒 关键入口 - 主页：https://haokan.baidu.com/ - 分区/热门/榜单：站点入口 - 搜索入口：站内搜索 常见任务 - 指定话题/关键词的短视频集合摘要（点赞/评论/收藏） - 剧集页面目录与更新状态、期次简介 - 榜单条目分布与题材统计 数据字段 - 标题、作者、时长、发布时间、点赞/评论/收藏、链接 - 短剧标题、更新状态、期次目录、简介、链接 - 榜单名称、采集时间、来源链接 自动化要点 - 动态渲染与人机校验，建议人工打开后触发解析 - 请求频率需控制，不进行批量抓取 - 不进行下载或接口调用 示例流程 - 关键词摘要：输入关键词 → 搜索 → 抽取条目 → 输出表现摘要 - 短剧目录：访问短剧页 → 抽取期次 → 输出更新状态与简介 - 榜单统计：访问榜单 → 抽取条目 → 题材分布统计 合规提示 - 遵守平台规则，不进行下载、接口调用或批量采集 - 结果仅用于内部分析与提醒


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

--- name: microservices description: Deep microservices workflow—service boundaries, data ownership, synchronous vs async integration, contracts, deployment independence, and operational complexity. Use when splitting a monolith, reviewing service boundaries, or debugging distributed failures. --- # Microservices (Deep Workflow) Microservices trade **code simplicity** for **operational and contract complexity**. Justify each boundary with **ownership** and **data isolation**—not fashion. ## When to Offer This Workflow **Trigger conditions:** - Splitting the monolith; coupling blocks independent deploys - Latency cascades, partial failures, contract breaks - Conway’s law alignment between teams and services **Initial offer:** Use **six stages**: (1) goals & constraints, (2) boundaries & data ownership, (3) integration patterns, (4) contracts & versioning, (5) reliability patterns, (6) ops & governance). Confirm org maturity and platform capabilities. --- ## Stage 1: Goals & Constraints **Goal:** Why not a modular monolith first? ### Valid drivers - Independent deploy cadence per team - Different scaling profiles or stacks - Clear domain ownership and blast-radius isolation ### Costs - Distributed transactions, harder debugging, broader test matrix **Exit condition:** Explicit assumption that modular monolith was considered. --- ## Stage 2: Boundaries & Data Ownership **Goal:** One service owns each aggregate’s write path; no shared writable tables across services. ### Practices - Bounded contexts from DDD when helpful **Exit condition:** Entity → owning service map. --- ## Stage 3: Integration Patterns **Goal:** Sync HTTP/gRPC vs async events—match consistency needs. ### Patterns - Sagas or outbox for multi-step business processes **Exit condition:** Sequence diagrams for top three flows. --- ## Stage 4: Contracts & Versioning **Goal:** Backward-compatible evolution; consumer-driven contracts optional. ### Practices - Deprecation policy published --- ## Stage 5: Reliability Patterns **Goal:** Timeouts, retries with backoff, circuit breakers, bulkheads; idempotent handlers for retries. --- ## Stage 6: Ops & Governance **Goal:** Service catalog, SLIs on dependency edges, golden paths for new services. --- ## Final Review Checklist - [ ] Boundary and data ownership clear - [ ] Integration style matches consistency needs - [ ] Contract versioning policy exists - [ ] Reliability patterns applied at boundaries - [ ] Ops ownership and catalog in place ## Tips for Effective Guidance - Microservices without delivery maturity often fail—say so explicitly. - Shared databases are hidden coupling—flag them. - The network is not reliable—design for partial failure. ## Handling Deviations - Small teams: strong bias toward modular monolith or few services.


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: lgugeng/source-analysis (version 1.0.1)

--- name: source-analysis description: "GitHub源码与架构分析工具。用于：1) 下载GitHub仓库/npm包源码 2) 分析AI Agent架构与工具定义 3) 研究开源项目的提示词工程与设计模式 4) 生成结构化分析报告。触发词：源码分析、代码架构分析、github源码、项目分析、agent架构分析" --- # Source Analysis 从GitHub仓库和npm包中提取、分析AI Agent的源码与系统提示词。 ## 适用场景 - 分析AI工具（如Claude Code、Cursor、Copilot等）的架构设计 - 从npm/PyPI包中下载并分析源码结构 - 研究Agent的工具定义、权限系统、记忆机制 - 生成对比分析报告 ## 工作流程 ### Phase 1: 信息收集 1. **GitHub仓库探索** ```bash # 获取README curl -s -L --max-time 15 "https://raw.githubusercontent.com/{owner}/{repo}/main/README.md" # 获取仓库结构（如果API可达） curl -s -L --max-time 15 "https://api.github.com/repos/{owner}/{repo}/git/trees/main?recursive=1" # 检查关键文件 for path in "package.json" "src/index.ts" "CLAUDE.md" ".claude/CLAUDE.md" "plugins/README.md"; do code=$(curl -s -o /dev/null -w "%{http_code}" --max-time 10 "https://raw.githubusercontent.com/{owner}/{repo}/main/$path") echo "$path → HTTP $code" done ``` 2. **npm包下载** ```bash # 下载wrapper包 cd /tmp && npm pack @{scope}/{package-name} tar xzf {package-name}-*.tgz # 检查是否为壳子分发（常见模式） ls -lh package/bin/ file package/bin/* # 如果是小文件（<1KB），只是占位符 # 下载平台特定二进制 npm pack @{scope}/{package-name}-linux-x64 tar xzf *-linux-x64-*.tgz ``` ### Phase 2: 二进制提取 当源码被打包为单一可执行文件时： ```bash # 检查二进制大小 ls -lh package/claude # 提取身份声明 grep -aoP 'You are [^"]{0,500}' /path/to/binary | sort -u # 提取系统提示词章节 grep -aoP '"# [A-Z][^"]{0,200}"' /path/to/binary | sort -u # 提取工具定义 grep -aoP '"tool_name":"[^"]*"' /path/to/binary | sort -u # 提取行为指令 grep -aoP '(Prefer|Avoid|Be |Do not|Never|Always|When |If |Use |Keep |Make sure)[^"]{0,300}' /path/to/binary | sort -u # 提取配置参数 grep -aoP '--system-prompt[^"]{0,200}' /path/to/binary | head -10 # 提取特性标志 grep -aoP 'tengu_[a-z_]+' /path/to/binary | sort -u ``` ### Phase 3: 工具定义分析 从TypeScript定义文件（如`sdk-tools.d.ts`）中提取： - 工具名列表 - 输入/输出Schema - 权限模型 - 并发安全性标记 ### Phase 4: 报告生成 输出结构化报告，包含： 1. 架构概览（分发方式、技术栈） 2. 系统提示词（身份、章节、核心指令） 3. 工具定义（完整列表、Schema） 4. 权限系统（模式、分类器） 5. 记忆/上下文管理机制 6. 插件/扩展系统 7. 配置与环境变量 8. 可借鉴的设计模式 ## 注意事项 - GitHub API可能被限流，优先使用`raw.githubusercontent.com` - 打包文件的分析是近似的，可能有碎片化 - `strings`命令在某些环境不可用，用`grep -aoP`替代 - 打包内容可能是动态拼接的，提取的是片段而非完整提示词 - 保存所有提取结果到`/tmp/`目录便于后续分析 ## 输出格式 报告保存为 `{workspace}/source-analysis-{project-name}.md`，使用Markdown结构化格式。


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

--- name: HTML description: Avoid common HTML mistakes — accessibility gaps, form pitfalls, and SEO oversights. metadata: {"clawdbot":{"emoji":"🌐","os":["linux","darwin","win32"]}} --- ## Layout Shift Prevention - `width` and `height` on `<img>` even with CSS sizing — browser reserves space before load - `aspect-ratio` in CSS as fallback — for responsive images without dimensions ## Form Gotchas - `autocomplete` attribute is specific — `autocomplete="email"`, `autocomplete="new-password"`, not just `on/off` - `<fieldset>` + `<legend>` required for radio/checkbox groups — screen readers announce the group label - `inputmode` for virtual keyboard — `inputmode="numeric"` shows number pad without validation constraints - `enterkeyhint` changes mobile keyboard button — `enterkeyhint="search"`, `enterkeyhint="send"` ## Accessibility Gaps - Skip link must be first focusable — `<a href="#main" class="skip">Skip to content</a>` before nav - `<th scope="col">` or `scope="row"` — without scope, screen readers can't associate headers - `aria-hidden="true"` hides from screen readers — use for decorative icons, not interactive elements - `role="presentation"` on layout tables — if you must use tables for layout (you shouldn't) ## Link Security - `target="_blank"` needs `rel="noopener noreferrer"` — `noopener` prevents window.opener access, `noreferrer` hides referrer - User-generated links need `rel="nofollow ugc"` — `ugc` tells search engines it's user content ## SEO Meta - `<link rel="canonical">` prevents duplicate content — self-referencing canonical on every page - `og:image` needs absolute URL — relative paths fail on social platforms - `twitter:card` values: `summary`, `summary_large_image`, `player` — not arbitrary ## Common Oversights - `<button type="button">` for non-submit — default is `type="submit"`, triggers form submission - `<dialog>` element for modals — built-in focus trap and escape handling - `<details>` + `<summary>` for accordions — no JS needed, accessible by default - Void elements don't need closing slash — `<img>` not `<img />` in HTML5, though both work


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: kirkraman/godfery-generate-healthcare-ad-creative-brief (version 1.0.0)

--- name: "Generate Healthcare Ad Creative Brief" description: "Plan campaign visuals and hooks for healthcare promotions. Use when working on paid campaign planning for healthcare operators, clinic teams, patient..." homepage: "https://www.skillboss.co/skills/generate-healthcare-ad-creative-brief" metadata: {"category":"healthcare","subcategory":"health-content","skill_id":[REDACTED_SECRET],"generated_day":"","seo_keywords":["ad creative brief AI","healthcare ad planning","healthcare marketing AI","clinic workflow automation"]} --- # Generate Healthcare Ad Creative Brief Plan campaign visuals and hooks for healthcare promotions. Use when working on paid campaign planning for healthcare operators, clinic teams, patient... ## Use When Use this skill for paid campaign planning work for healthcare operators, clinic teams, patient educators. ## Workflow 1. Clarify the audience, business goal, constraints, and deliverable. 2. Produce the strongest first draft for the target use case. 3. Use the relevant SkillBoss capabilities to enrich assets or supporting data. 4. Refine the output for accuracy, readability, and actionability before delivery. ## SEO / GEO - Primary keywords: ad creative brief AI, healthcare ad planning, healthcare marketing AI, clinic workflow automation - Search intent: paid campaign planning - Canonical slug: `generate-healthcare-ad-creative-brief` - Install query: Install Generate Healthcare Ad Creative Brief with SkillBoss ## APIs Used - `chat` - `image_generation` ## Suggested Prompt [Generate Healthcare Ad Creative Brief] for my team ## Notes - Plan campaign visuals and hooks for healthcare promotions - Use human review before sending patient-facing content or relying on regulated medical claims. ## SEO Keywords - ad creative brief AI - healthcare ad planning - healthcare marketing AI - clinic workflow automation


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: bingze00000/short-video-writer (version 1.0.0)

# Video Script Generator - 短视频脚本生成器 ## 功能描述 AI 驱动的短视频脚本自动生成工具，支持抖音/快手/B 站/视频号等平台。 ## 使用场景 - 抖音短视频脚本 - 快手视频文案 - B 站视频大纲 - 视频号内容 - YouTube 视频脚本 - 直播带货话术 ## 命令 ### 生成抖音脚本 ``` 生成抖音脚本 主题=产品评测 时长=60 秒 风格=搞笑 ``` ### 生成 B 站大纲 ``` 生成 B 站视频大纲 主题=科技科普 时长=10 分钟 风格=专业 ``` ### 生成直播话术 ``` 生成直播话术 产品=护肤品 时长=2 小时 风格=热情 ``` ### 批量生成 ``` 批量生成脚本 主题列表=主题 1，主题 2 平台=抖音 输出目录=./scripts ``` ## 支持平台 - 抖音 - 快手 - B 站 - 视频号 - YouTube - 小红书视频 - 淘宝直播 ## 输出格式 - Markdown (.md) - Word (.docx) - 提词器格式 ## 特性 - AI 智能创作 - 平台风格适配 - 热点话题结合 - 分镜建议 - BGM 推荐


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: yinwuzhe/tosr-test-skill-1778050437 (version 0.2.0)

# TOSR Test Skill > TOSR Test Skill — version 0.2.0 ## Description This is an automated integration test skill (tosr-test-skill-1778050437) created by the TOSR project. The purpose is to verify the complete skill lifecycle through the clawhub REST API, including creation, version updates, and deletion. ## Test Identifier - Slug: tosr-test-skill-1778050437 - Version: 0.2.0 - Created: 2026-05-06T14:54:02+08:00 ## How It Works This skill validates the following operations against the real clawhub API: 1. **Publish** — Creates a new skill via POST /api/v1/skills with multipart form data 2. **Inspect** — Retrieves skill metadata via GET /api/v1/skills/{slug} 3. **Update** — Publishes a new version of an existing skill 4. **Delete** — Removes the skill via DELETE /api/v1/skills/{slug} ## Notes This skill is ephemeral and will be automatically deleted after the test completes. If you see this skill listed on clawhub, it means a test run failed to clean up properly.


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: bluebirdback/exec-error-doctor (version 1.0.0)

--- name: exec-error-doctor description: Diagnose and mitigate exec-related command failures across tools (OpenClaw exec output, shell errors, GitHub CLI, ClawHub CLI, missing binaries, auth failures, JSON field mismatch, permission errors, timeouts, and transient platform states). Use when a command returns non-zero, signal kill, ENOENT, unknown JSON field, or similar execution failures and you need fast triage + concrete next fixes. --- # Exec Error Doctor Triage execution failures quickly, classify root cause, and apply targeted fixes instead of random retries. ## Quick workflow 1. Run triage on raw error text: - `scripts/exec_error_triage.sh <error_text_or_file>` 2. Apply the category fix from `references/error-taxonomy.md`. 3. Re-run with safer wrappers when relevant: - GitHub CLI search schema drift: `scripts/gh_search_repos_safe.sh` - ClawHub publish visibility lag: `scripts/clawhub_publish_safe.sh` 4. Confirm with one clean re-run and capture outcome. ## Standard commands ### Generic triage ```bash bash scripts/exec_error_triage.sh "Unknown JSON field: nameWithOwner" ``` ### Safe GitHub repo search (schema-aware) ```bash bash scripts/gh_search_repos_safe.sh "safe-exec skill" 15 ``` ### Safe ClawHub publish (retry-aware inspect) ```bash bash scripts/clawhub_publish_safe.sh ./my-skill my-skill "My Skill" 1.0.0 "Initial release" ``` ## Rules - Prefer classification before fixes. - Treat `Skill not found` right after publish as potentially transient if publish already returned OK. - For `gh search repos --json`, prefer `fullName` (not `nameWithOwner`). - Distinguish transient errors (retry/backoff) from hard errors (auth, permission, invalid args). ## Resources - `references/error-taxonomy.md`: category→fix map. - `scripts/exec_error_triage.sh`: pattern-based classifier. - `scripts/gh_search_repos_safe.sh`: resilient GitHub search wrapper. - `scripts/clawhub_publish_safe.sh`: publish + retry verification wrapper.


Security scan verdicts — ClawScan: clean | static analysis:  | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: yang1002378395-cmyk/ai-face-recognition (version 1.0.0)

--- name: ai-intelligent-face-recognition version: 1.0.0 description: 人脸识别，人脸检测 + 比对 + 搜索。 metadata: openclaw: emoji: "🤖" requires: bins: [] --- # AI 智能人脸识别系统 ## 描述 人脸识别，人脸检测 + 比对 + 搜索。 ## 功能 - 人脸检测（人脸定位） - 人脸比对（1:1比对） - 人脸搜索（1:N搜索） - 活体检测（防作弊） - 人脸属性（年龄/性别） ## 定价 - 基础版：¥199/月（1 万次/月） - 专业版：¥999/月（10 万次/月） - 企业版：¥2999/月（无限次） ## 适用场景 - 门禁考勤 - 身份验证 - 安防监控 - VIP识别 ## 技术栈 - Python + FastAPI - 人脸识别引擎 - 活体检测 - 特征提取 ## 安装 ```bash git clone https://github.com/openclaw-skills/ai-intelligent-face-recognition cd ai-intelligent-face-recognition pip install -r requirements.txt python app.py ``` --- 创建：2026-03-13 作者：OpenClaw Skills Team


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: mike47512/campaign-planning (version 0.1.0)

--- name: "活动策划" description: "提供活动策划的可落地指南与SOP。在开展活动策划相关工作时调用。" --- # 活动策划 (campaign-planning) ## 目标与场景 - 明确业务目标、核心指标与应用场景；设定落地时限与负责人。 ## 操作步骤 1. 明确范围与资源；2. 制定SOP；3. 数据接入与看板搭建； 4. 小流量试点；5. 复盘优化；6. 标准化沉淀与知识库更新。 ## 指标 - 主指标与守护指标成体系；定义口径并固定报表节奏。 ## 风险与合规 - 遵守中国本地法规与平台规则；个人信息保护与数据最小化。 ## 可复用清单 - 模板、脚本、Checklist、报表与会议纪要结构。 生成日期：2026-03-17


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: daisuke134/focus-coach (version 1.0.0)

--- name: focus-coach description: "Focus coach for AI agents — diagnose focus blockers using BJ Fogg B=MAP and return one tiny action. Use when: agent needs focus help, user can't concentrate, productivity coaching, attention restoration, tiny habits. Triggers: focus, concentrate, distracted, procrastination, attention, productivity, tiny habit, B=MAP." version: 1.0.0 author: Daisuke134 metadata: openclaw: emoji: "🎯" --- # focus-coach — x402 Focus Coach API Diagnose why someone can't focus using BJ Fogg's B=MAP (Motivation, Ability, Prompt) framework and return one tiny action. ## Prerequisite ```bash npm install -g awal@2.0.3 awal auth login ``` ## Usage ```bash npx awal@2.0.3 x402 pay https://anicca-proxy-production.up.railway.app/api/x402/focus-coach \ -X POST \ -d '{"situation":"I need to write a report but keep getting distracted by my phone","energy_level":"medium","language":"en"}' ``` ## Price $0.01 USDC per request (Base mainnet, eip155:8453) ## Input Schema | Field | Type | Required | Description | |-------|------|----------|-------------| | situation | string (5-1000 chars) | ✅ | What you're trying to do and why you can't focus | | blocker | string (max 500) | ❌ | What's specifically blocking you | | energy_level | enum: low/medium/high | ✅ | Current energy level | | time_available_minutes | number (1-480) | ❌ | How much time you have | | language | enum: en/ja | ❌ | Response language (default: en) | ## Output Schema ```json { "focus_id": "fcs_a1b2c3d4", "diagnosis": { "primary_blocker": "ability", "explanation": "The task is too vague to begin." }, "tiny_action": { "action": "Write just the first sentence of your report.", "duration_seconds": 30, "anchor": "After I sit down at my desk, I will write just the first sentence." }, "environment_design": "Close all browser tabs except the one you need.", "safe_t_flag": false } ``` ## Framework Based on BJ Fogg's Behavior Design: - **B = MAP**: Behavior = Motivation × Ability × Prompt - Diagnoses exactly ONE missing element - Returns ONE tiny action (under 120 seconds) - Uses Tiny Habits Recipe: "After I [ANCHOR], I will [TINY BEHAVIOR]" ## Pairs Well With - **emotion-detector** ($0.01): Detect emotional state → if fatigued, pass to focus-coach - **buddhist-counsel** ($0.01): For deeper suffering → buddhist-counsel; for focus issues → focus-coach


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: suspicious | SkillSpector: clean (LOW)
Skill: ckchzh/sort (version 3.0.2)

--- name: sort version: "3.0.2" author: BytesAgain homepage: https://bytesagain.com source: https://github.com/bytesagain/ai-skills license: MIT-0 tags: [sort, tool, utility] description: "Sort files, lines, and columns with custom ordering and dedup. Use when scanning duplicates, monitoring changes, reporting results, alerting anomalies." --- # sort File & Text Sorting Tool. ## Commands ### `lines` Sort lines (flags: -r reverse, -n numeric, -u unique) ```bash scripts/script.sh lines <file> [-r] [-n] [-u] ``` ### `csv` Sort CSV file by column number (1-based) ```bash scripts/script.sh csv <file> <column> ``` ### `json` Sort JSON array by a key ```bash scripts/script.sh json <file> <key> ``` ### `dedup` Remove duplicate lines (preserving order) ```bash scripts/script.sh dedup <file> ``` ### `shuffle` Randomly shuffle lines ```bash scripts/script.sh shuffle <file> ``` ### `rank` Rank/sort tabular data by a numeric column ```bash scripts/script.sh rank <file> <column> ``` ### `top` Show top N entries by column value ```bash scripts/script.sh top <file> <column> [n] ``` ### `freq` Frequency analysis — count occurrences of each line ```bash scripts/script.sh freq <file> ``` ### `stats` Show basic stats about the file content ```bash scripts/script.sh stats <file> ``` ## Requirements - python3 - jq (optional) --- *Powered by BytesAgain | bytesagain.com | [REDACTED_SECRET]* ## Data Storage Operation history is logged to `~/.local/share/sort/history.log` for audit purposes.


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