technical-acumen
Skill0 starsChanged 7 months agoMITView on GitHub
Understand system architecture, interface protocols, and technical costs to achieve an efficient balance between product ideals and technical reality.
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 25
Before proposing a requirement to R&D, ask yourself: "If this were my own money, how much would I be willing to spend to implement this …
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Technical Acumen: Technical Sensitivity and Architectural Understanding
Understanding technology is for better business trade-offs.
Checklist
- Identify Technical Constraints — Does the existing architecture support this feature? Is refactoring required?
- Analyze Interface Contracts (API Design) — Do input parameters, output parameters, and error codes align with business logic?
- Assess Implementation Cost (Estimation) — Is this a "one-day" task or a "one-month" engineering effort?
- Identify Technical Debt Risks — What long-term scalability have we sacrificed to meet a deadline?
Core Framework: Technical Assessment Model
- Scalability: Will the system crash if the user base grows 10x?
- Security: How is user privacy data encrypted? Are there injection risks?
- Consistency: In case of network jitter, will data become corrupted or inconsistent?
Expert Principles
Before proposing a requirement to R&D, ask yourself: "If this were my own money, how much would I be willing to spend to implement this feature?"
In this repository34 other files it gives its agents.
- agile-scrum-masterySkill
- artifact-provenanceSkill
- brainstormingSkill
- business-acumenSkill
- cross-functional-collaborationSkill
- customer-discoverySkill
- customer-empathySkill
- data-analysisSkill
- gtm-launch-managementSkill
- lean-experimentationSkill
- market-researchSkill
- metrics-definitionSkill
- negotiation-conflict-resolutionSkill
- north-star-metricSkill
- opportunity-mappingSkill
- outcome-ownershipSkill
- presentation-storytellingSkill
- prioritizationSkill
- problem-solvingSkill
- product-definitionSkill
- product-vision-strategySkill
- project-managementSkill
- prototypingSkill
- qa-quality-mindsetSkill
- roadmappingSkill
- spec-driven-designSkill
- stakeholder-managementSkill
- subagent-driven-discoverySkill
- user-interviewingSkill
- using-pmpowersSkill
- ux-design-awarenessSkill
- validation-guardSkill
- writing-plansSkill
- written-communicationSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.