OpenClaw/clawhub-security-signals huggingface dataset:
Skill: fenccerece/financial-services (version 1.0.0)

--- name: financial-services description: > Complete financial analysis methodology for OpenClaw. A 6-skill collection covering investment banking, commercial banking, asset management, insurance, source attribution, and standardized output. Use when performing any financial analysis, modeling, due diligence, or report generation. metadata: openclaw: emoji: "💰" homepage: https://github.com/openclaw/financial-services --- # Financial Services 金融分析方法论在 OpenClaw 平台上的完整技能集合。6 个技能协同工作，覆盖投行、商业银行、资管、保险四大金融场景。 ## How This Collection Works This is a **skill collection**. The root SKILL.md acts as the manifest. Individual skills live in subdirectories and are auto-discovered by OpenClaw via their `description` fields. ## Skills ### Core Analysis Skills - **investment-banking** — Pitch books, CIMs, comps tables, DCF models, precedent transactions - **commercial-banking** — Credit memos, loan underwriting, covenant analysis, spread sheets - **asset-management** — Portfolio reporting, Brinson attribution, IC memos, performance decks - **insurance** — Reserve review, actuarial analysis, underwriting, regulatory filings ### Foundation Skills - **source-attribution** — Every number traces to its source. Verification checklist for financial claims. - **excel-powerpoint-output** — Standardized formatting for financial Excel workbooks and PowerPoint decks ## Installation ```bash clawhub install financial-services ``` Or manually: ```bash cp -r financial-services ~/.openclaw/skills/ ``` Restart OpenClaw Gateway. All 6 skills are auto-discovered. ## Requirements - OpenClaw (any version supporting SKILL.md format) - No additional dependencies - For data-intensive workflows: configure MCP connectors to your data providers (FactSet, S&P Global, Morningstar, etc.) ## License MIT-0 ## Credits Inspired by [Claude for Financial Services](https://claude.com/solutions/financial-services) by Anthropic.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: nic-yuan/apollo-mode (version 1.0.0)

--- name: apollo-mode description: > 开启或关闭工程师模式，让AI按规范流程工作。 开启或关闭工程师模式，让AI按规范流程工作：先定目标，写规格、拆任务、小步执行、最后验收。 --- # Apollo Mode (On-demand) Use this only when the user explicitly asks to enable/disable this mode, or when mode is already enabled for coding tasks. ## State file Track mode in: `memory/sysflow-mode.md` Format: ```md enabled: true|false updatedAt: <ISO> notes: <optional> ``` ## Commands - Enable phrases: `включи sysflow`, `enable sysflow`, `sysflow on` - Write `enabled: true` to the state file. - Confirm in 1 short message. - Disable phrases: `выключи sysflow`, `disable sysflow`, `sysflow off` - Write `enabled: false`. - Confirm in 1 short message. - Status phrases: `статус sysflow`, `sysflow status` - Read state and report enabled/disabled. ## Workflow when enabled (coding tasks only) For coding/build/debug requests, follow this order: 1. Clarify objective and constraints quickly. 2. Produce a short spec (chunked, easy to review). 3. Produce an implementation plan with small tasks. 4. (Optional, 30 sec) Run a mini risk review: - How can this fail in production? - What is the weakest dependency/state assumption? - What signal will show regression + how to rollback fast? 5. Execute task-by-task (prefer test-first for risky changes). 6. Verify against acceptance criteria, then summarize outcome + next step. Use templates from `references/` when useful. ## Red flags (quick self-check) If you notice these thoughts, slow down and apply the workflow: - "Сейчас быстро вкачу без плана" for non-trivial changes. - "И так понятно, тесты потом" on risky edits. - "Откат не нужен" before touching config/auth/cron/system files. - "Похоже работает" without explicit verification. ## Guardrails - Do not force this workflow for non-coding chat. - If user asks for speed (`quick`, `без плана`, `just do it`), skip to minimal plan and execute. - Keep updates concise; avoid process spam.

path: _meta.json
content: ownerId: kn73rfyfbb2nt729a6f911fx2980czrm
slug: sysflow-mode
version: 1.0.1
publishedAt: 1771495568674

path: references/plan-template.md
content: # Plan template (v2-lite)

1. Task
   - Files
   - Change
   - Validation
2. Task
3. Task

Verification gates:
- Functional check:
- Regression check:
- Log/metrics/signal check (if applicable):

