Menu
Technology maturity assessment with adoption recommendation and risk analysis
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | Technology Radar |
| department | scout |
| description | Technology maturity assessment with adoption recommendation and risk analysis |
| version | 1 |
| triggers | ["framework","technology","tool","evaluate","choose","migrate","adopt","stack"] |
Assess technology maturity and fitness for the project, placing it on a radar quadrant with a clear adoption recommendation and risk profile.
Classify into one or more categories:
Place the technology in one quadrant:
Evidence for placement:
ADOPT
|
+-----------+
| [Name] | (or placed in TRIAL / ASSESS / HOLD)
+-----------+
|
HOLD ------- + ------- TRIAL
|
ASSESS
Quadrant: [Adopt / Trial / Assess / Hold] Confidence: [High / Medium / Low] Category: [Language / Framework / Library / Tool / Platform / Infrastructure]
Recommendation: [Adopt now / Trial in next sprint / Assess and revisit in N months / Hold and consider alternatives] Timeline: [Immediate / Next quarter / Next half / Not recommended] Migration path: [Description of incremental adoption strategy if applicable]
| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|
| ... | High/Med/Low | High/Med/Low | ... |
| Aspect | Current | Proposed | Delta |
|---|---|---|---|
| Performance | ... | ... | ... |
| DX | ... | ... | ... |
| Ecosystem | ... | ... | ... |
| Maintenance | ... | ... | ... |
Local git operations for syncing, branching, merging, and conflict resolution
GitHub interactions for issues, PRs, releases, and repository management
Use this skill when performing hardware security analysis for System-on-Chip components — threat modeling, verification scaffolding, compliance mapping, executive briefing, microarchitectural attack analysis, physical side-channel assessment, kernel security analysis, emerging hardware security, or TLA+ formal specification. Routes to the appropriate specialist. Trigger phrases include "threat model my SoC", "run STRIDE analysis", "generate SVA assertions", "compliance check against FIPS", "executive summary of findings", "Spectre analysis for cache", "DPA attack assessment", "kernel hardening review", "PQC hardware review", "TLA+ spec for access control". Do NOT use for software-only security, network security, or web application security.
Use when working with Terraform or OpenTofu - creating modules, writing tests (native test framework, Terratest), setting up CI/CD pipelines, reviewing configurations, choosing between testing approaches, debugging state issues, implementing security scanning (trivy, checkov), or making infrastructure-as-code architecture decisions
Security audit checklist for web applications. Use when reviewing, auditing, or hardening a web app's security posture. Covers rate limiting, auth headers, IP blocking, CORS, security middleware, input validation, file upload limits, ORM usage, and password hashing. Triggers on requests like "review security", "harden this app", "security audit", "check for vulnerabilities", or when building/reviewing API endpoints.
Use this skill when connecting AI or LLMs to data platforms. Covers MCP servers for warehouses, natural-language-to-SQL, embeddings for data discovery, LLM-powered enrichment, and AI agent data access patterns. Common phrases: "text-to-SQL", "MCP server for Snowflake", "LLM data enrichment", "AI agent access". Do NOT use for general data integration (use data-integration) or dbt modeling (use dbt-transforms).