SkillRadar README

The project's README from github.com/changchangidea-oss/SkillRadar. As one markdown file: README.md.

SkillRadar

Open-source discovery, security, ranking, and routing infrastructure for Agent Skills and Codex.

Release Daily Radar Router Benchmark Security Guard MIT Agent Skills Stars

SkillRadar overview

Give SkillRadar a coding task. It returns a small, safety-gated, evidence-backed set of Agent Skills instead of asking you to install an entire skill catalog.

SkillRadar discovers public SKILL.md files, parses their real contents, performs conservative static security checks, ranks candidates, bundles an offline registry, and routes tasks to relevant Skills without automatically executing untrusted third-party code.

Try it in 60 seconds

Codex Plugin

Install or verify the Codex CLI first:

command -v codex >/dev/null 2>&1 || npm install -g @openai/codex
codex --version

Then add the marketplace and install the plugin:

codex plugin marketplace add changchangidea-oss/SkillRadar --ref v0.5.0 && codex plugin add skillradar@skillradar

If your shell still says codex: command not found, restart the terminal and make sure your global npm binary directory is on PATH before retrying the plugin command.

Start a fresh Codex thread and run:

$skill-router
Find the best skills for a Next.js AI dashboard with tool calling and shadcn/ui.

A successful route should give you a small Top-3 result with auditable fields such as:

The installed plugin is offline-first and registry-first for explicit routing. Normal Top-3 routing does not require cloning this repository or fetching GitHub Raw.

Standard Agent Skill / skills.sh ecosystem

npx skills add changchangidea-oss/SkillRadar --skill skillradar

The standard Skill is intentionally read-first: discovery does not authorize third-party execution.

Local registry UI

git clone https://github.com/changchangidea-oss/SkillRadar.git
cd SkillRadar
npm run validate
npm run benchmark:router
npm run serve

Open http://localhost:4173.

Tried it? Tell us what happened

Real usage is more useful than synthetic demos.

Please remove tokens, credentials, private source code, and other sensitive data before posting.

Why SkillRadar exists

Installing hundreds of Skills is the wrong optimization. It increases context pressure, makes provenance harder to track, and turns task routing into guesswork.

SkillRadar takes the opposite approach:

What makes it different

Safety-gated discovery

Every discovered candidate passes through parsing and static security analysis. D/Blocked candidates remain audit-only and cannot enter the bundled routing shard.

Technology-specific evidence

Named technologies and services should be supported by specific evidence. Generic words such as workflow, integration, or data are not enough to justify a recommendation for a named tool or framework.

If the registry lacks a relevant capability, SkillRadar can expose that gap instead of filling Top-3 with unrelated Skills.

Offline-first explicit routing

The Codex plugin ships with a complete safety-gated core + design + general registry snapshot. Explicit routing can operate from the bundled registry without executing candidate repositories or depending on live GitHub discovery.

Auditable ranking

A route exposes relevance, SkillRadar score, security, provenance, reason, and match details so a recommendation can be inspected instead of treated as a black box.

Discovery coverage

SkillRadar combines the 12-field Design Radar with a General Agent Skills Radar across 10 domains:

AI Agents · Frontend · Backend & API · Data & Database · Testing & Quality · DevOps & Cloud · Security · Mobile · Automation & Integrations · Docs & Research.

General discovery combines multiple channels rather than relying on one repository query:

Candidates record discovery channels, coverage, domain evidence, quality, maintenance, popularity, security findings, and provenance.

Operational coverage is written to data/general-radar-latest.json; the auditable candidate pool is data/general-radar-registry.json.

Matching v2.1

Raw substring matching is not enough. Matching v2.1:

Project context is deliberately narrow: dependency names, common config filenames, and framework directories may be read. Source-file contents, environment-variable values, credentials, and candidate third-party scripts are not used for project-context routing.

If a C-grade Skill ranks first and an A/B candidate is within five match-score points, SkillRadar surfaces a safer-alternative advisory.

Router Quality Benchmark

The repository includes a golden benchmark so ranking changes have a measurable contract instead of relying on subjective spot checks.

The v0.5 baseline recorded:

The multi-capability AI Dashboard case is intentionally strict: the Top-3 must include nextjs, ai-sdk, and shadcn, proving that the reranker covers distinct explicit task facets instead of filling slots with generic near-matches.

Benchmark inputs live in data/router-benchmark.json; the latest auditable result is committed to data/router-benchmark-latest.json. CI and the release workflow enforce the benchmark. Weight changes remain code-reviewed and benchmark-gated.

Skill Budget Doctor

Current Codex has a finite model-visible Skill metadata budget; crowded catalogs can create context pressure. $manage-skills uses a read-only doctor instead of generic cleanup advice.

It inventories user, project, and enabled plugin Skills, estimates catalog pressure, detects near duplicates, uses current project/task relevance as a pruning signal, and generates:

It does not edit ~/.codex/config.toml, disable Skills, uninstall plugins, or execute discovered scripts without a later explicit approval.

Architecture

