zxhwolfe-dev/aiworkstation-open-source-intelligence

**One Skill. Nine live read-only Radar tools. Evidence-backed open-source AI research without a second server-side model call.**
简体中文 · Product page · AI Open Source Radar · Quickstart
AI Open Source Intelligence is the Skills/MCP product layer for **AI Open Source Radar**.
Production screenshot captured 2026-08-29. Rankings and project data update with Radar snapshots.
Product shape
The user does not choose separate research/comparison/stack Skills. The single Skill routes the task internally.
The **host model** performs natural-language reasoning and synthesis. The AI Workstation server provides data/evidence only on this product path.
One active Skill
It handles:
- browsing rankings, collections, categories, scenarios and the Radar Skills library;
- finding projects from deployment, privacy, integration, budget and license requirements;
- verifying named-project facts and license evidence;
- comparing two to five projects for a concrete use case;
- finding alternatives while preserving hard requirements;
- planning candidate open-source AI stacks and exposing unverified compatibility.
The only product Skill is packaged from:
agents/openai.yaml makes the Skill's dependency on the canonical
ai_open_source_intelligence Hosted MCP explicit while keeping automatic
invocation enabled. This is the Skill-level dependency contract; .mcp.json
is the matching Plugin-level connection contract.
The previous split research/comparison/stack Skill files are removed from the current product and distribution bundle.
Nine standard MCP tools
All nine are read-only. They do not execute or install third-party repository code.
No AI Workstation server-model execution
This is a hard product boundary for the current release.
The Hosted MCP exposes **no Premium model tool**, no checkout tool and no runtime OAuth/Premium switch. Requirement-based selection calls the public Radar selector with:
Therefore an ordinary Skill/MCP workflow is:
It is **not**:
If member-linked server-model capabilities are added later, they must ship as a new reviewed product version rather than being enabled through a hidden environment variable.
Evidence model
Every tool result separates:
1. **verified facts** — source-backed observations that crossed the evidence boundary;
2. **recommendations** — host-model/rules analysis;
3. **unknowns** — unavailable or unverified information;
4. **risks** — license, maintenance, deployment, security and integration limits.
A value in data is not automatically a verified fact. License evidence is deliberately stricter and is technical evidence, not legal advice.
Requirement tools publish the actual typed constraint contract through MCP:
Formal matches are revalidated against project-detail evidence. README excerpts
may directly verify narrow Docker, self-hosting, browser UI and low/no-code
claims; unresolved hard requirements become near-match blockers. A License label
is exposed only as observed_license_label until a direct LICENSE-family source
supports a verified license fact. Response observation time and evidence-source
freshness are reported separately.
Official resources in results
MCP tool results include canonical, non-tracking publisher links under: