tech-radar

A four-level framework for recording how suitable different technologies are for a team: Adopt, Trial, Assess, or Hold. A technology can be a programming language, framework, library, or other tool.

In plain words
What is it for?
Evaluating new technologies, planning migrations, reviewing the current stack, and recording whether a technology is ready for production use.
Why use it?
It gives teams a shared way to judge maturity, community support, performance, ecosystem fit, and risk instead of choosing tools informally.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/saolalab/clawforce/tech-radar
Any agent
npx skills add saolalab/clawforce --skill tech-radar
Clone the repo
git clone --depth 1 https://github.com/saolalab/clawforce

Made for: Claude Code, Codex.

Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 668 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00033 $0.00668
Opus 5 $0.00016 $0.00334
Sonnet 5 $0.00007 $0.00134
Haiku 4.5 $0.00003 $0.00067

Measured 3d ago against content hash a8e2983f41eb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

tech-radar scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

marketplace/roles/cto/workspace/skills/tech-radar/SKILL.md · 111 lines

How it starts

The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Tech Radar

The Tech Radar organizes technologies into four rings based on adoption status:

Four Rings

Adopt

Technologies we use in production and recommend for new projects.

Criteria:

  • Proven in production at scale
  • Well-documented and maintained
  • Team has expertise
  • Low risk, high value

Trial

Technologies we're experimenting with in non-critical projects.

Criteria:

  • Promising but not yet proven
  • Limited production experience
  • Evaluating fit for our use case
  • Small risk, potential high value

Assess

Technologies worth exploring to understand potential value.

Criteria:

  • Emerging or interesting
  • Not yet evaluated
  • May solve future problems
  • Unknown risk/value

Hold

Technologies we've decided not to adopt or are phasing out.

Criteria:

  • Doesn't fit our needs
  • Better alternatives exist
  • Deprecated or unmaintained
  • High risk or low value

Evaluation Criteria

When assessing a new technology, evaluate:

  1. Maturity — How long has it been around? Production-ready?
  2. Community — Active maintainers? Good documentation? Stack Overflow presence?
  3. Performance — Meets our performance requirements?
  4. Ecosystem — Integrations, libraries, tooling available?
  5. Learning Curve — How long to become productive?
  6. Vendor Lock-in — Open source or proprietary? Portable?
  7. Cost — Licensing, infrastructure, operational costs?
  8. Security — Security track record? Regular updates?
  9. Team Fit — Does the team have skills? Can we hire for it?

Tech Radar Template

# Tech Radar — {Quarter} {Year}

## Adopt
- {Technology} — {Brief reason}

## Trial
- {Technology} — {Brief reason, project using it}

## Assess
- {Technology} — {Brief reason, what we're exploring}

## Hold
- {Technology} — {Brief reason, migration plan if applicable}

Migration Planning Template

When moving from Hold to Adopt (or adopting a replacement):

# Migration Plan: {From Technology} → {To Technology}

## Current State
- **Usage**: {Where is it used?}
- **Dependencies**: {What depends on it?}
- **Risk**: {What breaks if we don't migrate?}

## Target State
- **Timeline**: {Target completion date}
- **Approach**: {Big bang | Gradual | Strangler pattern}
- **Success Criteria**: {How do we know it's done?}

## Migration Steps
1. {Step 1}
2. {Step 2}
3. {Step 3}

## Rollback Plan
{What if migration fails?}

## Timeline
- {Phase 1}: {Date range}
- {Phase 2}: {Date range}
- {Phase 3}: {Date range}

Read the full file on GitHub · 111 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 111 lines · 33 tokens per session scan A a8e2983f41eb

Subscribe to this mod's changes

tech-radar is a skill published in the GitHub repository saolalab/clawforce (38 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 33 tokens to every session and 668 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

agenticmail

🎀 AgenticMail — Full email, SMS, storage & multi-agent coordination for AI agents. 63 tools.

InternLM/WildClawBench · 28 tokens

ai-meeting-scheduling

Booking links fail for groups. SkipUp schedules meetings with 2-50 participants via email — one API call coordinates across timezones automatically. Also: check status, pause, resume, or cancel requests. Async only — does not instant-book, access calendars, or do free/busy lookups.

InternLM/WildClawBench · 66 tokens

agentic-paper-digest-skill

Fetches and summarizes recent arXiv and Hugging Face papers with Agentic Paper Digest. Use when the user wants a paper digest, a JSON feed of recent papers, or to run the arXiv/HF pipeline.

InternLM/WildClawBench · 54 tokens

eachlabs-voice-audio

Text-to-speech, speech-to-text, voice conversion, and audio processing using EachLabs AI models. Supports ElevenLabs TTS, Whisper transcription with diarization, and RVC voice conversion. Use when the user needs TTS, transcription, or voice conversion.

InternLM/WildClawBench · 60 tokens

arxiv-summarizer-orchestrator

End-to-end orchestration skill for periodic arXiv collection and reporting using three sub-skills: arxiv-search-collector, arxiv-paper-processor, and arxiv-batch-reporter. Supports manual language control across all markdown outputs and Stage-B processing strategy (subagentparallel default max 5, or serial).

InternLM/WildClawBench · 75 tokens

academic-literature-search

这是一个专注于学术文献检索的专业工具,集成了多个权威学术数据库,提供全面、快速、准确的文献检索服务。支持多数据库并发检索、高级过滤、智能排序和多种输出格式。.

InternLM/WildClawBench · 0 tokens