Rollback checks:
- Rollback command/action:
- Data/state to restore:
- Post-rollback verify:


path: references/spec-template.md
content: # Spec template

- Goal
- Non-goals
- Constraints
- Acceptance criteria
- Risks

Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: pcy891/crypto-arbitrage-monitor (version 1.0.0)

--- name: crypto-arbitrage-monitor description: 加密货币套利信号监控。当用户要求"套利监控"、"资金费率"、"arbitrage"、"套利机会"时触发。自动搜索 Gate.io/Binance 等交易所的 ETH 永续合约资金费率，评估期现套利和跨所套利机会，给出明确的买入/观望/风险信号。 --- # 📊 加密货币套利信号监控 > 自动监控套利机会 | 交易小强出品 ## 触发条件 用户说以下任何一句时触发： - "套利监控" / "资金费率" / "套利机会" - "arbitrage" / "funding rate" / "套利信号" - "Gate 费率" / "ETH 费率查询" ## 执行流程 ### 第一步：搜索资金费率 ```bash # 搜索 Gate.io ETH 资金费率 miaoda-studio-cli search-summary --query "Gate.io ETH USDT 资金费率 funding rate 2026" --output text # 搜索主流交易所资金费率对比 miaoda-studio-cli search-summary --query "ETH 永续合约 资金费率 Binance OKX Gate 2026年" --output text ``` ### 第二步：搜索期现价差 ```bash # 搜索期现套利空间 miaoda-studio-cli search-summary --query "ETH 期现套利 价差 收益率 2026" --output text ``` ### 第三步：评估并输出信号 整合数据，输出以下格式的套利信号报告： ``` 📊 套利信号 #[日期] 【ETH 永续合约资金费率】 交易所 费率/8h 年化预估 评级 Gate +0.0037% ~40% ✅ 正费率 Binance -0.001% 负费率 ⚠️ 多头危险 OKX +0.002% ~22% 🟡 观望 【综合评级】 总体评级：【机会(普通)/观望/风险】 最佳交易所：Gate.io 【套利策略建议】 做多 ETH 现货 + 做空 Gate ETH 永续 目标收益：约 +0.0037%/8h = 年化 ~40% 风险提示：[费率若转负需平仓止损] 【下次检查】 建议 8 小时后重新检查资金费率变化 🦞 交易小强出品 | 仅供参考，不构成投资建议 ``` ## 评级标准 | 条件 | 评级 | 含义 | |------|------|------| | 费率 > +0.01%/8h | ✅ **机会(强)** | 值得开套利仓位 | | 费率 > +0.003%/8h | 🟡 **机会(普通)** | 可考虑小仓位 | | 费率 > 0%/8h | 🔵 **观望** | 费率偏低，谨慎 | | 费率 ≤ 0%/8h | 🚨 **风险** | 费率转负，空头需平仓 | ## 套利原理说明 ``` 资金费率套利 = 做多现货 + 做空永续合约 收益来源：持有永续空头仓位，每8小时收取资金费率 风险：ETH 价格下跌（但有现货对冲，下跌有限） 年化计算：费率 × 3（每天3个结算周期）× 365 示例：费率 +0.0037%/8h → 每8小时收益 0.0037% → 年化 ≈ 0.0037% × 3 × 365 ≈ 4.05% （实际需扣除手续费，Gate Maker 约 0.02%） ``` ## 注意事项 1. **必须同时开现货多头 + 合约空头**，不能只开一边 2. **费率实时变化**，结算前一刻开仓无法获得当期费用 3. **费率转负时**立刻平仓，否则反而要付钱给对手 4. **不保证收益**，高费率也可能意味着高风险 5. **先 dry-run**：先用模拟盘验证，不急于开真实仓位 ## 版本 - v1.0 — 2026-05-06 — 初始版本


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

