OpenClaw/clawhub-security-signals huggingface dataset:
Skill: leooooooow/creator-cta-optimizer (version 1.0.0)

# Creator CTA Optimizer Improve weak, vague, or mistimed creator CTAs so the audience knows what to do next without the content feeling forced. Use this skill when a user has a script, post, or creator video concept that needs a stronger call to action. It is most useful for TikTok Shop, short-form UGC, creator ads, live commerce clips, founder videos, and conversion-oriented social content where the CTA needs to match audience intent and platform context. ## Problem it solves A lot of content loses conversion at the last moment because the CTA is too generic, too aggressive, too late, or mismatched to the audience stage. This skill helps adjust the CTA so it fits the content, the viewer’s readiness, and the platform behavior. ## Use when - A script ends weakly - The CTA sounds generic like “link in bio” or “buy now” with no nuance - You need different CTAs by funnel stage - A creator video needs softer, smarter conversion pressure - You want multiple CTA options to test ## Do not use when - The user needs a full script rather than CTA optimization - There is no defined goal for the viewer action - The content is purely informational with no next-step intent ## Inputs to ask for - Existing script, post, or video concept - Main goal: click, shop, DM, comment, follow, save, join live, etc. - Funnel stage: awareness, consideration, conversion, retention - Platform and format - Product or offer context - Tone preference: direct, soft, playful, urgent, community-led, proof-led ## Workflow 1. Diagnose why the current CTA underperforms 2. Identify the true audience intent and friction point 3. Match CTA style to the platform and funnel stage 4. Rewrite into multiple CTA variants with different pressure levels 5. Check that the CTA feels natural after the content body 6. Recommend the best variants to test first ## Output requirements Return: 1. Short diagnosis of the current CTA 2. 5-10 rewritten CTA options 3. CTA variants labeled by tone or use case 4. Best stage/use recommendation for each CTA 5. Suggested top 2-3 to test first 6. Optional CTA ladder for soft -> medium -> hard conversion pressure ## Quality standards - CTAs should sound like something a real creator would actually say - Variants must be meaningfully different, not tiny edits - CTA should fit the user’s actual goal and viewer readiness - Avoid robotic, pushy, or lazy CTA language - Recommendations should be immediately testable in content production ## Example prompts - Fix the CTA at the end of this TikTok Shop script - Give me better CTAs for a creator ad without sounding too salesy - Rewrite this weak call to action into softer and stronger variants


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

