tech-radar
SolidMUST use when user asks 'what's new?', 'any updates?', 'latest versions?', 'breaking changes?', 'should we upgrade?', 'what changed in X?', or when starting a new project. Detects dependencies dynamically from `package.json` / `requirements.txt` / `go.mod` / `composer.json` first, then reports per-package: latest version (vs. installed), breaking changes since installed version, security advisories (CRITICAL/HIGH), and deprecation warnings. Falls back to a generic stack table only when no manifest file is found.
Install
Quality Score: 85/100
Skill Content
Details
- Author
- faizkhairi
- Repository
- faizkhairi/claude-code-blueprint
- Created
- 4 months ago
- Last Updated
- 1 weeks ago
- Language
- Shell
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
tech-radar
MUST use when user asks 'what's new?', 'any updates?', 'latest versions?', 'breaking changes?', 'should we upgrade?', 'what changed in X?', or when starting a new project to check if dependencies are current. Also trigger proactively at the start of major upgrade sessions.
dev-radar
Pull current, real-world software-dev signal on demand from GitHub trending, Reddit, research papers, and blogs — filtered to the user's stack, hype-filtered, with verified sources. Use when the user asks "what's new/trending", "latest in <tech>", "should I adopt X", or wants a dev digest. Coding topics only.
generate-tech-stack
FIRE this skill when the user's intent is to discover, list, visualize, document, or summarize the technologies used in a software project. This includes all of the following triggers: EXPLICIT COMMANDS: /generate-tech-stack; "generate tech stack"; "create tech stack"; "show tech stack"; "build tech stack"; "make tech stack page"; "tech stack report". DISCOVERY / INVENTORY INTENT: user wants to know what libraries, packages, dependencies, frameworks, tools, or services a project uses — phrased as: "what libraries does this use", "what packages are installed", "what dependencies does this project have", "list all tools", "what frameworks are in use", "show me the dependencies", "what's in requirements.txt", "scan my project", "audit the stack", "inventory the project", "what's this project built with", "what tech does this use", "show all packages", "detect the stack". VISUALIZATION / DOCUMENTATION INTENT: user wants an HTML page, visual report, or summary document of the project's technology choices — phrased