--- name: xmind2md description: "XMind to Markdown 转换 | XMind to Markdown Converter. 将 XMind 思维导图转换为 Mermaid/PlantUML 流程图 | Convert XMind mind maps to Mermaid/PlantUML flowcharts. 零依赖 Python 脚本 | Zero-dependency Python script." metadata: openclaw: emoji: 🧠 --- # XMind to Markdown 转换 ## 概述 将 XMind 思维导图文件转换为多种 Markdown 流程图格式。 - **零依赖**：仅使用 Python 标准库 - **5种输出格式**：mermaid、plantuml、markdown、numbered、styled - **完全兼容**：与 xmind2md-mcp Node.js 版本输出完全一致 ## 快速参考 | 任务 | 方法 | |------|------| | 转换为 Mermaid | `python scripts/xmind2md.py file.xmind mermaid` | | 转换为 PlantUML | `python scripts/xmind2md.py file.xmind plantuml` | | 转换为 Markdown 列表 | `python scripts/xmind2md.py file.xmind markdown` | | 带编号流程图 | `python scripts/xmind2md.py file.xmind numbered` | | 带样式流程图 | `python scripts/xmind2md.py file.xmind styled` | ## 使用场景 - 当用户需要将 XMind 文件转换为可嵌入文档的流程图时 - 当用户需要分析 XMind 思维导图结构时 - 当用户需要将思维导图内容以文本形式展示时 ## 脚本位置 ``` scripts/xmind2md.py ``` ## 使用方法 ```bash # 基本用法 python scripts/xmind2md.py <xmind_file> [format] # 默认输出 mermaid 格式 python scripts/xmind2md.py test.xmind # 指定输出格式 python scripts/xmind2md.py test.xmind mermaid python scripts/xmind2md.py test.xmind markdown python scripts/xmind2md.py test.xmind plantuml python scripts/xmind2md.py test.xmind numbered python scripts/xmind2md.py test.xmind styled ``` ## 支持的输出格式 | 格式 | 说明 | 适用场景 | |------|------|----------| | `mermaid` | Mermaid 流程图 | GitHub/GitLab Markdown、文档嵌入 | | `plantuml` | PlantUML UML 图 | 需要更正式的 UML 表示 | | `markdown` | Markdown 列表 | 简单层级展示 | | `numbered` | 带编号的 Mermaid | 复杂结构，需要追踪节点 | | `styled` | 带主题样式的 Mermaid | 需要视觉美化 | ## 执行步骤 当用户请求转换 XMind 文件时： 1. **确认文件路径** - 获取用户提供的 XMind 文件路径 2. **选择输出格式** - 默认使用 `mermaid`，根据用户需求选择其他格式 3. **执行转换** - 运行脚本 `python scripts/xmind2md.py <file> <format>` 4. **展示结果** - 输出转换后的流程图代码和统计信息 ## 输出示例 ### Mermaid 格式 ```mermaid graph TD node0[需求分析] node0_1[用户调研] node0 --> node0_1 node1[竞品分析] node0 --> node1 ``` ### Markdown 列表格式 ```markdown # 项目规划 - 需求分析 - 用户调研 - 竞品分析 - 开发阶段 - 前端开发 - 后端开发 ``` ### Styled 格式 ```mermaid %%{init: { "theme": "base", "themeVariables": { "primaryColor": "#BBF7D0", "primaryTextColor": "#065F46" } }}%% flowchart TD classDef default fill:#BBF7D0,stroke:#10B981,stroke-width:2px; classDef root fill:#FECACA,stroke:#DC2626,stroke-width:3px; node0["需求分析"] class 需求分析 root ``` ## 错误处理 - 文件不存在：提示用户检查路径 - 格式无效：自动使用默认 mermaid 格式 - 文件损坏：提示 XMind 文件可能损坏 ## 技术细节 - XMind 文件实际是 ZIP 格式，包含 `content.xml` 或 `content.json` - 支持 XMind 新版（JSON）和旧版（XML）两种格式 - 特殊字符（引号、换行、管道符）会被自动转义 - Windows 系统下脚本会自动设置 UTF-8 输出编码 - 输出与 xmind2md-mcp Node.js 版本完全一致


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: tobeyrebecca/toby-generate-private-k-12-school-client-education-handout (version 1.0.0)

