Agent skill

Tech Decision

by team-attention in team-attention/hoyeon

This skill should be used when the user asks about "technical decision", "what to use", "A vs B", "comparison analysis", "library selection", "architecture decision", "which one to use"…

MITAuto-check passedBackend & APIs

Install Tech Decision

skills CLI
$ npx skills add team-attention/hoyeon --skill tech-decision -a claude-code

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

GitHub CLI
$ gh skill install team-attention/hoyeon tech-decision --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/team-attention/hoyeon.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/tech-decision .claude/skills/tech-decision && 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
tech-decision
GitHub stars
173
Token cost
~1.4k tokens
SKILL.md length
283 words
Files
3 (incl. references)
Skills in repo
36
Repo updated
First seen
Licence
MIT

At a glance

This skill should be used when the user asks about "technical decision", "what to use", "A vs B", "comparison analysis", "library selection", "architecture decision", "which one to use"…

  • Works in 6 steps: Problem Definition → Parallel Information Gathering → Synthesis Analysis → …
  • Asks about technical decision
  • SKILL.md covers Core Principle, Use Cases, Decision Workflow and Resources Used, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Tech Decision is an agent skill from team-attention/hoyeon. This skill should be used when the user asks about "technical decision", "what to use", "A vs B", "comparison analysis", "library selection", "architecture decision", "which one to use", "tradeoffs", "tech selection", "implementation approach", or needs deep analysis for technical decisions. Provides systematic multi-source research and synthesized recommendations.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/evaluation-criteria.md` and `references/report-template.md`).

It sits in Backend & APIs, covering Deep research. The repository describes itself as: Requirements-first Harness — derive, verify, execute. The licence is MIT.

When your agent uses it

  • Asks about technical decision
  • Comparison analysis
  • Library selection
  • Architecture decision

Example prompts

  • “technical decision”
  • “what to use”
  • “A vs B”
  • “/tech-decision”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Problem Definition
  2. Parallel Information Gathering
  3. Synthesis Analysis
  4. Final Report Generation
  5. Simple Comparison (A vs B)
  6. Deep Analysis (complex decision)

What it can do on your machine

Read from SKILL.md and the folder at commit 7cff032. 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 (its code samples are markdown).

    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 Decision loads about 1.4k tokens when it runs, and up to ~3.8k if it reads all its reference files. Until then it costs about 95 tokens; SKILL.md has 283 words of instructions outside code blocks.

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

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 team-attention/hoyeon at commit 7cff032, republished under its MIT licence (© team-attention). 283 words, ~1,383 tokens.

Download SKILL.mdSave it as .claude/skills/tech-decision/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
tech-decision
description
This skill should be used when the user asks about "technical decision", "what to use", "A vs B", "comparison analysis", "library selection", "architecture decision", "which one to use", "tradeoffs", "tech selection", "implementation approach", or needs deep analysis for technical decisions. Provides systematic multi-source research and synthesized recommendations.
version
0.1.0

Tech Decision - Deep Technical Decision Analysis

Skill for systematically analyzing technical decisions and deriving comprehensive conclusions.

Core Principle

Conclusion First: All reports present conclusion first, then provide evidence.

Use Cases

  • Library/framework selection (React vs Vue, Prisma vs TypeORM)
  • Architecture pattern decisions (Monolith vs Microservices, REST vs GraphQL)
  • Implementation approach selection (Server-side vs Client-side, Polling vs WebSocket)
  • Tech stack decisions (language, database, infrastructure, etc.)

Decision Workflow

Phase 1: Problem Definition

Clarify decision topic and context:

  1. Identify Topic: What needs to be decided?
  2. Identify Options: What are the choices to compare?
  3. Establish Criteria: What criteria to evaluate by?
    • Performance, learning curve, ecosystem, maintainability, cost, etc.
    • Set priority based on project characteristics
    • See references/evaluation-criteria.md for detailed criteria
Phase 2: Parallel Information Gathering

Gather information from multiple sources simultaneously. Must run in parallel:

┌─────────────────────────────────────────────────────────────┐
│  Run simultaneously (parallel with Task tool)               │
├─────────────────────────────────────────────────────────────┤
│  1. codebase-explorer agent                                 │
│     → Analyze existing codebase, identify patterns/constraints│
│                                                             │
│  2. docs-researcher agent                                   │
│     → Research official docs, guides, best practices        │
│                                                             │
│  3. Skill: dev-scan                                         │
│     → Gather community opinions (Reddit, HN, Dev.to, etc.)  │
│                                                             │
│  4. Skill: agent-council                                    │
│     → Gather various AI expert perspectives                 │
│                                                             │
│  5. [Optional] Context7 MCP                                 │
│     → Query latest docs per library                         │
└─────────────────────────────────────────────────────────────┘
Phase 3: Synthesis Analysis

Run tradeoff-analyzer agent with gathered information:

  • Organize pros/cons per option
  • Score by evaluation criteria
  • Organize conflicting opinions
  • Evaluate reliability (source-based)
Phase 4: Final Report Generation

Generate conclusion-first comprehensive report with decision-synthesizer agent (detailed template: references/report-template.md):

markdown
# Technical Decision Report: [Topic]

## Conclusion (Executive Summary)
**Recommendation: [Option X]**
[1-2 sentence key reason]

## Evaluation Criteria and Weights
| Criteria | Weight | Description |
|------|--------|------|
| Performance | 30% | ... |
| Learning Curve | 20% | ... |

## Option Analysis

### Option A: [Name]
**Pros:**
- [Pro 1] (Source: official docs)
- [Pro 2] (Source: Reddit r/webdev)

**Cons:**
- [Con 1] (Source: HN discussion)

**Good fit for:** [Scenario]

## Comprehensive Comparison
| Criteria | Option A | Option B | Option C |
|------|----------|----------|----------|
| Performance | ⭐⭐⭐ | ⭐⭐ | ⭐⭐⭐⭐ |
| **Total** | **X pts** | **Y pts** | **Z pts** |

## Recommendation Rationale
1. [Key reason 1 with source]
2. [Key reason 2 with source]

## Risks and Considerations
- [Consideration 1]
- [Consideration 2]

Resources Used

Agents (this plugin)
AgentRole
codebase-explorerAnalyze existing codebase, identify patterns/constraints
docs-researcherResearch official docs, guides, best practices
tradeoff-analyzerOrganize pros/cons, comparative analysis
decision-synthesizerGenerate conclusion-first final report
Existing Skills (call via Skill tool)
SkillPurposeHow to Call
dev-scanCommunity opinions from Reddit, HN, Dev.toSkill: dev-scan
agent-councilGather various AI expert perspectivesSkill: agent-council

Quick Execution Guide

1. Simple Comparison (A vs B)
User: "React vs Vue which is better?"

Execute:
1. Task docs-researcher + Task codebase-explorer (parallel)
2. Skill: dev-scan
3. Task tradeoff-analyzer
4. Task decision-synthesizer
2. Deep Analysis (complex decision)
User: "Thinking about which state management library to use"

Execute:
1. Task codebase-explorer (analyze current state)
2. Parallel:
   - Task docs-researcher (Redux, Zustand, Jotai, Recoil, etc.)
   - Skill: dev-scan
   - Skill: agent-council
3. Task tradeoff-analyzer
4. Task decision-synthesizer

Notes

  1. Provide Context: More accurate analysis with project characteristics, team size, existing tech stack
  2. Confirm Criteria: First confirm what criteria matter to user
  3. Show Reliability: Mark unclear or outdated sources
  4. Conclusion First: Always present conclusion first

© team-attention, 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 2 other files (references) in skills/tech-decision of team-attention/hoyeon.

  • SKILL.md
  • references/evaluation-criteria.md
  • references/report-template.md

Open the folder on GitHubat commit 7cff032

Compare with similar skills

Tech Decision 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.

Tech Decision compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Tech Decision this skillteam-attention/hoyeon173—~1.4kAutomated safety check: PassMIT
Tech Decisionteam-attention/plugins-for-claude-natives8272 repos~1.2kAutomated safety check: PassMIT
Customs Trade Law Onur Kafkaslawve-ai/awesome-legal-skills842—~4.1kAutomated safety check: PassAGPL-3.0
Claude To MedrixflowCitrus-bit/Anaxa120—~1.7kAutomated safety check: PassMIT
GitHub Deep Researchbytedance/deer-flow84k4 repos~1.3kAutomated safety check: PassMIT
Deep Research MCP Guidepminervini/deep-research-mcp113—~5.8kAutomated safety check: PassMIT

Similar skills

  • Tech Decision

    team-attention/plugins-for-claude-natives

    This skill should be used when the user asks to "기술 의사결정", "뭐 쓸지 고민", "A vs B", "비교 분석", "라이브러리 선택", "아키텍처 결정", "어떤 걸 써야 할지", "트레이드오프", "기술 선택", "구현 방식 고민", or needs deep analysis for technical…

    827 GitHub starsUsed in 2 repos~1.2k tokens
    Backend & APIsAuto-check passed
  • Customs Trade Law Onur Kafkas

    lawve-ai/awesome-legal-skills

    U.S. An agent skill from lawve-ai/awesome-legal-skills.

    842 GitHub stars~4.1k tokensUpdated 7 days ago
    Backend & APIsAuto-check passed
  • Claude To Medrixflow

    Citrus-bit/Anaxa

    Interact with MedrixFlow AI agent platform via its HTTP API.

    120 GitHub stars~1.7k tokensUpdated 1 mo ago
    Research & ScienceAuto-check passed
  • GitHub Deep Research

    bytedance/deer-flow

    Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.

    84k GitHub starsUsed in 4 repos~1.3k tokens
    Research & ScienceAuto-check passed
  • Deep Research MCP Guide

    pminervini/deep-research-mcp

    Explains how to run, integrate and debug the deep-research-mcp project through its CLI, Python API or MCP server, with OpenAI, Gemini and DR-Tulu backends.

    113 GitHub stars~5.8k tokensUpdated 11 days ago
    Research & ScienceAuto-check passed
  • Searches the web, code, companies and people through the Exa MCP server, with notes on setup, the web_search_exa tool and treating results as untrusted data.

    276k GitHub starsUsed in 4 repos~1.1k tokens
    Productivity & AutomationAuto-check passed

More from team-attention/hoyeon

All 36 skills in this repo
  • Skill Session Analyzer

    team-attention/hoyeon

    This skill should be used when the user asks to "analyze session", "evaluate skill execution", "check session logs", provides a session ID with a skill path, or wants to verify that a skill executed…

    173 GitHub stars~1.9k tokensUpdated 4 mo ago
    Auto-check: notes
  • Browser Work

    team-attention/hoyeon

    Recon-first browser automation. An agent skill from team-attention/hoyeon.

    173 GitHub stars~1.9k tokensUpdated 4 mo ago
    Auto-check passed
  • Check

    team-attention/hoyeon

    This skill should be used when the user wants to verify their changes before pushing, or update the project's rule checklists.

    173 GitHub stars~1.8k tokensUpdated 4 mo ago
    Auto-check: notes
  • Compound

    team-attention/hoyeon

    This skill should be used when the user says "/compound", "compound this", "document learnings", "save what we learned", or after completing a PR.

    173 GitHub stars~1.1k tokensUpdated 4 mo ago
    Auto-check: notes
  • QA

    team-attention/hoyeon

    Systematically QA test any application — web apps, native macOS apps, Electron apps, CLI tools, interactive REPLs, or anything on screen.

    173 GitHub stars~2.6k tokensUpdated 4 mo ago
    Auto-check: notes
  • Analyze Oss

    team-attention/hoyeon

    Analyze an open-source project from What/Why perspective (not how-it's-implemented).

    173 GitHub stars~2k tokensUpdated 4 mo ago
    Auto-check passed

Questions about Tech Decision

What does Tech Decision do?

This skill should be used when the user asks about "technical decision", "what to use", "A vs B", "comparison analysis", "library selection", "architecture decision", "which one to use"…. Tech Decision is an agent skill from team-attention/hoyeon. This skill should be used when the user asks about "technical decision", "what to use", "A vs B", "comparison analysis", "library selection", "architecture decision", "which one to use", "tradeoffs", "tech selection", "implementation approach", or needs deep analysis for technical decisions.

When should I use Tech Decision?

Tech Decision fits situations like: asks about technical decision; comparison analysis; library selection; architecture decision.

How do I install Tech Decision in Claude Code?

Run `npx skills add team-attention/hoyeon --skill tech-decision -a claude-code`. Or copy the skill folder (skills/tech-decision in team-attention/hoyeon) into .claude/skills/tech-decision in your project. Claude Code loads it when a task matches its description.

How do I install Tech Decision in Codex?

Run `npx skills add team-attention/hoyeon --skill tech-decision -a codex`. Or copy the skill folder (skills/tech-decision in team-attention/hoyeon) into .agents/skills/tech-decision in your project. Codex loads it when a task matches its description.

Can I use Tech Decision 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 team-attention/hoyeon --skill tech-decision -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-decision, .gemini/skills/tech-decision, .github/skills/tech-decision and .opencode/skills/tech-decision in your project.

What does Tech Decision need to run?

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

Does Tech Decision 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 Decision 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 Decision use?

Tech Decision 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 Decision use?

About 1.4k tokens (SKILL.md is roughly 5.5k 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 2.4k tokens, read only when the agent opens those files.

What are the alternatives to Tech Decision?

Skills that share tags, products or a category with Tech Decision: Tech Decision (team-attention/plugins-for-claude-natives, 827 stars), Customs Trade Law Onur Kafkas (lawve-ai/awesome-legal-skills, 842 stars), Claude To Medrixflow (Citrus-bit/Anaxa, 120 stars) and GitHub Deep Research (bytedance/deer-flow, 84k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Tech Decision?

team-attention (a GitHub organization) maintains it in team-attention/hoyeon, which has 173 GitHub stars. The repository holds 36 skills in this directory. The repository was last updated on May 21, 2026.

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