Assess technical risks and unknowns for acquisition and investment decisions.
npx skills add https://github.com/Arafly/sre-playbooks --skill due-diligence-arafly
Please help me install this Agent Skill. Skill: due-diligence Source: https://github.com/Arafly/sre-playbooks/tree/main/due-diligence Command: npx skills add https://github.com/Arafly/sre-playbooks --skill due-diligence-arafly
This Skill helps you assess the technical risks, unknowns, and value drivers of a company, product, platform, or system when access is limited and the decision must be made quickly. It focuses on identifying evidence that could affect valuation, integration cost, security exposure, compliance risk, and deal terms.
Review the available evidence for this transaction, identify the material technical risks and unknowns, and produce a go, no-go, or go-with-conditions recommendation.
High-intent search queries and answers about installing and using this skill.
Technical due diligence under limited access requires inventorying available evidence, analyzing architecture and operational risks, reviewing security and licensing exposures, and translating findings into a defensible go, no-go, or go-with-conditions recommendation.
Evidence-based tech review separates verified facts, management claims, assumptions, and unknowns so decision-makers can trust the findings. It narrows the review to material systems and dependencies, converting technical risks into concrete impacts on valuation and deal terms.
Assess vendor technical risk by reviewing architecture, security, licensing, and operational dependencies. This process identifies hidden technical debt, key-person dependence, and integration friction, translating them into concrete impacts on price, timeline, and deal structure.
Yes, deal-thesis scoping narrows the security review to the systems and workflows that matter to the transaction. It focuses on identifying evidence that could affect valuation, integration cost, security exposure, and compliance risk under time pressure.
The best way to review technical debt and key-person dependence is to inventory evidence, analyze architecture and operational risks, and translate findings into concrete impacts on deal terms, producing a defensible recommendation for decision-makers.
jewzaamGenerate C4 context, container, and component diagrams from a codebase.
alyamenfactoryIdentify and evaluate suppliers for B2B procurement with vendor evaluation matrices and RFPs.
LeKayScan codebases for technical debt indicators and maintain a debt register.
Dev-Dennis-040Audit DeFi smart contracts for vulnerabilities using automated analysis and manual review.