--- name: tripclaw description: 将 OpenClaw 生成的自驾行程导入到 TripClaw 应用。当用户说"导入行程到 TripClaw"、"同步到 TripClaw"、"发送到 TripClaw"、"推送到 TripClaw" 或提及 TripClaw 行程同步时触发。支持将行程数据（途经点、住宿、活动、预算等）通过 API 同步到用户的 TripClaw 账户。 --- # TripClaw 行程导入 将 OpenClaw 生成的自驾行程同步到 TripClaw 应用。 ## 快速开始 ### 1. 配置 API Key 用户需要先配置 TripClaw API Key： ```bash # 设置环境变量（推荐） export TRIPCLAW_API_KEY="your-api-key-here" # 或在 OpenClaw 配置中添加 ``` ⚠️ **安全提醒**：API Key 是敏感信息，请勿分享、勿提交到公开仓库、勿在截图或录屏中暴露。 ### 2. 触发方式 用户说以下任一指令时触发： - "导入行程到 TripClaw" - "同步到 TripClaw" - "发送到 TripClaw" - "把行程推送到 TripClaw" ## 行程数据结构 TripClaw 接受以下 JSON 格式的行程数据： ```json { "name": "行程名称", "description": "行程描述（可选）", "startDate": "2024-01-15", "endDate": "2024-01-22", "travelers": 2, "waypoints": [ { "order": 1, "name": "地点名称", "type": "start|waypoint|destination", "location": { "address": "详细地址", "coordinates": { "lat": 25.0389, "lng": 102.7183 } }, "arrivalDate": "2024-01-15", "stay": { "accommodation": "住宿名称", "nights": 1, "bookingUrl": "预订链接（可选）" } } ], "activities": [ { "date": "2024-01-16", "name": "活动名称", "description": "活动描述", "location": { "address": "活动地点", "coordinates": { "lat": 0, "lng": 0 } }, "duration": "2小时", "cost": 100 } ], "budget": { "total": 15000, "currency": "CNY" } } ``` ### 字段说明 | 字段 | 必填 | 说明 | |------|------|------| | name | ✅ | 行程名称 | | description | ❌ | 行程描述 | | startDate | ✅ | 开始日期 (YYYY-MM-DD) | | endDate | ✅ | 结束日期 (YYYY-MM-DD) | | travelers | ❌ | 出行人数，默认 1 | | waypoints | ✅ | 途经点数组，至少 1 个 | | activities | ❌ | 活动安排数组 | | budget | ❌ | 预算信息 | ### Waypoint 类型 - `start` - 出发点 - `waypoint` - 中途经停点 - `destination` - 最终目的地 ## 使用流程 1. **检测意图**：用户表达导入/同步行程到 TripClaw 的意图 2. **收集数据**：从当前对话或用户提供的行程信息中提取数据 3. **构建结构**：按照上述 JSON 结构组织行程数据 4. **调用 API**：使用 `scripts/import_trip.py` 发送到 TripClaw 5. **反馈结果**：告知用户导入成功或失败原因 ## 执行导入 使用脚本执行实际导入： ```bash python3 scripts/import_trip.py --api-key "$TRIPCLAW_API_KEY" --data '<trip-json-data>' ``` 或传入文件： ```bash python3 scripts/import_trip.py --api-key "$TRIPCLAW_API_KEY" --file trip.json ``` ## API 参考 详细的 API 文档请参阅 [references/api.md](references/api.md)。 ## 错误处理 | 错误码 | 说明 | 处理建议 | |--------|------|----------| | 401 | API Key 无效或过期 | 检查 TRIPCLAW_API_KEY 配置 | | 400 | 数据格式错误 | 检查 JSON 结构是否符合规范 | | 404 | 用户不存在 | 确认 API Key 对应的账户状态 | | 429 | 请求过于频繁 | 稍后重试 | | 500 | 服务器错误 | 联系 TripClaw 支持 | ## 隐私与安全 - API Key 仅存储在用户本地环境 - 行程数据通过 HTTPS 加密传输 - 不会记录或缓存敏感数据


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

--- name: pm2 description: Manage Node.js applications with PM2 process manager. Use for deploying, monitoring, and auto-restarting Node apps in production. Covers starting apps, viewing logs, setting up auto-start on boot, and managing multiple processes. --- # PM2 Process Manager Production process manager for Node.js with built-in load balancer. ## Install ```bash npm install -g pm2 ``` ## Quick Start ```bash # Start an app pm2 start app.js pm2 start npm --name "my-app" -- start pm2 start "npm run start" --name my-app # With specific port/env pm2 start npm --name "my-app" -- start -- --port 3000 PORT=3000 pm2 start npm --name "my-app" -- start ``` ## Common Commands ```bash # List processes pm2 list pm2 ls # Logs pm2 logs # All logs pm2 logs my-app # Specific app pm2 logs --lines 100 # Last 100 lines # Control pm2 restart my-app pm2 stop my-app pm2 delete my-app pm2 reload my-app # Zero-downtime reload # Info pm2 show my-app pm2 monit # Real-time monitor ``` ## Auto-Start on Boot ```bash # Save current process list pm2 save # Generate startup script (run the output command with sudo) pm2 startup # Example output - run this: # sudo env PATH=$PATH:/opt/homebrew/bin pm2 startup launchd -u username --hp /Users/username ``` ## Next.js / Production Builds ```bash # Build first npm run build # Start production server pm2 start npm --name "my-app" -- start # Or with ecosystem file pm2 start ecosystem.config.js ``` ## Ecosystem File (ecosystem.config.js) ```javascript module.exports = { apps: [{ name: 'my-app', script: 'npm', args: 'start', cwd: '/path/to/app', env: { NODE_ENV: 'production', PORT: 3000 } }] } ``` ## Useful Flags | Flag | Description | |------|-------------| | `--name` | Process name | | `--watch` | Restart on file changes | | `-i max` | Cluster mode (all CPUs) | | `--max-memory-restart 200M` | Auto-restart on memory limit | | `--cron "0 * * * *"` | Scheduled restart | ## Cleanup ```bash pm2 delete all # Remove all processes pm2 kill # Kill PM2 daemon pm2 unstartup # Remove startup script ```


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

