Clawtrix Dev Intel
Finds the best ClawHub skills for developer-tooling agents. Personalized to your tech stack and mission — not a generic popularity list.
Quick Reference
| Task | Action |
|---|
| New agent onboarding | Run full discovery for the agent's stated tech stack |
| Weekly skill update |
Run Step 1 only — check for new releases on watched slugs |
| Specific capability gap | Run Step 2 with targeted search queries |
| Stack audit | Run full sequence, output to memory/ |
Discovery Run Sequence
Step 1 — Read Agent Mission
Read the agent's SOUL.md (or equivalent). Extract:
- - Primary language/stack (e.g., TypeScript, Python, Go, Rails)
- Dev workflows the agent runs (e.g., "reviews PRs", "runs tests", "writes CI pipelines")
- Current installed skills (to avoid re-recommending what's already there)
- Any explicit gaps ("I wish I could...")
Step 2 — Search ClawHub for Dev Tooling Skills
Query the ClawHub search API (clawhub.ai/api/v1/search) for each of these categories, substituting the agent's actual stack:
- - CI/CD skills — query: INLINECODE2
- Testing and coverage — query: INLINECODE3
- Code review automation — query: INLINECODE4
- Stack-specific — query:
{agent's primary stack} developer (e.g., typescript developer, python developer) - Git workflow — query: INLINECODE8
For each result, record: slug, displayName, score, updatedAt. Deduplicate across queries.
Step 3 — Score Each Candidate
Apply the Clawtrix scoring matrix (from clawtrix-scoring-engine):
| Dimension | Max | How to measure |
|---|
| Mission relevance | 3 | Does this directly support the agent's dev workflow? 3=core, 2=adjacent, 1=tangential |
| Gap fill |
2 | Does the agent lack this capability today? 2=yes, 1=partial, 0=no |
| Community signal | 1 | installs > 1,000 = +1 |
| Recency | 1 | Updated in last 30 days = +1 |
| Trust | 1 | No security flags, legitimate publisher = +1 |
Step 4 — Apply Dev-Specific Filters
Before recommending, verify:
- - [ ] Skill is compatible with the agent's primary language/framework
- [ ] No security flags (run against
clawtrix-security-audit pattern list) - [ ] Publisher has a credible track record (> 2 other published skills)
- [ ] Not already installed by this agent
Step 5 — Output Top 3
Never recommend more than 3. Write to memory/reports/dev-intel-YYYY-MM-DD.md:
CODEBLOCK0
Watched Skills
These are the highest-signal dev-tooling skills on ClawHub based on first intelligence run:
| Slug | What it does | Why it matters |
|---|
| INLINECODE16 | Captures learnings, errors, corrections | Continuous improvement loop for coding agents |
| INLINECODE17 |
Multi-agent task routing and handoffs | Essential for agents coordinating with Paperclip or other agents |
|
security-audit-toolkit | OWASP checks, codebase vulnerability scanning | Any agent touching production code needs this layer |
When to Use This for n8n Teams
For dev agents at companies already running n8n automation:
- - ClawHub skills for n8n workflow conversion exist and are a natural fit
- These teams already automate workflows — adding skill-based AI extends that investment seamlessly
Run Step 2 with n8n workflow as a search query to find current conversion options in ClawHub.
Upgrade Note — Clawtrix Pro
This skill surfaces dev-tooling recommendations on demand. Clawtrix Pro adds:
- - Proactive alerts when a high-signal dev skill ships or updates
- Cross-agent comparison ("your CTO agent has X but your dev agent doesn't")
- Weekly dev stack briefing with install/update diffs
Version History
v0.1.0 — Initial release. Stack-personalized discovery, 5-query search sequence, scoring matrix integration, n8n angle included.
v0.1.2 — 2026-04-02 — Replaced bash curl blocks in Step 2 with descriptive search instructions to resolve scanner flag.
v0.1.1 — Cleaned up internal research notes from n8n and watched-skills sections; now fully customer-facing.
Clawtrix Dev Intel
为开发者工具代理找到最佳的ClawHub技能。根据你的技术栈和任务进行个性化推荐——而非通用流行度列表。
快速参考
| 任务 | 操作 |
|---|
| 新代理入职 | 针对代理声明的技术栈运行完整发现流程 |
| 每周技能更新 |
仅运行步骤1——检查已关注slug的新版本 |
| 特定能力缺口 | 使用针对性搜索查询运行步骤2 |
| 技术栈审计 | 运行完整流程,输出至memory/ |
发现运行流程
步骤1 —— 读取代理任务
读取代理的SOUL.md(或等效文件)。提取:
- - 主要语言/技术栈(例如:TypeScript、Python、Go、Rails)
- 代理运行的开发工作流(例如:审查PR、运行测试、编写CI流水线)
- 当前已安装的技能(避免重复推荐已有内容)
- 任何明确缺口(我希望我能……)
步骤2 —— 在ClawHub搜索开发工具技能
针对以下每个类别查询ClawHub搜索API(clawhub.ai/api/v1/search),替换为代理的实际技术栈:
- - CI/CD技能 —— 查询:ci cd
- 测试与覆盖率 —— 查询:testing coverage
- 代码审查自动化 —— 查询:code review
- 技术栈特定 —— 查询:{代理的主要技术栈} developer(例如:typescript developer、python developer)
- Git工作流 —— 查询:git workflow
对每个结果,记录:slug、displayName、score、updatedAt。跨查询去重。
步骤3 —— 为每个候选技能评分
应用Clawtrix评分矩阵(来自clawtrix-scoring-engine):
| 维度 | 最高分 | 如何衡量 |
|---|
| 任务相关性 | 3 | 是否直接支持代理的开发工作流?3=核心,2=相邻,1=边缘 |
| 缺口填补 |
2 | 代理目前是否缺乏此能力?2=是,1=部分,0=否 |
| 社区信号 | 1 | 安装量 > 1,000 = +1 |
| 时效性 | 1 | 最近30天内更新 = +1 |
| 可信度 | 1 | 无安全标记,发布者合法 = +1 |
步骤4 —— 应用开发者特定过滤器
在推荐前,验证:
- - [ ] 技能与代理的主要语言/框架兼容
- [ ] 无安全标记(对照clawtrix-security-audit模式列表检查)
- [ ] 发布者有可信记录(已发布超过2个其他技能)
- [ ] 该代理尚未安装此技能
步骤5 —— 输出前3名
推荐数量不超过3个。写入memory/reports/dev-intel-YYYY-MM-DD.md:
markdown
Dev Intel — YYYY-MM-DD
代理:[名称]
技术栈:[语言/框架]
审计技能数:N个候选
前3名推荐
1. [作者/slug](评分:N/8)
- - 功能:[一句话描述]
- 为何适合此代理:[一句话关联SOUL.md]
- 安装:clawhub install [slug]
2. ...
3. ...
跳过项(及原因)
| Slug | 原因 |
|---|
| ... | 任务相关性低 / 安全标记 / 已安装 |
关注技能
基于首次情报运行,以下是ClawHub上信号最强的开发工具技能:
| Slug | 功能 | 重要性 |
|---|
| pskoett/self-improving-agent | 捕获学习、错误、修正 | 编码代理的持续改进循环 |
| agent-team-orchestration |
多代理任务路由与交接 | 代理与Paperclip或其他代理协调时必不可少 |
| security-audit-toolkit | OWASP检查、代码库漏洞扫描 | 任何接触生产代码的代理都需要这一层 |
何时为n8n团队使用此技能
对于已在运行n8n自动化的公司的开发代理:
- - 存在用于n8n工作流转换的ClawHub技能,且天然契合
- 这些团队已自动化工作流——添加基于技能的AI可无缝扩展该投资
使用n8n workflow作为搜索查询运行步骤2,以在ClawHub中找到当前可用的转换选项。
升级说明 —— Clawtrix Pro
此技能按需提供开发工具推荐。Clawtrix Pro新增:
- - 当高信号开发技能发布或更新时主动提醒
- 跨代理比较(你的CTO代理有X,但你的开发代理没有)
- 每周开发技术栈简报,含安装/更新差异
版本历史
v0.1.0 —— 初始版本。基于技术栈个性化的发现、5查询搜索序列、评分矩阵集成、包含n8n角度。
v0.1.2 —— 2026-04-02 —— 将步骤2中的bash curl代码块替换为描述性搜索指令,以解决扫描器标记。
v0.1.1 —— 清理了n8n和关注技能部分的内部研究笔记;现已完全面向客户。