/tech-evaluation
Evaluates a proposed technology choice (library, framework, ML model, infrastructure component, third-party service, or any new dependency) before it gets adopted into a project. Use this skill PROACTIVELY whenever the user mentions adopting, using, integrating, switching to, or
$ npx -y skills add EdytaKucharska/keel --skill tech-evaluation --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/tech-evaluation
Context preview
The summary Claude sees to decide when to auto-load this skill.
Evaluates a proposed technology choice (library, framework, ML model, infrastructure component, third-party service, or any new dependency) before it gets adopted into a project. Use this skill PROACTIVELY whenever the user mentions adopting, using, integrating, switching to, or
The AI fractional CTO that lives in your repo — and remembers you. A keel is the weighted spine below a boat's waterline: invisible, and the only reason the vessel stays upright as it takes on load. Your AI tools already generate the app — the sails.
Other skills on keel.
- /architecture-review
Reviews a proposed or existing software architecture for a product, feature, or system. Use this skill PROACTIVELY whenever the user describes how their product is structured, proposes a new architecture, mentions splitting or merging services, brings up data model decisions,
Open skill - /deep-review
The whole-project readiness review of an existing codebase. Invoke when the user EXPLICITLY runs /keel:deep-review, or asks for a comprehensive/full/deep review of their whole project — "is my app production-ready?", "review the whole project before I launch / before I start
Open skill - /enterprise-ready
The enterprise-sales security gauntlet. Invoke PROACTIVELY when a SPECIFIC customer, prospect, or deal is applying security or compliance scrutiny — a security questionnaire received (or expected from a named prospect), a customer's procurement/InfoSec/legal review, being asked
Open skill - /estimate-check
Invoke PROACTIVELY (do NOT judge the number directly, and NEVER produce a counter-estimate) whenever the user reports an engineering estimate, quote, or timeline someone gave them — "my engineer says 6 weeks, is that real?", "the agency/freelancer quoted 3 months", "is N weeks
Open skill - /feature-decision
Invoke PROACTIVELY (do NOT answer the implementation question directly, and do NOT re-brainstorm the feature) whenever a user wants to add a feature or capability to a product that already exists — "we want to add X", "how should we build [feature]?", "users are asking for X",
Open skill - /first-build-scope
Invoke PROACTIVELY (do NOT answer the build question directly) whenever a user wants to turn a product idea into a first build and no code exists yet — "I want to build an app/SaaS/tool that does X", "where do I start", "what would it take to build X", "what stack for a new X",
Open skill