--- name: COO / Chief Operations Officer slug: coo version: 1.0.2 homepage: https://clawic.com/skills/coo changelog: "Updated name format, optimized description, added Related Skills and Feedback" description: Be the COO with process design, organizational scaling, cross-functional execution, and operational excellence. metadata: {"clawdbot":{"emoji":"⚡","requires":{"bins":[]},"os":["linux","darwin","win32"]}} --- ## When to Use Agent needs to be the COO: process design, organizational scaling, cross-functional execution, vendor management, crisis management, or operational metrics. ## Quick Reference | Domain | File | |--------|------| | Process design and optimization | `process.md` | | Organizational scaling | `scaling.md` | | Cross-functional execution | `execution.md` | | Operational metrics | `metrics.md` | ## Core Rules 1. **Systems over heroics** — Repeatable beats exceptional one-offs 2. **Standardize before scaling** — Chaos multiplies with growth 3. **Remove before automating** — Don't automate waste 4. **Hire ahead of breaking** — Scrambling costs more than planning 5. **One owner per outcome** — Shared accountability is no accountability 6. **Decide at lowest level** — Don't bottleneck at the top 7. **Process serves people** — Bureaucracy kills speed ## By Company Stage | Stage | COO Focus | |-------|-----------| | **Pre-PMF** | Minimal process, founder-driven, stay flexible | | **Seed** | Document what works, first operational hires | | **Series A** | Repeatable processes, team leads, basic metrics | | **Series B+** | Operational excellence, managers of managers, optimization | ## Decision Checklist Before major operational changes: - Company stage? (startup chaos, growth scaling, mature optimization) - Team size? (breaking points at 10, 30, 100, 300) - Current bottlenecks? (people, process, tools) - Cross-functional dependencies? (who blocks whom) - Measurement baseline? (can't improve what you can't see) ## Common Traps | Trap | Consequence | |------|-------------| | Process before problem | Bureaucracy without value | | Scaling without standards | Chaos multiplies | | Automating waste | Faster bad outcomes | | Hero culture dependency | Single points of failure | | Top-down bottlenecks | Slow decisions, disempowered teams | ## Security & Privacy This skill provides strategic guidance only. **Data handling:** - No external API calls - No data leaves your machine - No persistent storage required ## Human-in-the-Loop Escalate to human for: - Organizational restructures - Major vendor commitments - Headcount planning - Process changes affecting culture - Crisis response decisions - Cross-functional conflict resolution ## Related Skills Install with `clawhub install <slug>` if user confirms: - `ceo` — executive strategy and board management - `cfo` — financial modeling and capital allocation - `cto` — technical strategy and architecture - `business` — strategy validation and planning ## Feedback - If useful: `clawhub star coo` - Stay updated: `clawhub sync`


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: jhillin8/morning-routine (version 1.0.0)

--- name: morning-routine description: Build a powerful morning routine with habit checklists, timing, and streak tracking author: clawd-team version: 1.0.0 triggers: - "morning routine" - "start my day" - "morning checklist" - "wake up routine" - "morning habits" --- # Morning Routine Win your morning, win your day. ## What it does The Morning Routine skill transforms your first hours into a structured, trackable system that compounds over time. - **Habit Checklists**: Define your core morning habits and check them off as you complete them - **Timing Tracking**: See how long each habit takes and when you typically finish your routine - **Streak Tracking**: Build momentum with daily streak counts—watch your consistency grow - **Adaptation Suggestions**: Get insights on which habits stick and which ones need adjustment based on your data ## Usage **Start routine** ``` "start my morning routine" "begin my routine" "morning routine go" ``` Launches your checklist. Clawd guides you through each habit with timing reminders. **Check off habit** ``` "I did meditation" "hydration complete" "movement done" "planning finished" ``` Mark individual habits as complete. Clawd tracks completion time and logs the action. **Routine status** ``` "how's my routine" "what's left" "routine progress" "show me what's next" ``` Get a real-time snapshot of your current routine—how many habits done, how many remaining. **Modify routine** ``` "add yoga to my routine" "remove morning news" "change routine" "swap habit" ``` Customize habits on the fly. Clawd saves changes and adapts your checklist immediately. **Review streak** ``` "show my streak" "how many days" "consistency report" "routine history" ``` See your current streak, longest streak, and consistency metrics over time. ## Common Elements Most powerful morning routines include these components: - **Wake time**: Consistent wake time creates a foundation for everything else - **Hydration**: Glass of water first thing activates your system - **Movement**: 10-20 mins of stretching, walking, or exercise - **Mindfulness**: Meditation, journaling, or breathing practice - **Planning**: Review your day and set 3 key priorities - **No phone**: Keep your phone off until after your core routine Build your routine from these blocks. Start with 2-3 habits. Add more as they stick. ## Tips - **Consistency matters more than perfection.** 5 days of 80% routine beats 2 days of 100%. Streaks are built on showing up, not perfection. - **Stack habits together.** Brush teeth → drink water → meditate creates a trigger chain. Each habit pulls the next one. - **Time your routine.** Know how long it actually takes. Build buffer time so you're not rushed—rushed mornings cascade into rushed days. - **Review weekly, not daily.** Check your streaks and adaptation data once per week. Daily obsessing kills momentum. - **All data stays local on your machine.** Your routine data never leaves your device. No cloud sync, no tracking, no third parties—just you and your habits.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: tianjin-ren/security-audit-tianjin (version 1.0.1)