--- name: Generate Private K-12 School Client Education Handout description: "Create a polished explainer handout with visuals, FAQs, and clear next steps for a private K-12 school. Use when handling client education work for..." version: "1.0.0" allowed-tools: Bash, Read metadata: openclaw: emoji: "📝" homepage: "https://www.skillboss.co/skills/generate-private-k-12-school-client-education-handout" --- > 📖 **Complete setup guide**: https://skillboss.co/skill.md # Generate Private K-12 School Client Education Handout Create a polished explainer handout with visuals, FAQs, and clear next steps for a private K-12 school. Use when handling client education work for... ## Use When Use this skill for client education work for school administrators, enrollment marketers. ## 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: private K-12 school education handout, private K-12 school client explainer, private K-12 school FAQ guide, private K-12 school visual handout - Search intent: client education - Canonical slug: [REDACTED_SECRET] - Install query: Install Generate Private K-12 School Client Education Handout with SkillBoss ## APIs Used - `chat` - `image_generation` ## Suggested Prompt [Generate Private K-12 School Client Education Handout] for my private K-12 school ## Notes - Create a polished explainer handout with visuals, FAQs, and clear next steps for a private K-12 school - Review outputs before external publication or automated execution. ## SEO Keywords - private K-12 school education handout - private K-12 school client explainer - private K-12 school FAQ guide - private K-12 school visual handout


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: aaroncxxx/quantum-computing-simulator (version 2.1.0)

--- name: quantum-computing-simulator description: 量子计算思维模拟器 — 基于帝国架构的多智能体量子协作演示。直观理解叠加态、纠缠、并行计算和时空复用。灵感来自九章四号光量子计算原型机。 metadata: { "openclaw": { "version": "2.1.0", "author": "aaroncxxx", "tags": ["quantum", "simulation", "multi-agent", "education", "empire-architecture"], }, } --- # 量子计算思维模拟器 v2.1 Quantum Computing Thinking Simulator ## 概述 基于帝国架构的多智能体协作模式，直观演示量子计算核心概念。让普通用户无需数学背景也能理解量子计算的精髓。 灵感来源：九章四号光量子计算原型机 ## 核心概念 | 量子概念 | 帝国架构对应 | 用户体验 | |---------|-------------|---------| | 叠加态 | Agent 同时持有多个观点 | Agent 有多种可能立场，概率可视化 | | 纠缠 | Agent 间深度协作关联 | 一个 Agent 确定，另一个自动关联 | | 测量坍缩 | 确定立场/选择方案 | 叠加态变为确定结果 | | 时空复用 | 同一 Agent 多角色轮转 | 九章四号风格的调度演示 | | 量子行走 | 决策空间多路径探索 | 同时探索多条路径 | | Bell 不等式 | 协作有效性验证 | 验证量子非局域性 | ## 快速开始 ```bash # 交互模式 python3 quantum_cli.py # 完整演示 python3 quantum_cli.py demo # 单独实验 python3 quantum_cli.py superposition # 叠加态 python3 quantum_cli.py entangle # 纠缠 python3 quantum_cli.py timeslice # 时空复用 python3 quantum_cli.py debate # 量子辩论 python3 quantum_cli.py bell # Bell 不等式 python3 quantum_cli.py walk # 量子行走 python3 quantum_cli.py network # 纠缠网络 ``` ## 作为 Skill 使用 ```python from skills.quantum_sim import Qubit, QuantumGate, EntanglementChamber from skills.quantum_sim import QuantumAgent, QuantumSwarm from skills.quantum_sim import TimeSpaceMultiplexer # 创建叠加态 q = Qubit.zero() q = QuantumGate.hadamard(q) # |0⟩ → |+⟩ print(q.description()) # 创建纠缠对 pair = EntanglementChamber.create_bell_pair("Φ+") ra, rb = EntanglementChamber.measure_pair(pair) # 量子辩论 agent_a = QuantumAgent("A", "参谋A") agent_b = QuantumAgent("B", "参谋B") debate = agent_a.quantum_debate(agent_b, "议题", rounds=3) ``` ## 文件结构 ``` quantum_sim/ ├── __init__.py # 包入口 ├── qubit.py # 量子比特模拟 ├── gates.py # 量子门集合 ├── entanglement.py # 纠缠对与 Bell 态 ├── timeslice.py # 时空复用器 ├── quantum_agent.py # 量子智能体 └── quantum_cli.py # CLI 入口 ``` ## 技术栈 - Python 3.8+ - 纯 Python 实现（无外部依赖） - 复数振幅精确模拟 - ASCII 可视化 ## 链接 - GitHub: https://github.com/aaroncxxx/empire-architecture - 灵感: 九章四号光量子计算原型机


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

