11h (edited) • General Discussion 💬
I adapted the AIS-OS kit for a Microsoft / corporate stack
I took the AIS-OS kit and re-pointed it for people stuck inside a Microsoft shop (M365, Power Platform, Power BI, Azure), running on Claude Code rather than n8n. Put it up under MIT so anyone here can fork it.
Same Four Cs structure, same Three Ms thinking baked in. What I changed for the corporate world:
- /onboard is now an adaptive interview that branches by department (IT, supply chain, or a generic path), maps your Connections, and drafts a least-privilege Entra/IT access request you can hand straight to your admins.
- Connection policy prefers a Microsoft MCP server where the tenant has consented it, and falls back to the CLIs (m365 / az / pac / Graph) when it hasn't, because most corporate tenants lock things down.
- A /project skill that spins up a self-contained sub-OS per workstream, with its own Context, decisions, and skills.
- Guardrails for a real tenant: read-only by default, every write needs sign-off, no autonomous sends. (We all remember the 150k-inbox story.)
It ships blank. Set three org values once, then each person runs /onboard.
Built on Nate's AIS-OS, full credit for the foundation and the frameworks.
2
3 comments
I adapted the AIS-OS kit for a Microsoft / corporate stack
skool.com/ai-automation-society
Learn to get paid for AI solutions, regardless of your background.
Leaderboard (30-day)
1
🔥
+7543
2
🔥
+5017
3
🔥
+3542
4
+3122
5
+1424
Powered by