--- name: security-audit description: Comprehensive security auditing for Clawdbot deployments. Scans for exposed credentials, open ports, weak configs, and vulnerabilities. Auto-fix mode included. --- # Security Audit Skill ## When to use Run a security audit to identify vulnerabilities in your Clawdbot setup before deployment or on a schedule. Use auto-fix to remediate common issues automatically. ## Setup No external dependencies required. Uses native system tools where available. ## How to ### Quick audit (common issues) ```bash node skills/security-audit/scripts/audit.cjs ``` ### Full audit (comprehensive scan) ```bash node skills/security-audit/scripts/audit.cjs --full ``` ### Auto-fix common issues ```bash node skills/security-audit/scripts/audit.cjs --fix ``` ### Audit specific areas ```bash node skills/security-audit/scripts/audit.cjs --credentials # Check for exposed API keys node skills/security-audit/scripts/audit.cjs --ports # Scan for open ports node skills/security-audit/scripts/audit.cjs --configs # Validate configuration node skills/security-audit/scripts/audit.cjs --permissions # Check file permissions node skills/security-audit/scripts/audit.cjs --docker # Docker security checks ``` ### Generate report ```bash node skills/security-audit/scripts/audit.cjs --full --json > audit-report.json ``` ## Output The audit produces a report with: | Level | Description | |-------|-------------| | 🔴 CRITICAL | Immediate action required (exposed credentials) | | 🟠 HIGH | Significant risk, fix soon | | 🟡 MEDIUM | Moderate concern | | 🟢 INFO | FYI, no action needed | ## Checks Performed ### Credentials - API keys in environment files - Tokens in command history - Hardcoded secrets in code - Weak password patterns ### Ports - Unexpected open ports - Services exposed to internet - Missing firewall rules ### Configs - Missing rate limiting - Disabled authentication - Default credentials - Open CORS policies ### Files - World-readable files - Executable by anyone - Sensitive files in public dirs ### Docker - Privileged containers - Missing resource limits - Root user in container ## Auto-Fix The `--fix` option automatically: - Sets restrictive file permissions (600 on .env) - Secures sensitive configuration files - Creates .gitignore if missing - Enables basic security headers ## Related skills - `security-monitor` - Real-time monitoring (available separately)


Security scan verdicts — ClawScan: clean | static analysis: suspicious | VirusTotal: clean | SkillSpector: suspicious (HIGH)
Skill: wangxiaofei860208-source/agentic-engineering-bak (version 1.0.0)

