ai-runtime-toolkit
AI Runtime工具装备系统,支持8个内部专业工具和10+个外部CLI工具的整合管理,提供工具发现、执行和配置功能,遵循整合优于创造的设计理念
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 6
- Forks
- 0
01 前言 Front Matter
- name
- ai-runtime-toolkit
- license
- MIT
- version
- 2.0.0
- description
- AI Runtime工具装备系统,支持8个内部专业工具和10+个外部CLI工具的整合管理,提供工具发现、执行和配置功能,遵循整合优于创造的设计理念
02 资源文件 5
- 脚本discover-toolkit.py1.6 KB
- 参考文档EXTERNAL-TOOLS-SKILL.md3.8 KB
- 参考文档EXTERNAL-TOOLS.md2.0 KB
- 参考文档registry.md2.4 KB
- 参考文档skill-report.json321.8 KB
03 SKILL.md 正文
AI Runtime 工具装备系统
概述
工具装备是AI Runtime的外置能力扩展系统,遵循"整合 > 创造"的核心理念,通过智能整合成熟的CLI工具和自主创建的专业工具,实现认知能力的有效扩展。
核心能力
双重工具体系
- 内部工具: AI Runtime自主创建的专业工具(8个)
- 外部工具: 深度整合的成熟CLI工具(10+个)
智能发现系统
- 自动工具检测和注册
- 元数据驱动的管理机制
- 命令行和编程接口双重支持
快速开始
查看所有工具
# 进入工具装备目录
cd toolkit
# 查看所有工具
python3 discover-toolkit.py list
# 查看外部工具
python3 discover-toolkit.py list --external
使用工具
# 查看工具详情
python3 discover-toolkit.py show SERVICE-CHECK-001
# 运行工具
python3 discover-toolkit.py run dependency-analyzer . -o deps.json
# 搜索工具
python3 discover-toolkit.py search monitor
工具分类
内部工具(自主创建)
- Python工具: 依赖分析器、代码统计器、图形生成器、报告生成器
- Bash工具: 服务健康检查器、日志分析器、磁盘健康检查器
- Node.js工具: API测试工具
外部工具(深度整合)
- 基础必备: fzf、eza、bat、ripgrep、zoxide、jq
- 搜索增强: fd、ripgrep
- 数据处理: jq
- 界面优化: fzf、eza、bat、starship
渐进式披露文档架构
基于 anthropics/skills 设计,按需加载详细信息:
核心理念
- 工具哲学 - 设计理念、分类体系和发展策略
使用指南
- 快速开始 - 10分钟上手工具装备系统
详细参考
开发指南
设计理念
整合优于创造
- 成熟工具: 使用经过社区验证的CLI工具
- 专注专业: 每个工具只做一件事,做到极致
- 认知卸载: 直接使用,无需重复开发
元数据驱动
- .meta.yml: 工具元数据标准格式
- 自动发现: 基于文件系统结构自动注册
- 类型安全: 明确的工具分类和版本管理
使用场景
代码分析
# 分析项目依赖
python3 discover-toolkit.py run dependency-analyzer . -o deps.json
# 生成代码统计
python3 discover-toolkit.py run code-stats src/ -o stats.json
系统监控
# 检查服务健康
python3 discover-toolkit.py run service-check http://localhost:3000
# 分析日志文件
python3 discover-toolkit.py run log-analyzer /var/log/app.log --level ERROR
数据处理
# 处理JSON数据
cat data.json | jq '.items[] | select(.status == "active")'
# 搜索代码
rg "TODO|FIXME" src/
相关系统
版本信息
- 版本: 2.0.0
- 内部工具: 8个
- 外部工具: 10+个
- 最后更新: 2025-11-14
基于 anthropics/skills 渐进式披露架构设计
04 同仓库更多 Skills
serpmaven
Scrape Google search results (SERP) to JSON with SERP Maven (serpmaven) - a real Chrome browser on a residential proxy with sticky sessions. Run it as a CLI, a Python library, a local HTTP search API (`serve`), an MCP server or a Docker image; set the proxy login, workers, pages and cost tracking. Use when the user wants Google results, rank tracking, a self-hosted SERP API, or live Google search for an AI agent.
revnu-landing-page-audit
Find out why a landing page isn't turning visitors into signups, demos or sales. Audits one page against what the ad, post or search that sends people there promised, then checks the first screen, proof, call to action, friction and mobile. Returns at most 7 prioritized fixes, plus what is fine and what could not be checked; rewrites specific lines and fixes the page in the repo when asked. Never promises a conversion lift. Works without a Revnu account. Use when the user says or asks: "audit my landing page", "why isn't this page converting", "review my homepage", "my ads get clicks but no signups", "people bounce from the pricing page", "CRO review", "improve conversion rate", "is my hero section clear", "roast my landing page", "rewrite my headline", "what's wrong with this page", "landing page feedback", "make the signup page convert better". Not for SEO or AI-search audits, page speed engineering on its own, or building a new page from scratch.
revnu-growth-context
Write down once who buys, what they're stuck on, what it costs, what proof you have and what you've already tried, so every growth task starts from facts instead of a questionnaire. Creates or updates .agents/revnu-growth.md from the repo, the live site and the user, and imports an existing product-marketing.md. Use when the user says "set up our marketing context", "who is our ideal customer", "write our ICP", "describe the product for marketing", "positioning doc", "what's our brand voice", "remember this about our customers", "log what we tried", "what have we learned from marketing", "we changed pricing, update the context", "update our growth notes", "summarize the business for the agent", "import my product-marketing.md", "start a growth doc", or before a first marketing, SEO, outreach or launch task when no context file exists. Works without a Revnu account.
revnu-get-listed
Get onto the third-party pages AI answers and search cite when buyers ask for the best tool in your category: "best X" roundups, directories, review sites, GitHub awesome lists, community threads and comparison pages. Finds which ones are cited, ranks them by fit and effort, and drafts each submission, PR or pitch by the target's own rules. Use when the user says "get us listed", "which directories should we submit to", "how do we get into best-of lists", "why does ChatGPT recommend competitors and not us", "get mentioned in AI answers", "submit to awesome lists", "get on G2", "where are our competitors listed", "pitch listicle authors", "find backlink opportunities", "launch directories", "get into roundups", "Product Hunt alternatives", "where should we be listed", "get cited by Perplexity". Never submits, pays or posts without a yes. Works without a Revnu account.
revnu-ai-readiness-audit
Audit whether your website gives ChatGPT, Perplexity, Claude, Gemini and Google's AI Overviews something worth quoting, and fix the pages that don't. Use when the user says or asks "is my site ready for AI search", "audit my site for AI answers", "AEO audit", "GEO audit", "why doesn't ChatGPT quote our pricing", "make our pages citable by AI", "do I need llms.txt", "does schema help with ChatGPT", "check our structured data", "is our content visible without JavaScript", "AI SEO audit", "optimize our homepage for AI answers", "LLM SEO check", "why does AI get our product wrong", "fix our site for AI Overviews". Checks fetchability and indexability, answers in the raw HTML, entity facts, schema (including JS-injected markup), headings, dates and llms.txt, then gives at most 10 prioritised fixes and edits the repo when asked. Works without a Revnu account.
proxy-troubleshooting
Diagnose residential proxy failures, with NodeMaven's gateway as the reference - 407 with correct credentials, 406, 410, 500, a connection that hangs, ERR_TUNNEL_CONNECTION_FAILED in a browser, Playwright or Puppeteer ignoring proxy credentials, a sticky session that changes IP, geo-targeting that is silently ignored, passwords with special characters, and unexpected traffic from headless Chrome. Use when a proxy connection fails, returns the wrong location, or costs more traffic than expected.