Radar Automation
ComposioHQ/awesome-claude-skills
Automate Radar tasks via Rube MCP (Composio). An agent skill from ComposioHQ/awesome-claude-skills.
Build a technology radar for an engineering team, categorizing technologies into Adopt/Trial/Assess/Hold quadrants following the ThoughtWorks Tech Radar format.
MITAuto-check passed
Install Tech Radar
$ npx skills add mohitagw15856/pm-claude-skills --skill tech-radar -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills tech-radar --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/tech-radar .claude/skills/tech-radar && rm -rf skills-srcUse ~/.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/
Install the "tech-radar" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/tech-radar into .claude/skills/tech-radar/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tech-radar", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/tech-radarType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill tech-radar -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills tech-radar --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/tech-radar .agents/skills/tech-radar && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "tech-radar" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/tech-radar into .agents/skills/tech-radar/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tech-radar", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill tech-radar -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills tech-radar --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/tech-radar .cursor/skills/tech-radar && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "tech-radar" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/tech-radar into .cursor/skills/tech-radar/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tech-radar", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/tech-radar--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill tech-radar -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills tech-radar --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/tech-radar .gemini/skills/tech-radar && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "tech-radar" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/tech-radar into .gemini/skills/tech-radar/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tech-radar", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills tech-radarInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill tech-radar -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/tech-radar .github/skills/tech-radar && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "tech-radar" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/tech-radar into .github/skills/tech-radar/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tech-radar", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill tech-radar -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills tech-radar --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/tech-radar .opencode/skills/tech-radar && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "tech-radar" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/tech-radar into .opencode/skills/tech-radar/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tech-radar", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
tech-radar- GitHub stars
- 1.4k
- Token cost
- ~3.3k tokens
- SKILL.md length
- 1,598 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Build a technology radar for an engineering team, categorizing technologies into Adopt/Trial/Assess/Hold quadrants following the ThoughtWorks Tech Radar format.
- Works in 4 steps: Submit to [Slack channel / form URL]… → A tech lead reviews within 2 weeks and… → At the review session, the architecture… → …
- Asked to create a tech radar
- SKILL.md covers Required Inputs, Output Format, How to Read This Radar and Quadrant 1: Techniques, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Tech Radar is an agent skill from mohitagw15856/pm-claude-skills. Build a technology radar for an engineering team, categorizing technologies into Adopt/Trial/Assess/Hold quadrants following the ThoughtWorks Tech Radar format. Use when asked to create a tech radar, evaluate the team's technology landscape, categorize tools and frameworks, or establish a technology strategy. Produces a full tech radar with quadrant tables, individual blip rationales, a decision trail, and a maintenance process guide.
Its SKILL.md is about 3.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to create a tech radar
- Evaluate the teams technology landscape
- Categorize tools and frameworks
- Establish a technology strategy
Example prompts
- “/tech-radar”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Submit to [Slack channel / form URL] with: technology name, quadrant, proposed ring, and one-paragraph rationale.
- A tech lead reviews within 2 weeks and either schedules it for the next review session or requests more information.
- At the review session, the architecture group discusses and votes. Simple majority wins; ties go to Hold pending further evidence.
- Approved blips are added to the radar doc and the decision trail within 1 week of the session.
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. 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
Tech Radar loads about 3.3k tokens when it runs. Until then it costs about 112 tokens; SKILL.md has 1,598 words of instructions outside code blocks.
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 mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 1,598 words, ~3,309 tokens.
Download SKILL.mdSave it as
.claude/skills/tech-radar/SKILL.md (or your agent's skills folder).- name
- tech-radar
- description
- Build a technology radar for an engineering team, categorizing technologies into Adopt/Trial/Assess/Hold quadrants following the ThoughtWorks Tech Radar format. Use when asked to create a tech radar, evaluate the team's technology landscape, categorize tools and frameworks, or establish a technology strategy. Produces a full tech radar with quadrant tables, individual blip rationales, a decision trail, and a maintenance process guide.
Tech Radar
Produce a complete technology radar document for an engineering team. The radar gives the team a shared, explicit position on every significant technology in their stack — what to standardize on, what to experiment with, what to evaluate, and what to actively stop using. Follow the ThoughtWorks Tech Radar format: four quadrants (Techniques, Tools, Platforms, Languages & Frameworks) each with four rings (Adopt, Trial, Assess, Hold). Each technology entry ("blip") gets a ring assignment, a one-paragraph rationale, and a date. Include a decision trail showing what moved and why, and a maintenance process the team can run to keep the radar current.
Required Inputs
Ask for these if not already provided:
- Team or company name — for the document header
- Current tech stack — list every significant technology, tool, language, and platform the team currently uses
- Technologies under active evaluation — tools or frameworks the team is currently trying or considering
- Technologies to deprecate or move off — anything the team wants to stop using or is actively migrating away from
- Strategic technology bets — any technologies the company has made a deliberate bet on (e.g., "we're all-in on Kubernetes" or "migrating to event-driven architecture")
- Team context — team size, product domain, and any constraints (regulatory, compliance, vendor lock-in concerns)
If a technology is mentioned without a ring placement, use the rationale inputs to determine the appropriate ring. When uncertain between two rings, ask.
Output Format
Technology Radar: [Team / Company Name]
Edition: [Month Year] Maintained by: [Team Name / Architecture Guild / CTO Office] Review cadence: Bi-annual (every 6 months) Next review: [Month Year + 6 months]
How to Read This Radar
This radar reflects [Team / Company Name]'s current thinking on technologies we use, evaluate, and retire. Use it to make consistent technology choices, onboard new engineers, and have structured conversations about the stack.
Quadrants categorize the type of technology:
| Quadrant | What belongs here |
|---|---|
| Techniques | Methods, patterns, and practices (e.g., trunk-based development, event sourcing) |
| Tools | Software tools used in the development and delivery process (e.g., linters, CI systems, observability platforms) |
| Platforms | Infrastructure and hosting environments (e.g., AWS, Kubernetes, Snowflake) |
| Languages & Frameworks | Programming languages and application frameworks (e.g., Go, React, FastAPI) |
Rings express our recommendation:
| Ring | Meaning | What to do |
|---|---|---|
| Adopt | Industry-proven, working well for us — our standard choice | Use by default for new work; no special justification needed |
| Trial | Worth pursuing — we are experimenting with it in limited production use | Use in a bounded context with architectural oversight; share learnings |
| Assess | Worth exploring — we have not used it in production yet | Spike, prototype, or research; do not use in production without a review |
| Hold | Do not start new work with this technology | Complete existing commitments; do not expand use; plan migration |
Quadrant 1: Techniques
Adopt
| Technology | Since | Notes |
|---|---|---|
| [Technique name, e.g., Trunk-based development] | [Month Year] | [One sentence: why we adopted it and what it replaced] |
| [Technique name] | [Month Year] | [One sentence rationale] |
| [Technique name] | [Month Year] | [One sentence rationale] |
[Technique name] — Adopt [One paragraph rationale. Explain what problem this technique solves, why it works well in your context, and what the team should know before applying it. Reference any internal experience — e.g., "We rolled this out across 8 services in 2024 and saw a 40% reduction in merge conflicts."]
[Repeat for each Adopt-ring technique.]
Trial
| Technology | Since | Notes |
|---|---|---|
| [Technique name] | [Month Year] | [One sentence: what we're testing and where] |
[Technique name] — Trial [One paragraph. What are we trialing? In which teams or services? What hypothesis are we testing? What would cause us to move it to Adopt vs. Hold?]
Assess
| Technology | Since | Notes |
|---|---|---|
| [Technique name] | [Month Year] | [One sentence: why we're interested] |
[Technique name] — Assess [One paragraph. Why is this interesting to us? What would we need to see to move it to Trial? Who is responsible for the assessment?]
Hold
| Technology | Since | Notes |
|---|---|---|
| [Technique name] | [Month Year] | [One sentence: why we're stopping and what replaces it] |
[Technique name] — Hold [One paragraph. Why are we putting this on hold? What is the migration path? What is the target end-state for teams still using it?]
Quadrant 2: Tools
Adopt
| Technology | Since | Notes |
|---|---|---|
| [Tool name, e.g., GitHub Actions] | [Month Year] | [One sentence rationale] |
| [Tool name] | [Month Year] | [One sentence rationale] |
[Tool name] — Adopt [One paragraph rationale. Why is this our standard tool? What does it do well in our context? Any configuration or usage patterns the team should follow?]
[Repeat for each Adopt-ring tool.]
Trial
| Technology | Since | Notes |
|---|---|---|
| [Tool name] | [Month Year] | [One sentence: what we're testing] |
[Tool name] — Trial [One paragraph rationale and trial scope.]
Assess
| Technology | Since | Notes |
|---|---|---|
| [Tool name] | [Month Year] | [One sentence: why we're evaluating it] |
[Tool name] — Assess [One paragraph: what sparked interest, who is evaluating, and timeline.]
Hold
| Technology | Since | Notes |
|---|---|---|
| [Tool name] | [Month Year] | [One sentence: what replaces it] |
[Tool name] — Hold [One paragraph: deprecation rationale and migration path.]
Quadrant 3: Platforms
Adopt
| Technology | Since | Notes |
|---|---|---|
| [Platform name, e.g., AWS EKS] | [Month Year] | [One sentence rationale] |
| [Platform name] | [Month Year] | [One sentence rationale] |
[Platform name] — Adopt [One paragraph. What does this platform provide? What are the boundaries of its use? Any internal golden-path setup the team should follow?]
[Repeat for each Adopt-ring platform.]
Trial
| Technology | Since | Notes |
|---|---|---|
| [Platform name] | [Month Year] | [One sentence: scope of trial] |
[Platform name] — Trial [One paragraph rationale and trial boundaries.]
Assess
| Technology | Since | Notes |
|---|---|---|
| [Platform name] | [Month Year] | [One sentence: why we're exploring it] |
[Platform name] — Assess [One paragraph assessment plan.]
Hold
| Technology | Since | Notes |
|---|---|---|
| [Platform name] | [Month Year] | [One sentence: migration target and timeline] |
[Platform name] — Hold [One paragraph: what triggered the hold decision, migration target, and timeline.]
Quadrant 4: Languages & Frameworks
Adopt
| Technology | Since | Notes |
|---|---|---|
| [Language/Framework, e.g., Go] | [Month Year] | [One sentence rationale] |
| [Language/Framework] | [Month Year] | [One sentence rationale] |
[Language/Framework] — Adopt [One paragraph. What is this language or framework used for? What are the team's proficiency expectations? Any frameworks or libraries that go alongside it as part of the standard choice?]
[Repeat for each Adopt-ring language or framework.]
Show full SKILL.md (617 more words)Show less
Trial
| Technology | Since | Notes |
|---|---|---|
| [Language/Framework] | [Month Year] | [One sentence: bounded use case] |
[Language/Framework] — Trial [One paragraph rationale.]
Assess
| Technology | Since | Notes |
|---|---|---|
| [Language/Framework] | [Month Year] | [One sentence: interest driver] |
[Language/Framework] — Assess [One paragraph assessment plan.]
Hold
| Technology | Since | Notes |
|---|---|---|
| [Language/Framework] | [Month Year] | [One sentence: reason and migration path] |
[Language/Framework] — Hold [One paragraph: deprecation rationale, existing system obligations, and timeline to retire.]
Decision Trail
This log records every ring movement since the radar's first edition. Use it to understand the evolution of our technology choices.
| Technology | Quadrant | Previous Ring | New Ring | Edition | Reason |
|---|---|---|---|---|---|
| [Name] | [Quadrant] | — | Adopt | [Month Year] | First placement — [one sentence why] |
| [Name] | [Quadrant] | Assess | Trial | [Month Year] | [What prompted the move — evidence, team feedback, production trial results] |
| [Name] | [Quadrant] | Trial | Adopt | [Month Year] | [Adoption rationale — usage results, team satisfaction, scale proven] |
| [Name] | [Quadrant] | Adopt | Hold | [Month Year] | [Why moved to Hold — better alternative, security concern, cost, vendor issue] |
| [Name] | [Quadrant] | — | Hold | [Month Year] | First placement — added directly to Hold because [reason] |
Radar Maintenance Process
Who Contributes
- Architecture review group / CTO office — final ring placement decisions
- All engineers — submit blip nominations via [channel or form]
- Tech leads — triage nominations and prepare proposals for review sessions
Update Cadence
| Activity | Frequency | Owner |
|---|---|---|
| New blip nominations accepted | Ongoing — any engineer via [channel] | Anyone |
| Nomination triage | Monthly | Tech leads |
| Full radar review session | Every 6 months | Architecture group |
| Published radar update | Every 6 months | [Owner name or role] |
How to Nominate a Blip
- Submit to [Slack channel / form URL] with: technology name, quadrant, proposed ring, and one-paragraph rationale.
- A tech lead reviews within 2 weeks and either schedules it for the next review session or requests more information.
- At the review session, the architecture group discusses and votes. Simple majority wins; ties go to Hold pending further evidence.
- Approved blips are added to the radar doc and the decision trail within 1 week of the session.
Ring Change Criteria
| To move TO Adopt | To move TO Trial | To move TO Assess | To move TO Hold |
|---|---|---|---|
| Proven in multiple production systems; team broadly trained; clear operational runbook exists | At least one production use case running; architectural oversight in place; learnings documented | Concrete use case identified; spike completed or in progress; interest from at least 2 engineers | Better alternative exists; known security/compliance risk; strategic direction change; unacceptable maintenance burden |
Questions about this radar: [Slack channel] | Submit a nomination: [URL or channel]
Quality Checks
- Every blip has a written rationale paragraph — not just a table row entry
- The decision trail is populated with at least the initial placement date for every blip
- Hold-ring entries include a concrete migration path or target technology, not just "stop using it"
- Ring definitions are present and include both what each ring means AND what engineers should do in response
- Maintenance process includes: nomination channel, review cadence, who decides, and ring-change criteria
- Technologies identified as "strategic bets" in the inputs are placed in Adopt (if proven) or Trial (if being rolled out)
- Technologies identified for deprecation are in Hold with a rationale that references the replacement
Anti-Patterns
- Do not place a technology in Adopt without evidence it is proven at the team's scale — aspirational placements mislead engineers
- Do not add a blip without a written rationale paragraph — table rows without context are unusable
- Do not create a Hold entry without specifying a concrete migration path or target technology
- Do not skip the maintenance process — a radar with no process for updates becomes stale within two quarters
- Do not omit ring definitions — engineers need to know what they should do in response to each ring, not just what the ring means
Example Trigger Phrases
- "Create a tech radar."
- "Evaluate the team's technology landscape."
- "Establish a technology strategy."
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/tech-radar of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Tech 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Tech Radar this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~3.3k | Automated safety check: Pass | MIT | |
| Radar AutomationComposioHQ/awesome-claude-skills | 77k | 3 repos | ~723 | Automated safety check: Pass | None | |
| Tech Matrixsickn33/agentic-awesome-skills | 47k | 1 repos | ~3.1k | Automated safety check: Pass | MIT | |
| Technology Radarmagnus919/hermes-profiles | 289 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Nexrad Radar Visualizationsickn33/agentic-awesome-skills | 47k | 1 repos | ~3.7k | Automated safety check: Pass | MIT | |
| Sanity Radarsanity-io/sanity | 6.4k | — | ~2.9k | Automated safety check: Pass | MIT |
Similar skills
Tech Matrix
sickn33/agentic-awesome-skills
Reference document for monopoly tech-matrix. An agent skill from sickn33/agentic-awesome-skills.
Technology Radar
magnus919/hermes-profiles
CTO methodology for technology evaluation, architecture governance, build-vs-buy decisions, engineering metrics, technical debt quantification, and innovation pipeline management.
Nexrad Radar Visualization
sickn33/agentic-awesome-skills
Plot NEXRAD Level II/III site scans and decoded radar mosaics with correct radar geometry, map grids, units, quality masks, timestamps, and provenance.
- Official
Sanity Radar
sanity-io/sanity
Studio Radar, the repo-health dashboard at radar.sanity.dev (source in dev/radar) — what each tool shows, where the data lives, how to query benchRun / gitCommit / gitTag / bisectSession documents…
Radar Satellite Analysis
sickn33/agentic-awesome-skills
Interpret weather radar and satellite observations by validating product metadata and geometry, deriving storm and cloud structures, tracking evolution, and quantifying uncertainty.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Questions about Tech Radar
What does Tech Radar do?
Build a technology radar for an engineering team, categorizing technologies into Adopt/Trial/Assess/Hold quadrants following the ThoughtWorks Tech Radar format. Tech Radar is an agent skill from mohitagw15856/pm-claude-skills. Build a technology radar for an engineering team, categorizing technologies into Adopt/Trial/Assess/Hold quadrants following the ThoughtWorks Tech Radar format.
When should I use Tech Radar?
Tech Radar fits situations like: asked to create a tech radar; evaluate the teams technology landscape; categorize tools and frameworks; establish a technology strategy.
How do I install Tech Radar in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill tech-radar -a claude-code`. Or copy the skill folder (skills/tech-radar in mohitagw15856/pm-claude-skills) into .claude/skills/tech-radar in your project. Claude Code loads it when a task matches its description.
How do I install Tech Radar in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill tech-radar -a codex`. Or copy the skill folder (skills/tech-radar in mohitagw15856/pm-claude-skills) into .agents/skills/tech-radar in your project. Codex loads it when a task matches its description.
Can I use Tech 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 mohitagw15856/pm-claude-skills --skill tech-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/tech-radar, .gemini/skills/tech-radar, .github/skills/tech-radar and .opencode/skills/tech-radar in your project.
What does Tech Radar need to run?
SKILL.md names no scripts, command-line tools or credentials: Tech Radar is instructions for the agent only.
Does Tech 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 Tech 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 Tech Radar use?
Tech Radar is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Tech Radar use?
About 3.3k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Tech Radar?
Skills that share tags, products or a category with Tech Radar: Radar Automation (ComposioHQ/awesome-claude-skills, 77k stars), Tech Matrix (sickn33/agentic-awesome-skills, 47k stars), Technology Radar (magnus919/hermes-profiles, 289 stars) and Nexrad Radar Visualization (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Tech Radar?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.