--- name: agentic-engineering description: Operate as an agentic engineer using eval-first execution, decomposition, and cost-aware model routing. origin: ECC --- # Agentic Engineering Use this skill for engineering workflows where AI agents perform most implementation work and humans enforce quality and risk controls. ## Operating Principles 1. Define completion criteria before execution. 2. Decompose work into agent-sized units. 3. Route model tiers by task complexity. 4. Measure with evals and regression checks. ## Eval-First Loop 1. Define capability eval and regression eval. 2. Run baseline and capture failure signatures. 3. Execute implementation. 4. Re-run evals and compare deltas. ## Task Decomposition Apply the 15-minute unit rule: - each unit should be independently verifiable - each unit should have a single dominant risk - each unit should expose a clear done condition ## Model Routing - Haiku: classification, boilerplate transforms, narrow edits - Sonnet: implementation and refactors - Opus: architecture, root-cause analysis, multi-file invariants ## Session Strategy - Continue session for closely-coupled units. - Start fresh session after major phase transitions. - Compact after milestone completion, not during active debugging. ## Review Focus for AI-Generated Code Prioritize: - invariants and edge cases - error boundaries - security and auth assumptions - hidden coupling and rollout risk Do not waste review cycles on style-only disagreements when automated format/lint already enforce style. ## Cost Discipline Track per task: - model - token estimate - retries - wall-clock time - success/failure Escalate model tier only when lower tier fails with a clear reasoning gap.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: wanglingchao-2025/my-weather-helper (version 1.0.1)

# 技能：天气助手 (Weather Helper) ## 触发条件 - 当用户询问“天气”、“气温”或“穿衣建议”时触发。 ## 工作流程 1. **获取位置**：如果用户没有说明城市，请礼貌地询问。 2. **执行搜索**：使用内置的搜索工具（如 Google Search）查询该城市的实时天气。 3. **整理输出**：按照以下格式回复： - 🌡️ **实时气温**：[数值] - ☁️ **天气状况**：[晴/雨/阴] - 🧥 **穿衣建议**：[根据气温给出的建议] ## 注意事项 - 严禁编造天气数据，必须以搜索结果为准。 - 如果搜索失败，请告知用户手动检查。

path: plugin.json
content: {
  "name": "my-weather-helper",
  "version": "1.0.0",
  "description": "一个简单的天气查询辅助技能",
  "author": "你的名字",
  "skills": [
    {
      "action": "query_weather",
      "description": "当用户询问天气时，引导用户提供城市名并调用搜索工具"
    }
  ]
}

Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: tangsuann/etf-trading-backtest (version 1.0.0)

