Imported from maruthiprithivi/typeless_skills (
AGENTS.md). Install upstream withnpx skills add maruthiprithivi/typeless_skills. Copyright stays with the author.
SFOS Agent Instructions
This file is the compiled agent guide for the Solo Founder Operating System skill suite. AI agents should read this file to understand how to interact with SFOS.
Activation
The SFOS master skill activates when the user mentions ANY of these topics:
- Company automation, infrastructure, bootstrapping
- Personas (CPO, CTO, CFO, SRE, QA, CISO, CMO, Writer, DevOps, Support)
- Products, CI/CD, deployments, monitoring
- Security scanning, secrets, IP protection, commit shield
- Collaborator management, access control, onboarding, offboarding
- Obsidian vault, content publishing, email, newsletters
- System audit, cleanup, secret rotation, drift detection
Entry Point
The master skill is at sfos/SKILL.md. Always start there. It contains:
- First-run detection -- checks if
~/.sfos/environment.jsonexists - Modular setup -- guides users through picking only needed modules
- Routing table -- maps user intent to sub-skill SKILL.md files
- Credential safety rules -- secrets must NEVER flow through the AI context
Routing
| User intent keywords | Load this file |
|---|---|
| set up, bootstrap, initialize, new product | sfos/bootstrap/SKILL.md |
| commit, push, security, secret leak, IP | sfos/security/SKILL.md |
| add MCP, upgrade, enhance, changelog | sfos/evolve/SKILL.md |
| audit, clean, prune, rotate, drift | sfos/maintain/SKILL.md |
| onboard, offboard, access, permissions | sfos/collab/SKILL.md |
| vault, blog, email, publish, content | sfos/knowledge/SKILL.md |
Critical Rules
- Never read credential files (
.env,.credentials.local,*.key,*.pem) - Never let users paste secrets into the chat -- guide terminal commands instead
- Always check
~/.sfos/environment.jsonbefore any operation - Always write changelog via sfos-evolve before executing changes
- Progressive disclosure -- only load the sub-skill you need, not all of them
- Respect modules_enabled -- only offer capabilities the user has set up
Module Awareness
After setup, ~/.sfos/environment.json contains a modules_enabled array.
Only offer functionality for enabled modules. If the user tries to use a module
they haven't set up, offer to run the module setup flow instead of failing.
Shared Resources
- JSON schemas:
sfos/shared/schemas/ - Python libraries:
sfos/shared/lib/(infisical_client, vault_io, n8n_client, sfos_common) - Templates:
sfos/shared/templates/ - Dependencies:
sfos/shared/requirements.txt(requests only)