flowchart LR
  GH[Public GitHub repositories] --> DR[Design Radar]
  GH --> GR[General Radar]
  DR --> S[Parse + security scan]
  GR --> S
  S -->|A / B / C| R[Classify + rank]
  S -->|D / Blocked| A[Audit-only pool]
  R --> REG[(Safety-gated registry)]
  REG --> SNAP[(Bundled core + design + general snapshot)]
  SNAP --> M[Matching v2.1]
  M --> Q[Router Quality Benchmark]
  M --> CODEX[Codex $skill-router]
  CODEX --> T[Top-3 task match]
  CODEX --> B[Skill Budget Doctor]

Safety boundary

Discovery is not execution.

The scanner looks for high-risk patterns and capabilities including destructive shell commands, pipe-to-shell installs, remote shell use, dynamic execution, secret access, networking, package installation, filesystem writes, git writes, and deploy tooling.

Grades are conservative:

This is not a formal security audit or sandbox. The goal is to make risk visible before an agent installs or runs something.

Codex Plugin

The plugin lives in packages/codex-plugin/ and includes:

A repository-level Codex marketplace lives at .agents/plugins/marketplace.json, so Codex can install directly from GitHub. The plugin filters D/Blocked candidates again at runtime as defense in depth.

Repository map

SkillRadar/
├── .agents/plugins/marketplace.json
├── .github/ISSUE_TEMPLATE/
├── skills/skillradar/SKILL.md
├── data/
│   ├── skills.json
│   ├── design-skills-*.json
│   ├── general-domains.json
│   ├── general-skills-radar.json
│   ├── general-radar-registry.json
│   ├── general-radar-latest.json
│   ├── router-benchmark.json
│   └── router-benchmark-latest.json
├── packages/codex-plugin/
│   ├── data/registry.json
│   ├── scripts/skillradar.mjs
│   ├── scripts/skill-budget.mjs
│   └── skills/
├── docs/ADOPTION.md
├── scripts/
└── .github/workflows/

Open-source operating model

The repository intentionally keeps evidence in public Git history. Daily bots commit generated Radar data and refreshed bundled snapshots; benchmark and routing-quality evidence remain inspectable; CI verifies security patterns, registry integrity, project-context boundaries, plugin-only offline routing, Router Quality Benchmark behavior, Skill Budget Doctor behavior, and public marketplace installation.

We do not manufacture Stars, Forks, installs, contributor activity, testimonials, or feedback. See docs/ADOPTION.md for the evidence rules used by the project.

Public pages

Contributing

Code contributions and usage reports are both useful. See CONTRIBUTING.md.

Useful contributions include new public Skill sources, safety rules/fixtures, domain taxonomy improvements, ranking improvements, benchmark cases, OS compatibility tests, UI/metrics improvements, install reports, and real routing feedback.

Release

See v0.5.0 release notes.

License

MIT — see LICENSE.

SkillRadar (changchangidea-oss/SkillRadar)

Searching Database…

这是什么?SkillRadar 是面向 Agent Skills 和 Codex 的开源发现、安全、排序与路由基础设施:给它一个编程任务,它会返回一个精简、有安全把关、有依据支撑的相关技能 Top-3 集合,而不是让你安装整个技能目录。
这是 Codex 插件还是独立工具?它主要以 Codex 插件形式发布,带有四个命令(skill-router、find-skill、inspect-skill、manage-skills),但底层是一套完整的发现/排序引擎,自带注册表数据和路由基准,插件就构建在其之上。
怎么让 SkillRadar 在 Codex 里运行?先安装或确认 Codex CLI,然后添加 SkillRadar 市场并安装插件,再新开一个 Codex 会话运行任务;路由成功会返回 Top-3 结果,其中包含 matchscore、skillradarscore 和 security 等可审计字段。
除了 Codex CLI 还需要别的吗?你只需要 Codex CLI,并且 npm 的全局可执行文件目录在 PATH 中;已安装的插件离线优先、本地注册表优先,所以正常的 Top-3 路由不需要克隆仓库或访问 GitHub Raw。
它会真正运行或全面审计找到的技能吗?不会。发现明确不等于执行,所以它不会自动运行不受信任的第三方代码;它的静态风险分级(A 到 D/Blocked)也声明并非正式的安全审计或沙箱,只是在安装或运行之前提示风险的一种方式。
Skill Budget Doctor 是什么?它是 manage-skills 命令,一个只读的审计器:清点用户、项目和插件技能,估算技能目录对上下文的压力,检测近似重复项,并建议用来禁用冗余技能的配置片段——但它本身从不修改配置文件,也不禁用任何东西。
SkillRadar 的匹配为什么比普通关键词搜索更聪明?Matching v2.1 能识别概念和短语,避免短词的子串误配(比如 ai 误配到 tailwind),对身份/标签/领域/摘要赋予不同权重,并对 Top 3 做互补性重排,让结果覆盖任务的不同侧面,而不是近似重复的匹配。
有证据表明排序改动不会破坏结果吗?有。仓库自带带黄金路由用例的 Router Quality Benchmark;v0.5 基线 7/7 用例全部通过,Top-3 中零个 D/Blocked 结果,Top-1 平均匹配分 85.1,而且 CI 在每次变更时都强制执行该基准。
作者为什么要做这个,而不是直接安装一堆技能?安装成百上千个技能会加大上下文压力,让来源难以追踪,也让任务路由变成碰运气;因此 SkillRadar 保持发现覆盖面广泛,同时让真正加载进代理上下文的技能保持精简且有依据。
Size
8.6 MB
Stars
190
Age
1mo
Commits · 90 Days