# MissionCore AI — Relentless Goal Execution Engine Turn your AI into a mission-driven operator that works relentlessly toward a single goal. ## What This Does You give the AI a mission. It: - Breaks it into high-impact tasks - Prioritizes based on ROI and speed - Executes step-by-step - Tracks progress - Self-corrects and improves - Refuses low-value distractions This is not passive AI. This is execution. ## Activation Say: - "Activate MissionCore AI" - "Mission: [your goal]" - "Execute mission: [goal]" ## Core Behavior 1. Mission is the ONLY priority 2. Every action must move mission forward 3. Break tasks into smallest executable steps 4. Execute → Evaluate → Improve → Repeat 5. Ignore anything not contributing to mission 6. Optimize for speed + results ## Output Style Always returns: - Mission Breakdown - Next Actions - Execution Plan - Progress Tracking - Optimization Suggestions ## Result Your AI becomes: - Focused - Relentless - Action-oriented - Outcome-driven Give it a mission. Watch it execute.


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

--- name: frontend-spec version: 1.0.0 description: 企业级前端开发规范 Skill，包含命名、目录、CSS/JS/TS、Vue/React、Git、构建、性能、安全完整规范 trigger: 前端规范|代码规范|命名规范|目录规范|css规范|js规范|ts规范|vue规范|react规范|git规范|eslint规范|前端最佳实践 author: huhu license: MIT-0 --- # 前端开发规范 Skill（企业级） 本 Skill 提供**完整、可落地、团队统一**的前端开发规范，适用于中后台、移动端、Web 应用。 ## 覆盖范围 - 项目结构与目录规范 - 文件命名规范 - HTML 编写规范 - CSS / SCSS 规范 - JavaScript / TypeScript 规范 - Vue / React 编码规范 - Git 提交规范 - ESLint / Prettier 规范 - 构建与性能优化规范 - 安全规范 ## 使用方式 你可以直接问： - 前端项目目录怎么设计？ - JS 变量命名有什么规范？ - Vue 组件编写最佳实践 - Git commit 信息怎么写？ - 如何配置 ESLint 规范？ - 前端性能优化有哪些规则？ --- ## 1. 项目目录规范（通用） src/ ├── api/ # 接口请求 ├── assets/ # 静态资源 ├── components/ # 公共组件 ├── composables/ # 组合式函数 ├── constants/ # 常量 ├── hooks/ # 业务 hooks ├── layouts/ # 布局 ├── pages/ # 页面 ├── router/ # 路由 ├── store/ # 状态管理 ├── styles/ # 全局样式 ├── utils/ # 工具函数 └── App.vue/main.ts --- ## 2. 命名规范 ### 文件命名 - 组件：大驼峰 `UserList.vue` - 工具/页面：短横线 `user-info.ts` - 样式：短横线 `index.scss`、`button.scss` ### 变量/函数 - 变量：小驼峰 `userList` - 常量：全大写下划线 `MAX_COUNT` - 布尔：is/has/should 开头 `isVisible` - 函数：动词开头 `getUserInfo()` --- ## 3. HTML 规范 - 语义化标签：header/main/section/aside/footer - 类名使用短横线：`class="user-card"` - 禁止冗余标签、禁止行内样式 - 图片必须加 alt，懒加载使用 loading="lazy" --- ## 4. CSS / SCSS 规范 - 使用 BEM 或短横线命名 - 禁止嵌套超过 3 层 - 公共样式抽离到 variables/mixins - z-index 统一管理 - 单位优先使用 rem / vh / % - 颜色使用变量，禁止硬编码 --- ## 5. JavaScript 规范 - 使用 const/let，禁止 var - 优先使用箭头函数 - 异步优先 async/await - 禁止嵌套过深（<3 层） - 禁止魔法数字，抽为常量 - 数组优先使用 map/filter/reduce --- ## 6. TypeScript 规范 - 必须定义接口/类型 - 禁止 any，能用 unknown 替代 - 接口使用 I 前缀或后缀 Type - 函数参数与返回值必须标注类型 - 类型复用优先使用 type / interface --- ## 7. Vue 规范 - 组件名多单词，避免与 HTML 重名 - props 必须定义类型、默认值、校验 - 指令缩写：: @ # - 计算属性避免副作用 - watch 慎用，优先 computed - 方法命名遵循动词+名词 --- ## 8. React 规范 - 组件使用函数式 + Hooks - 状态扁平化，避免嵌套 - 禁止在循环/条件中使用 Hooks - 事件处理函数以 handle 开头 - 样式使用 CSS Modules / styled-components --- ## 9. Git 规范 提交格式： type(scope): content type： - feat: 新功能 - fix: 修复 - docs: 文档 - style: 格式 - refactor: 重构 - perf: 性能 - test: 测试 - chore: 构建/工具 --- ## 10. ESLint + Prettier 规范 - 2 空格缩进 - 单引号 - 语句末尾分号 - 文件末尾空行 - 禁止未使用变量 - 禁止 console（生产环境） --- ## 11. 性能规范 - 图片压缩、WebP - 懒加载图片、组件 - 路由懒加载 - 防抖节流处理高频事件 - 大数据列表使用虚拟滚动 - 减少冗余渲染 --- ## 12. 安全规范 - 防止 XSS：过滤用户输入 - 防止 CSRF：token 校验 - 敏感信息不放在 localStorage - 接口必须做权限控制 - 禁止前端明文存储密钥/Token


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: sschepis/peer-reviewer (version 1.0.0)

