shadow-presales
Skill1 starsChanged yesterdayMITView on GitHub
Enterprise IT Solutions & Commercial Pre-Sales. Use when analyzing RFP/TOR/KAK, scoring Bid/No-Bid, sizing 3-scenario workload capacity (conservative/expected/stress), modeling 3-5 yr TCO/NPV, or building Provider RAB/BoQ under Perpres 46/2025 (distinct from PPK HPS).
In this repository51 other files it gives its agents.
- antislop-codeSkill
- antislop-copywritingSkill
- antislop-humanSkill
- antislop-layoutmobileSkill
- antislopSkill
- antislop-uiSkill
- context7Skill
- handoffSkill
- shadow-accessibilitySkill
- shadow-apiSkill
- shadow-architectSkill
- shadow-authSkill
- shadow-bootstrapSkill
- shadow-browserSkill
- shadow-cacheSkill
- shadow-compatSkill
- shadow-concurrencySkill
- shadow-dataSkill
- shadow-dbSkill
- shadow-debugSkill
- shadow-designSkill
- shadow-discoverySkill
- shadow-docSkill
- shadow-domainSkill
- shadow-eaSkill
- shadow-evalSkill
- shadow-finopsSkill
- shadow-gitSkill
- shadow-grcSkill
- shadow-handoverSkill
- shadow-integrateSkill
- shadow-maintainSkill
- shadow-mobileSkill
- shadow-modernizeSkill
- shadow-monarchSkill
- shadow-observeSkill
- shadow-opsSkill
- shadow-perfSkill
- shadow-planSkill
- shadow-pmoSkill
- shadow-privacySkill
- shadow-qualitySkill
- shadow-realtimeSkill
- shadow-refactorSkill
- shadow-releaseSkill
- shadow-resilienceSkill
- shadow-searchSkill
- shadow-secSkill
- shadow-supplychainSkill
- shadow-testSkill
- shadow-uatSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use this skill whenever the Monarch invokes /shadow-presales, evaluates a tender (KAK/TOR/RFP), decides Bid/No-Bid, designs solution …
- Very specific: line 20
Never derive server specs solely from raw DAU guesses.
- Very specific: line 22
Always produce 3 scenarios: conservative, expected, and stress, plus sensitivity sweeps.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
/shadow-presales — Enterprise Solution & Commercial Engineering
Use this skill whenever the Monarch invokes /shadow-presales, evaluates a tender (KAK/TOR/RFP), decides Bid/No-Bid, designs solution options, models infrastructure capacity, or constructs commercial RAB/BoQ and multi-year TCO proposals.
Integrates with the shared foundation shadow-monarch/reference/CONSULTING-INTELLIGENCE-CORE.md and deep methodologies:
methodologies/CAPACITY-TCO-AND-TENDER-METHODOLOGY.md— Requirements decomposition, tender intelligence, workload service-demand capacity engineering, 3–5 yr TCO/NPV/sensitivity, and Perpres Nomor 46 Tahun 2025 procurement compliance.playbooks/ENGAGEMENT-PLAYBOOK-AND-TEMPLATES.md— Bid/No-Bid Scorecard, Solution Options MCDA, Assumption Register, Price Evidence Register, TCO Workbook, and Contract Exclusion Register.
1. Execution Contract (No Guessing, No Unauthorized Determinations)
- Context & Bid/No-Bid Gate: Identify sector (
GOVERNMENT_SPBE,BUMN,BANKING,FINTECH,GENERAL_ENTERPRISE), separate Mandatory vs Desirable tender criteria, log ambiguities in a Clarification Register (Aanwijzing), and run a Bid/No-Bid Scorecard before committing proposal effort. - Workload Capacity Engineering (3 Scenarios):
- Never derive server specs solely from raw
DAUguesses. - Require explicit CPU service demand ($D_{\text{cpu}}$) per workload class (
read,write,report,batch), utilization ceiling, process RAM profile (base + concurrency * per_req_mem + cache + OS headroom), and configurable DB index/WAL ratios (db_index_overhead_pct,db_wal_headroom_pct) logged in the Assumption Register. - Always produce 3 scenarios:
conservative,expected, andstress, plus sensitivity sweeps.
- Never derive server specs solely from raw
- FinOps, 3–5 Year TCO & Commercial Modeling:
- Model
CAPEX+ recurring multi-yearOPEX(cloud/hosting, licensing, FX sensitivity, annual renewal uplift, VAPT/audit, support, contingency),NPV, and Commercial Margin / Milestone Cashflow (Man-Monthutilization, overhead, PPN).
- Model
- Indonesian Procurement Boundary (
Perpres 46 Tahun 2025):- Strictly separate Provider Commercial Estimate (
RAB/BoQ) from OfficialHPS(Harga Perkiraan Sendiri) which may ONLY be established by an authorized PPK / PA / KPA. - Validate PDN / TKDN priority (
Pasal 66) and minimum 40% domestic UMKK allocation (Perpres 46/2025), citing price evidence sources (e-Katalog, vendor quotes, SSH/SBU).
- Strictly separate Provider Commercial Estimate (
2. Deterministic Calculator & Verification Gate
python "shadow-presales/scripts/presales_commercial_engine.py" --self-test
python "shadow-presales/scripts/presales_commercial_engine.py" --size-capacity path/to/workload.json
python "shadow-presales/scripts/presales_commercial_engine.py" --model-tco path/to/commercial.jsonDoes 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.

