Agent skill

Technology Radar

by magnus919 in magnus919/hermes-profiles

CTO methodology for technology evaluation, architecture governance, build-vs-buy decisions, engineering metrics, technical debt quantification, and innovation pipeline management.

MITAuto-check passedDevelopment

Install Technology Radar

skills CLI
$ npx skills add magnus919/hermes-profiles --skill technology-radar -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install magnus919/hermes-profiles technology-radar --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/magnus919/hermes-profiles.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/technology-radar .claude/skills/technology-radar && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
technology-radar
GitHub stars
289
Token cost
~1.3k tokens
SKILL.md length
462 words
Files
5 (incl. references)
Skills in repo
31
Repo updated
First seen
Licence
MIT

At a glance

CTO methodology for technology evaluation, architecture governance, build-vs-buy decisions, engineering metrics, technical debt quantification, and innovation pipeline management.

  • Works in 6 steps: Technology is a means, not an end. Every… → Radar is a living document. A technology… → Build vs buy is never just cost. Total… → …
  • Tasks that involve Technical debt
  • SKILL.md covers Domain Model, When to Load, Loading Order and Reference Files, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Technology Radar is an agent skill from magnus919/hermes-profiles. CTO methodology for technology evaluation, architecture governance, build-vs-buy decisions, engineering metrics, technical debt quantification, and innovation pipeline management. Covers technology radar framework (Adopt/Trial/Assess/Hold), TCO analysis, architecture review boards, RFC processes, DORA/SPACE/DevEx metrics, debt interest calculation, and POC-to-production readiness criteria.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/architecture-governance.md`, `references/build-vs-buy.md` and `references/engineering-metrics.md`).

It sits in Development, covering Technical debt, Software architecture and Platform engineering. The repository describes itself as: Curated Hermes Agent profiles for specialist swarms — opinionated, Hermes-optimized, artifact-pyramid native. The licence is MIT.

When your agent uses it

  • Tasks that involve Technical debt
  • Tasks that involve Software architecture
  • Tasks that involve Platform engineering

Example prompts

  • “/technology-radar”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Technology is a means, not an end. Every technology decision must trace back to a business outcome. "Because it's new" is not a reason to…
  2. Radar is a living document. A technology radar updated once a year is a museum. Update it quarterly, or every time a significant…
  3. Build vs buy is never just cost. Total Cost of Ownership includes maintenance, hiring, training, integration, migration, and opportunity…
  4. Engineering metrics measure the system, not the people. DORA metrics measure the delivery capability of the org. SPACE measures developer…
  5. Technical debt has a principal and an interest payment. The principal is the cost to fix it properly. The interest is the recurring drag…
  6. Production readiness gates exist to prevent crisis. Every gate that is skipped in the name of speed will be paid for in incident response…

What it can do on your machine

Read from SKILL.md and the folder at commit 867a555. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Technology Radar loads about 1.3k tokens when it runs, and up to ~7.6k if it reads all its reference files. Until then it costs about 102 tokens; SKILL.md has 462 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~102
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~7.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from magnus919/hermes-profiles at commit 867a555, republished under its MIT licence (© magnus919). 462 words, ~1,264 tokens.

Download SKILL.mdSave it as .claude/skills/technology-radar/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
technology-radar
description
CTO methodology for technology evaluation, architecture governance, build-vs-buy decisions, engineering metrics, technical debt quantification, and innovation pipeline management. Covers technology radar framework (Adopt/Trial/Assess/Hold), TCO analysis, architecture review boards, RFC processes, DORA/SPACE/DevEx metrics, debt interest calculation, and POC-to-production readiness criteria.
version
1.0.0
author
Hermes Agent community
license
MIT

Technology Radar

CTO methodology for making technology decisions, governing architecture, measuring engineering effectiveness, managing technical debt, and operating an innovation pipeline. These frameworks help a CTO balance short-term delivery velocity with long-term platform health.

Domain Model

DomainCoversArtifact
Technology RadarAdopt/Trial/Assess/Hold quadrants, tool selection criteria, deprecation policyTechnology radar document
Build vs BuyTCO analysis, decision matrices, vendor evaluation, integration costBuild-vs-buy recommendation
Architecture GovernanceStandards, review boards, RFC process, design reviewsADRs, RFC documents, governance charter
Engineering MetricsDORA (deploy frequency, lead time, MTTR, change failure rate), SPACE, DevExEngineering dashboard, health report
Technical DebtInterest calculation, remediation prioritization, principal estimationTechnical debt register
Innovation PipelineHorizon scanning, POC criteria, production readiness gatesInnovation funnel, POC report

When to Load

Load this skill when the task involves:

  • Evaluating a new technology or tool for adoption
  • Making a build-vs-buy decision with TCO analysis
  • Designing or auditing architecture governance processes
  • Setting up engineering metrics dashboards (DORA, SPACE)
  • Quantifying and prioritizing technical debt remediation
  • Running an innovation pipeline with POC-to-production gates
  • Deprecating or retiring legacy technology
  • Conducting an architecture review board session

Loading Order

skill_view('technology-radar')                      # This — methodology index
skill_view('executive-methodology')                  # Shared decision frameworks
skill_view('artifact-pyramids')                      # Output contract
skill_view('technology-radar', file_path='references/technology-radar.md')
skill_view('technology-radar', file_path='references/build-vs-buy.md')
skill_view('technology-radar', file_path='references/architecture-governance.md')
skill_view('technology-radar', file_path='references/engineering-metrics.md')

Reference Files

ReferenceLoad WhenFile
Technology RadarYou need to evaluate and categorize a technology or tool for adoption, trial, assessment, or holdreferences/technology-radar.md
Build vs BuyYou're comparing build vs buy options with TCO analysis and decision criteriareferences/build-vs-buy.md
Architecture GovernanceYou're designing RFC processes, review boards, or architecture standardsreferences/architecture-governance.md
Engineering MetricsYou need to measure engineering effectiveness with DORA, SPACE, or DevEx frameworksreferences/engineering-metrics.md
Show full SKILL.md (211 more words)Show less

Design Principles

  1. Technology is a means, not an end. Every technology decision must trace back to a business outcome. "Because it's new" is not a reason to adopt. "Because it solves X faster/safer/cheaper" is.
  2. Radar is a living document. A technology radar updated once a year is a museum. Update it quarterly, or every time a significant adoption/hold/promote/promote-to-trial decision is made.
  3. Build vs buy is never just cost. Total Cost of Ownership includes maintenance, hiring, training, integration, migration, and opportunity cost. A cheaper build today may be vastly more expensive over 3 years.
  4. Engineering metrics measure the system, not the people. DORA metrics measure the delivery capability of the org. SPACE measures developer satisfaction. Neither is a performance review tool for individuals.
  5. Technical debt has a principal and an interest payment. The principal is the cost to fix it properly. The interest is the recurring drag on velocity. Prioritize debt where interest/principal ratio is highest.
  6. Production readiness gates exist to prevent crisis. Every gate that is skipped in the name of speed will be paid for in incident response time later.
  • executive-methodology — shared decision frameworks and governance
  • operational-design — COO-side process design and scaling
  • artifact-pyramids — output contract specification
  • platform-engineering — infrastructure and CI/CD implementation patterns

© magnus919, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references) in skills/technology-radar of magnus919/hermes-profiles.

  • SKILL.md
  • references/architecture-governance.md
  • references/build-vs-buy.md
  • references/engineering-metrics.md
  • references/technology-radar.md

Open the folder on GitHubat commit 867a555

Compare with similar skills

Technology Radar next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Technology Radar compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Technology Radar this skillmagnus919/hermes-profiles289—~1.3kAutomated safety check: PassMIT
Vanity Engineering Reviewbencium/bencium-marketplace446—~2.4kAutomated safety check: PassMIT
Tech Debt Auditcode-yeongyu/oh-my-openagent70k—~2.4kAutomated safety check: NotesCustom licence
Codebase Pathfinderthedotmack/claude-mem99k—~1.5kAutomated safety check: PassApache-2.0
Architecture SurveyYeachan-Heo/oh-my-claudecode40k—~1.3kAutomated safety check: PassMIT
Cto Plan ReviewerIbrahim-3d/orchestrator-supaconductor381—~2.9kAutomated safety check: PassAGPL-3.0

Similar skills

  • Vanity Engineering Review

    bencium/bencium-marketplace

    Reviews codebases, architectures, PRs, and technical plans for vanity engineering — code and systems built for the developer's ego, resume, or intellectual pleasure rather than delivering user or…

    446 GitHub stars~2.4k tokensUpdated 7 days ago
    DevelopmentAuto-check passed
  • Tech Debt Audit

    code-yeongyu/oh-my-openagent

    Audits a codebase for technical debt across nine dimensions and writes TECH_DEBT_AUDIT.md with file-cited findings, severity, effort estimates and priorities.

    70k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check: notes
  • Codebase Pathfinder

    thedotmack/claude-mem

    Maps a codebase into feature-grouped Mermaid flowcharts, finds duplicated concerns across features and proposes a unified architecture with handoff prompts for planning.

    99k GitHub stars~1.5k tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Architecture Survey

    Yeachan-Heo/oh-my-claudecode

    Periodic survey that walks a repo's module graph and reports ranked candidates for deepening, without changing any code itself.

    40k GitHub stars~1.3k tokensUpdated 3 days ago
    DevelopmentAuto-check passed
  • Cto Plan Reviewer

    Ibrahim-3d/orchestrator-supaconductor

    Technical architecture review agent for execution plans. An agent skill from Ibrahim-3d/orchestrator-supaconductor.

    381 GitHub stars~2.9k tokensUpdated 13 days ago
    DevelopmentAuto-check passed
  • Archify Diagrams

    tt-a1i/archify

    Creates interactive architecture, workflow, sequence, data-flow and lifecycle diagrams as standalone HTML with inline SVG, themes and image or video export.

    82k GitHub stars~2.9k tokensUpdated today
    DevelopmentAuto-check passed

More from magnus919/hermes-profiles

All 31 skills in this repo
  • Data Scientist

    magnus919/hermes-profiles

    PhD-level expertise in data science, statistics, and machine learning.

    289 GitHub stars~3.3k tokensUpdated 3 mo ago
    Auto-check passed
  • Brand Designer

    magnus919/hermes-profiles

    Create comprehensive brand identity documentation for any brand.

    289 GitHub stars~2.3k tokensUpdated 3 mo ago
    Auto-check passed
  • Sdd Authoring

    magnus919/hermes-profiles

    Specification authoring for AI-native SDD — writes formal specifications in structured formats (Gherkin, user stories, acceptance criteria), enforces spec quality gates, and produces…

    289 GitHub stars~1.4k tokensUpdated 3 mo ago
    Auto-check passed
  • Sdd Verification

    magnus919/hermes-profiles

    SDD acceptance criteria verification — maps specification acceptance criteria to tests, validates implementation output against spec requirements, and produces artifact-pyramid-compliant…

    289 GitHub stars~1.8k tokensUpdated 3 mo ago
    Auto-check passed
  • Sdd Work Decomposition

    magnus919/hermes-profiles

    SDD work decomposition — translates formal specifications into dependency-aware task plans with per-task acceptance criteria.

    289 GitHub stars~1.4k tokensUpdated 3 mo ago
    Auto-check passed
  • Artifact Pyramids

    magnus919/hermes-profiles

    Progressive disclosure for what AI agents produce. An agent skill from magnus919/hermes-profiles.

    289 GitHub stars~2.5k tokensUpdated 3 mo ago
    Auto-check passed

Categories

Questions about Technology Radar

What does Technology Radar do?

CTO methodology for technology evaluation, architecture governance, build-vs-buy decisions, engineering metrics, technical debt quantification, and innovation pipeline management. Technology Radar is an agent skill from magnus919/hermes-profiles. CTO methodology for technology evaluation, architecture governance, build-vs-buy decisions, engineering metrics, technical debt quantification, and innovation pipeline management.

When should I use Technology Radar?

Technology Radar fits situations like: tasks that involve Technical debt; tasks that involve Software architecture; tasks that involve Platform engineering.

How do I install Technology Radar in Claude Code?

Run `npx skills add magnus919/hermes-profiles --skill technology-radar -a claude-code`. Or copy the skill folder (skills/technology-radar in magnus919/hermes-profiles) into .claude/skills/technology-radar in your project. Claude Code loads it when a task matches its description.

How do I install Technology Radar in Codex?

Run `npx skills add magnus919/hermes-profiles --skill technology-radar -a codex`. Or copy the skill folder (skills/technology-radar in magnus919/hermes-profiles) into .agents/skills/technology-radar in your project. Codex loads it when a task matches its description.

Can I use Technology Radar in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add magnus919/hermes-profiles --skill technology-radar -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/technology-radar, .gemini/skills/technology-radar, .github/skills/technology-radar and .opencode/skills/technology-radar in your project.

What does Technology Radar need to run?

SKILL.md names no scripts, command-line tools or credentials: Technology Radar is instructions for the agent only.

Does Technology Radar access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Technology Radar safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Technology Radar use?

Technology Radar is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Technology Radar use?

About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 6.4k tokens, read only when the agent opens those files.

What are the alternatives to Technology Radar?

Skills that share tags, products or a category with Technology Radar: Vanity Engineering Review (bencium/bencium-marketplace, 446 stars), Tech Debt Audit (code-yeongyu/oh-my-openagent, 70k stars), Codebase Pathfinder (thedotmack/claude-mem, 99k stars) and Architecture Survey (Yeachan-Heo/oh-my-claudecode, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Technology Radar?

magnus919 (a GitHub user) maintains it in magnus919/hermes-profiles, which has 289 GitHub stars. The repository holds 31 skills in this directory. The repository was last updated on June 27, 2026.

Source: magnus919/hermes-profiles on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.