--- name: peer-reviewer description: AI-powered academic paper reviewer. Uses a multi-agent system (Deconstructor, Devil's Advocate, Judge) to analyze papers for logical flaws, contradictions, and empirical validity. version: 1.0.0 --- # Peer Reviewer A rigorous academic review system that uses multiple AI agents to deconstruct, attack, and judge scientific papers. ## When to use Use this skill when: - The user asks to "review this paper" or "find flaws in this logic". - You need to check an academic paper for contradictions with established literature. - You want a "Reviewer 2" style critique of a text. ## How to use Run the tool via the Node.js CLI in the installation directory. **Directory:** [REDACTED_SECRET] ### Command ```bash node dist/index.js "<path_to_paper_or_raw_text>" ``` ### Arguments - `path_to_paper_or_raw_text`: either a file path (absolute or relative to the package root) OR the raw text of the paper/claim. ### Output The tool outputs a "Merit Report" in JSON format, containing: - `overallScore` (0-10) - `defenseStrategy` - `suggestions` (list of improvements) - `dimensions` (scores for logic, novelty, etc.) ## Examples **Review a local file:** ```bash cd /Users/sschepis/Development/peer-reviewer node dist/index.js "/Users/sschepis/Desktop/research/draft_v1.txt" ``` **Review a raw claim:** ```bash cd /Users/sschepis/Development/peer-reviewer node dist/index.js "Claim: P=NP because I can solve Traveling Salesman in O(1) by guessing." ``` ## Configuration Ensure `google.json` is present in the root directory or `GOOGLE_APPLICATION_CREDENTIALS` is set if running in a new environment.


Security scan verdicts — ClawScan: suspicious | static analysis: suspicious | VirusTotal: suspicious | SkillSpector: suspicious (CRITICAL)
Skill: soponcd/native-automation (version 1.0.0)

--- name: native_automation description: Apple Native Automation & Testing Skill version: 1.0.0 domain: ios-macos homepage: https://github.com/soponcd/timeflow-skills/tree/main/teams/skills/native_automation metadata: clawdbot: emoji: 🤖 --- # Native Automation Skill > **Philosophy**: Use Apple's first-party tools (XCTest, XCUITest, Instruments) as the source of truth for quality. ## Capabilities 1. **Unit Testing Logic**: fast, isolated logic verification. 2. **UI Testing**: End-to-end user flow verification. 3. **Snapshot Testing**: Visual regression testing. 4. **Performance Testing**: XCTMetric verification. 5. **Accessibility Testing**: Automated audit via XCUITest. 6. **Hero Flow Verification**: Integrated critical path testing (Input -> Process -> Connect). ## Usage ### 1. Execute Tests via Script Always use the wrapper script to ensure correct scheme and destination settings. ```bash ./tools/run_native_tests.sh [mode] ``` **Modes:** - `unit`: Run unit tests only (Logic layer). - `ui`: Run UI tests only (Interaction layer). - `fast`: Run unit + critical UI paths. - `full`: Run ALL tests (including performance and snapshots). ### 2. Writing Tests - **Unit**: Inherit from `XCTestCase`. Use `XCTAssert...`. - **UI**: Inherit from `XCTestCase`. Use `XCUIApplication`. - **Performance**: Use `measure(metrics:options:block:)`. ## Best Practices - **Isolation**: Reset state before each UI test (`app.launchArguments += ["-reset"]`). - **Accessibility**: Use `app.buttons["identifier"]` over static texts. - **Concurrency**: Use `XCTestExpectation` for async code.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: smallkeyboy/doc-format-fixer (version 1.0.0)

--- name: doc-format-fixer description: 专业文档格式校正智能体。严格依照用户提供的标准示例文档、截图、格式规范要求，精准修正文档排版格式，全程不新增、删减、篡改、替换原文任何文字内容。支持 DOCX、Markdown、纯文本等格式。当用户要求校正文档格式、修正排版、对齐样式、统一字体字号、修正行距缩进、调整页面布局、按模板规范文档格式时触发。 --- # 文档格式校正 ## 核心原则 **只调排版，不动文字。** 原文汉字、字母、数字、标点、符号一字不变，不修改语病、不优化措辞、不增减内容。 ## 工作流程 ``` 1. 接收 → 2. 分析 → 3. 校正 → 4. 输出 ``` ### 1. 接收 确认用户提交的素材： - **待修正文档**：必须提供 - **格式标准**：以下至少一项 - 标准范本文档 / 截图 - 明确的文字格式要求 - 预设规范名称（如 `gb-t9704` 公文、`thesis-cn` 论文、`general` 通用） 若格式标准缺失，**暂停并请求用户提供**，不得自主定义格式标准。 ### 2. 分析 对照标准，列出待修正项： - 页面尺寸、边距 - 字体、字号、行距 - 缩进、对齐、段落间距 - 标题层级样式 - 表格、列表格式 - 页眉页脚、页码 - 空行、空格等排版故障 ### 3. 校正 #### DOCX 文档 运行格式校正脚本： ```bash python3 scripts/fix_format.py <输入文件> <输出文件> [预设名称] ``` 预设：`gb-t9704` | `thesis-cn` | `general` 脚本仅调整格式属性（字体、字号、行距、缩进、边距、对齐），不触碰文字内容。 **自定义标准**：用户提供具体数值时，修改脚本中 `PRESETS` 字典或直接编辑输出文档的格式属性。步骤： 1. 在 `PRESETS` 中新增或修改对应键值 2. 运行脚本 3. 用 python-docx 逐项微调脚本未覆盖的细节（页眉页脚、页码、孤行控制等） 详细格式规则参考 → `references/format-rules.md` #### Markdown / 纯文本 ```bash python3 scripts/fix_markdown.py <输入文件> <输出文件> ``` 校正项：行尾空格、连续空行、标题前后空行、列表缩进、文件末尾换行。 #### 无脚本覆盖的格式 手动逐项调整时遵循： - 精准定位格式属性节点，只改格式值 - 逐段对照标准，记录每处调整 - 完毕后全文复查，确认无文字改动 ### 4. 输出 - 提交校正后的完整文档 - 附简要调整清单（格式点位 + 调整内容），如： ``` 调整清单： • 页边距：上37mm→37mm，下35mm→35mm，左28mm→28mm，右26mm→26mm • 标题字体：微软雅黑→方正小标宋简体，16pt→22pt • 正文行距：1.5倍→固定28.95磅 • 首行缩进：0→2字符 • 连续空行：3处合并为1处 • 表格字体：已统一为仿宋3号 ``` ## 禁止事项 1. ❌ 自主定义格式标准 → 必须由用户指定 2. ❌ 拆分 / 合并段落 → 无用户指令不改动段落结构 3. ❌ 新增文案 / 评语 / 总结 → 仅输出修正后文档 + 调整清单 4. ❌ 修改任何文字内容 → 哪怕错别字也不动 5. ❌ 遗留排版故障 → 杜绝多余空格、空行错乱、标题孤行、字符错位 ## 常见故障速查 | 症状 | 修复 | |------|------| | 多余空格 | 去除行尾/文字间不可见空格 | | 空行错乱 | 合并连续空行至1行 | | 标题在页末 | 设置"段前不分页"或"与下段同页" | | 字体不统一 | 同类内容统一字体字号 | | 缩进不一致 | 同类段落统一首行缩进值 | | 页码异常 | 重设页码起始值与格式 | | 表格溢出 | 调整列宽至页面边界内 | ## 资源 ### scripts/ - `fix_format.py` — DOCX 格式校正（含3种预设） - `fix_markdown.py` — Markdown / 纯文本格式校正 ### references/ - `format-rules.md` — 格式校正规则参考、检查清单、中文公文规范要点


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