tech-radar-boot
From the author
Use when choosing or evaluating a technology (framework, database, library, cloud tool) — injects Tikal Israeli Tech Radar context (adoption ring, quadrant, opinion, Keep/Start alternatives for Stop items) and pairs the selection with ADR capture via /architect-specify; invoked from team-boot's Class Boots catalog (formerly tech-radar-context).
Install
npx skills add tikalk/adlc-team-skills --skill tech-radar-boot -a claude-code
Installs to .claude/skills/tech-radar-boot/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
- Ships scripts we have not reviewedLow
Why 78
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- architect-boottikalk/adlc-team-skillsUse when architecture work starts or a tech-stack or pattern decision emerges — injects the project ADR index (docs/adlc/memory/adr/, legacy .adlc/memory/adr/ fallback) as session context and pairs the decision with capture via /architect-specify; invoked from team-boot's Class Boots catalog.Planning★ 143
- technology-radarmagnus919/agent-skillsBuild and maintain technology radars for adoption, trial, assessment, and hold decisions, and choose proportionate architecture-governance paths for technology portfolios. Use when governing technology choices, build-versus-buy decisions, architecture standards, exceptions, or engineering portfolio risk. Do not use for enterprise capability or target-state architecture, writing ADRs, implementing systems, security engineering, or operational incident/runbook work.Security★ 148
- architect-specifytikalk/adlc-team-skillsUse when you want guided trade-off analysis, multi-option comparison, or structured architectural decision facilitation before documenting. Optional for routine capture — team-boot writes lightweight ADR drafts directly.Planning★ 143
- product-boottikalk/adlc-team-skillsUse when product or feature work starts, or a PDR-worthy decision (scope, persona, monetization) emerges — injects the PDR index (docs/adlc/memory/pdr/, legacy .adlc/memory/pdr/ fallback) as session context and pairs the decision with capture via /product-specify; invoked from team-boot's Class Boots catalog.Planning★ 143
- architecture-decision-recordswshobson/agentsWrite and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.Planning★ 41.7K
- tech-radar-patternsvibeeval/vibecosystemThoughtWorks Radar model, technology evaluation framework, ADR format, and stack compatibility analysisOther★ 540
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in