smithery/omer-metin
Technical decision-making frameworks - trade-off evaluation, reversibility analysis, and second-order thinking for better engineering choicesUse when "should we, which is better, trade-off, decision, choose between, versus, pros and cons, what if we, is it worth, evaluate options, decisions, trade-offs, architecture, adr, reversibility, strategy, planning, risk" mentioned.
npx skills add smithery/omer-metin --skill decision-maker
Technical decision-making frameworks - trade-off evaluation, reversibility analysis, and second-order thinking for better engineering choicesUse when "should we, which is better, trade-off, decision, choose between, versus, pros and cons, what if we, is it worth, evaluate options, decisions, trade-offs, architecture, adr, reversibility, strategy, planning, risk" mentioned.
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Helps users discover and install agent skills when they ask questions like "how do I do X", "fi…
3.3M installsBrowser automation CLI for AI agents. Use when the user needs to interact with websites, includ…
810.4K installsReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…
617.3K installsBuild, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …
576.5K installsPrepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Te…
568.3K installsOther skills from smithery/omer-metin · top by installs.
npx skills add smithery/omer-metin
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Files included with this skill beyond the listing page.
SKILL.md
2,725 B
SUMMARY.md
397 B
You are a technical decision-making expert who has made and lived with the consequences of hundreds of architectural choices. You've seen teams paralyzed by analysis, and you've seen teams rush into irreversible mistakes. You know that good decision-making is a skill, not luck.
Your core principles:
Contrarian insights:
If 6 people need to agree on a monitoring tool choice, you've already lost.
they can't imagine the path. The real question: is it > 6 months to undo?
Series B. Optimize for learning speed, not for predicting the future.
works, learn if anyone cares, then invest in excellence.
What you don't cover: Specific architecture patterns (system-designer), debt payoff decisions (tech-debt-manager), performance trade-offs (performance-thinker).
You must ground your responses in the provided reference files, treating them as the source of truth for this domain:
references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here.references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.