--- name: etf-trading-backtest description: ETF模拟交易回测系统。支持A股ETF日内交易策略的模拟交易与回测分析，包括BOLL、MACD、KDJ等技术指标组合判断，自动计算手续费、止损止盈、风险指标（最大回撤、夏普比率等）。适用于船舶ETF(560710)等标的的量化交易回测。当用户提及：ETF模拟交易、股票回测、量化交易策略回测、技术指标交易、回测分析、560710交易时触发此skill。 --- # ETF模拟交易回测系统 ## 简介 本Skill提供ETF/股票模拟交易和回测分析功能，基于技术指标（BOLL、MACD、KDJ）判断买卖信号，支持自动计算手续费、止损止盈、风险指标统计。 ## 核心功能 1. **实时模拟交易** - 根据技术指标信号执行模拟买入/卖出 2. **回测分析** - 基于历史数据回测策略表现 3. **风险指标计算** - 最大回撤、夏普比率、卡玛比率等 4. **报告生成** - 自动生成交易报告和复盘分析 ## 交易标的 默认标的：**560710 富国中证智选船舶产业ETF** 可扩展到其他ETF/股票。 ## 交易规则 | 规则 | 说明 | |------|------| | **交易时间** | 工作日9:30-15:00 | | **交易频率** | 每天最多1次操作 | | **T+1规则** | 当日买入，次日才能卖出 | | **手续费** | 买入0.025% + 卖出0.025% + 印花税0.1% | | **初始资金** | 100万（模拟） | | **止损线** | -5% | | **止盈线** | +8% | ## 买卖信号 ### 买入信号 | 信号类型 | 条件 | 优先级 | |----------|------|--------| | **BOLL下轨+KDJ超卖** | 价格触及BOLL下轨 + KDJ的J<20 | 高 | | **突破中轨+放量** | 价格突破BOLL中轨 + 成交量放大>1.5倍 | 高 | | **MACD底背离** | 价格创新低，MACD未创新低 | 中 | ### 卖出信号 | 信号类型 | 条件 | 优先级 | |----------|------|--------| | **BOLL上轨+KDJ超买** | 价格触及BOLL上轨 + KDJ的J>80 | 高 | | **死叉** | MACD死叉 + KDJ死叉 | 高 | | **止损** | 亏损达到-5% | 强制 | | **止盈** | 盈利达到+8% | 可选 | ## 风险指标 | 指标 | 说明 | 理想值 | |------|------|--------| | **总收益率** | 最终收益/初始资金 | 越高越好 | | **年化收益率** | 年化后的收益率 | >15% | | **胜率** | 盈利交易占比 | >50% | | **盈亏比** | 平均盈利/平均亏损 | >1.5 | | **最大回撤** | 从最高点到最低点的跌幅 | <15% | | **夏普比率** | 风险调整后收益 | >1.0 | | **卡玛比率** | 收益/最大回撤 | >1.5 | ## 使用方式 ### 1. 触发方式 当用户提及以下关键词时自动触发： - "ETF模拟交易" - "股票回测" - "量化交易策略回测" - "技术指标交易" - "回测分析" - "560710交易" - "船舶ETF" ### 2. 执行流程 ``` 1. 获取实时/历史行情数据 2. 计算BOLL、MACD、KDJ指标 3. 判断买卖信号 4. 执行模拟交易（如触发信号） 5. 记录交易日志 6. 计算风险指标 7. 生成报告 ``` ### 3. 定时任务（可选） 可通过Cron设置每日定时执行： - 9:30 开盘分析 - 14:50 尾盘确认 - 15:00 收盘复盘 ## 脚本说明 ### scripts/trade.py 主交易脚本，包含： - `get_realtime_data()` - 获取实时行情 - `calculate_indicators()` - 计算技术指标 - `generate_signals()` - 生成买卖信号 - `execute_trade()` - 执行模拟交易 - `calculate_metrics()` - 计算风险指标 ### references/rules.md 详细交易规则和参数配置。 ## 输出格式 ### 交易报告 ```markdown ## 📊 日内交易报告 ### 交易概要 - **日期**：2026-03-17 - **操作**：买入 - **信号强度**：⭐⭐ ### 盈亏情况 - **当前持仓**：10000份 - **持仓盈亏**：+500元 (+0.5%) ``` ### 回测报告 ```markdown ## 📈 回测报告 ### 基础统计 - 总收益率：+15.84% - 年化收益率：+42.35% - 胜率：64.29% ### 风险指标 - 最大回撤：-8.42% - 夏普比率：1.56 - 卡玛比率：5.02 ``` ## 注意事项 1. 模拟交易仅供学习参考，不构成投资建议 2. 技术指标可能失效，需结合市场环境判断 3. 严格执行止损纪律 4. 建议先在模拟环境测试 ## 扩展定制 如需修改默认参数，可编辑： - 交易标的代码 - 初始资金 - 手续费率 - 止损止盈线 - 技术指标参数 --- *版本: 1.0.0* *创建日期: 2026-03-17*


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

--- name: "cnc" version: "1.0.0" description: "CNC machining program manager" author: "BytesAgain" homepage: "https://bytesagain.com" source: "https://github.com/bytesagain/ai-skills" tags: [cnc, industrial, cli, tool] category: "industrial" --- # cnc CNC machining program manager ## Commands ### `status` ```bash scripts/script.sh status ``` Show current status ### `add` ```bash scripts/script.sh add ``` Add new entry ### `list` ```bash scripts/script.sh list ``` List all entries ### `search` ```bash scripts/script.sh search ``` Search entries ### `remove` ```bash scripts/script.sh remove ``` Remove entry by number ### `export` ```bash scripts/script.sh export ``` Export data to file ### `stats` ```bash scripts/script.sh stats ``` Show statistics ### `config` ```bash scripts/script.sh config ``` View or set config ### `help` ```bash scripts/script.sh help ``` ### `version` ```bash scripts/script.sh version ``` ## Configuration Use `scripts/script.sh config <key> <value>` to set preferences. | Variable | Required | Description | |----------|----------|-------------| | `CNC_DIR` | No | Data directory (default: ~/.cnc/) | ## Data Storage All data stored in `~/.cnc/` using JSONL format (one JSON object per line). ## Output Structured output to stdout. Exit code 0 on success, 1 on error. --- *Powered by BytesAgain | bytesagain.com | [REDACTED_SECRET]*


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