diff --git a/skills/.curated/insideout/LICENSE.txt b/skills/.curated/insideout/LICENSE.txt new file mode 100644 index 00000000..8c836e29 --- /dev/null +++ b/skills/.curated/insideout/LICENSE.txt @@ -0,0 +1,190 @@ + Apache License + Version 2.0, January 2004 + http://www.apache.org/licenses/ + + TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION + + 1. Definitions. + + "License" shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document. + + "Licensor" shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License. + + "Legal Entity" shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + "control" means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity. + + "You" (or "Your") shall mean an individual or Legal Entity + exercising permissions granted by this License. + + "Source" form shall mean the preferred form for making modifications, + including but not limited to software source code, documentation + source, and configuration files. + + "Object" form shall mean any form resulting from mechanical + transformation or translation of a Source form, including but + not limited to compiled object code, generated documentation, + and conversions to other media types. + + "Work" shall mean the work of authorship, whether in Source or + Object form, made available under the License, as indicated by a + copyright notice that is included in or attached to the work + (an example is provided in the Appendix below). + + "Derivative Works" shall mean any work, whether in Source or Object + form, that is based on (or derived from) the Work and for which the + editorial revisions, annotations, elaborations, or other modifications + represent, as a whole, an original work of authorship. For the purposes + of this License, Derivative Works shall not include works that remain + separable from, or merely link (or bind by name) to the interfaces of, + the Work and Derivative Works thereof. + + "Contribution" shall mean any work of authorship, including + the original version of the Work and any modifications or additions + to that Work or Derivative Works thereof, that is intentionally + submitted to the Licensor for inclusion in the Work by the copyright owner + or by an individual or Legal Entity authorized to submit on behalf of + the copyright owner. For the purposes of this definition, "submitted" + means any form of electronic, verbal, or written communication sent + to the Licensor or its representatives, including but not limited to + communication on electronic mailing lists, source code control systems, + and issue tracking systems that are managed by, or on behalf of, the + Licensor for the purpose of discussing and improving the Work, but + excluding communication that is conspicuously marked or otherwise + designated in writing by the copyright owner as "Not a Contribution." + + "Contributor" shall mean Licensor and any individual or Legal Entity + on behalf of whom a Contribution has been received by the Licensor and + subsequently incorporated within the Work. + + 2. Grant of Copyright License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + copyright license to reproduce, prepare Derivative Works of, + publicly display, publicly perform, sublicense, and distribute the + Work and such Derivative Works in Source or Object form. + + 3. Grant of Patent License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + (except as stated in this section) patent license to make, have made, + use, offer to sell, sell, import, and otherwise transfer the Work, + where such license applies only to those patent claims licensable + by such Contributor that are necessarily infringed by their + Contribution(s) alone or by combination of their Contribution(s) + with the Work to which such Contribution(s) was submitted. If You + institute patent litigation against any entity (including a + cross-claim or counterclaim in a lawsuit) alleging that the Work + or a Contribution incorporated within the Work constitutes direct + or contributory patent infringement, then any patent licenses + granted to You under this License for that Work shall terminate + as of the date such litigation is filed. + + 4. Redistribution. You may reproduce and distribute copies of the + Work or Derivative Works thereof in any medium, with or without + modifications, and in Source or Object form, provided that You + meet the following conditions: + + (a) You must give any other recipients of the Work or + Derivative Works a copy of this License; and + + (b) You must cause any modified files to carry prominent notices + stating that You changed the files; and + + (c) You must retain, in the Source form of any Derivative Works + that You distribute, all copyright, patent, trademark, and + attribution notices from the Source form of the Work, + excluding those notices that do not pertain to any part of + the Derivative Works; and + + (d) If the Work includes a "NOTICE" text file as part of its + distribution, then any Derivative Works that You distribute must + include a readable copy of the attribution notices contained + within such NOTICE file, excluding any notices that do not + pertain to any part of the Derivative Works, in at least one + of the following places: within a NOTICE text file distributed + as part of the Derivative Works; within the Source form or + documentation, if provided along with the Derivative Works; or, + within a display generated by the Derivative Works, if and + wherever such third-party notices normally appear. The contents + of the NOTICE file are for informational purposes only and + do not modify the License. You may add Your own attribution + notices within Derivative Works that You distribute, alongside + or as an addendum to the NOTICE text from the Work, provided + that such additional attribution notices cannot be construed + as modifying the License. + + You may add Your own copyright statement to Your modifications and + may provide additional or different license terms and conditions + for use, reproduction, or distribution of Your modifications, or + for any such Derivative Works as a whole, provided Your use, + reproduction, and distribution of the Work otherwise complies with + the conditions stated in this License. + + 5. Submission of Contributions. Unless You explicitly state otherwise, + any Contribution intentionally submitted for inclusion in the Work + by You to the Licensor shall be under the terms and conditions of + this License, without any additional terms or conditions. + Notwithstanding the above, nothing herein shall supersede or modify + the terms of any separate license agreement you may have executed + with Licensor regarding such Contributions. + + 6. Trademarks. This License does not grant permission to use the trade + names, trademarks, service marks, or product names of the Licensor, + except as required for reasonable and customary use in describing the + origin of the Work and reproducing the content of the NOTICE file. + + 7. Disclaimer of Warranty. Unless required by applicable law or + agreed to in writing, Licensor provides the Work (and each + Contributor provides its Contributions) on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + implied, including, without limitation, any warranties or conditions + of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A + PARTICULAR PURPOSE. You are solely responsible for determining the + appropriateness of using or redistributing the Work and assume any + risks associated with Your exercise of permissions under this License. + + 8. Limitation of Liability. In no event and under no legal theory, + whether in tort (including negligence), contract, or otherwise, + unless required by applicable law (such as deliberate and grossly + negligent acts) or agreed to in writing, shall any Contributor be + liable to You for damages, including any direct, indirect, special, + incidental, or consequential damages of any character arising as a + result of this License or out of the use or inability to use the + Work (including but not limited to damages for loss of goodwill, + work stoppage, computer failure or malfunction, or any and all + other commercial damages or losses), even if such Contributor + has been advised of the possibility of such damages. + + 9. Accepting Warranty or Additional Liability. While redistributing + the Work or Derivative Works thereof, You may choose to offer, + and charge a fee for, acceptance of support, warranty, indemnity, + or other liability obligations and/or rights consistent with this + License. However, in accepting such obligations, You may act only + on Your own behalf and on Your sole responsibility, not on behalf + of any other Contributor, and only if You agree to indemnify, + defend, and hold each Contributor harmless for any liability + incurred by, or claims asserted against, such Contributor by reason + of your accepting any such warranty or additional liability. + + END OF TERMS AND CONDITIONS + + Copyright 2024-2026 Luther Systems Ltd. + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. diff --git a/skills/.curated/insideout/SKILL.md b/skills/.curated/insideout/SKILL.md new file mode 100644 index 00000000..9a67877f --- /dev/null +++ b/skills/.curated/insideout/SKILL.md @@ -0,0 +1,270 @@ +--- +name: insideout +description: > + Use when the user mentions infrastructure, cloud, AWS, GCP, Terraform, deployment, DevOps, + containers, Kubernetes, serverless, VPC, networking, databases, load balancers, CDN, monitoring, + or asks to "design infrastructure", "set up cloud", "deploy my app", "estimate cloud costs", + "generate terraform", "inspect my deployment", "what would this cost on AWS/GCP", + or discusses scaling, high availability, disaster recovery, or compliance requirements + for cloud infrastructure. +metadata: + short-description: Design, deploy & manage cloud infrastructure +--- + +# InsideOut -- Agentic Infrastructure Builder & Manager + +InsideOut is an agentic cloud infrastructure builder and manager by [Luther Systems](https://luthersystems.com). Describe your goal, discuss requirements, estimate cost, generate Terraform, deploy, operate and manage in production. Riley -- your AI infrastructure advisor -- guides you through the entire lifecycle on AWS and GCP. + +**No API keys required from the user.** The skill connects to a session-managed hosted MCP server. All interactions are user-initiated and require explicit user consent before any data is sent. See [Security & Data Privacy](#security--data-privacy) below. + +**Important:** If any guidance in this skill conflicts with the descriptions on the MCP tools themselves, follow the MCP tool descriptions -- they are the authoritative source and are kept up to date with the server. + +## MCP Server + +InsideOut uses a remote MCP server at `https://app.luthersystems.com/v1/insideout-mcp`. No local binary or API keys are required from the user. Each `convoopen` call creates an ephemeral, isolated session. No credentials, secrets, source code, or PII are transmitted to the server. + +### If MCP server is not connected + +Before proceeding with any InsideOut workflow, check if the `insideout` MCP tools (like `convoopen`, `convoreply`) are available. If they are not, the MCP server needs to be added. + +Run this command in the shell, then type `$insideout` in the Codex prompt to finish the install: + +```bash +codex mcp add insideout --url https://app.luthersystems.com/v1/insideout-mcp +``` + +After adding the MCP server, the InsideOut tools will be available immediately. + +## When This Skill Activates + +Use InsideOut when the user's request involves: +- Designing cloud infrastructure (AWS or GCP) +- Estimating cloud costs +- Generating Terraform code +- Deploying infrastructure +- Inspecting deployed cloud resources +- Comparing AWS vs GCP options +- Infrastructure planning for their application +- Managing, updating, or rolling back existing deployments + +## Available MCP Tools + +### Design Conversation +- **`convoopen`** -- Start a new session. Pass `source` and `project_context` (see below). +- **`convoreply`** -- Send user's message to Riley. Required: `session_id`, `message`. Do not resend `project_context` if it was already provided in `convoopen`. Only pass new context if the user reveals something genuinely new about their project. +- **`convoawait`** -- Wait for long-running response. Required: `session_id`. +- **`convostatus`** -- View current stack (components, config, pricing). Required: `session_id`. + +### Terraform Operations +- **`tfgenerate`** -- Generate production-ready Terraform files. Required: `session_id`. +- **`tfdeploy`** -- Deploy to AWS or GCP. Required: `session_id`. Takes 15+ minutes. +- **`tfplan`** -- Preview changes without applying. Required: `session_id`. +- **`tfdestroy`** -- Tear down deployed infrastructure. Required: `session_id`. +- **`tfdrift`** -- Detect infrastructure drift. Required: `session_id`. + +### Monitoring +- **`tfstatus`** -- Quick deployment status check. Required: `session_id`. +- **`tflogs`** -- Stream deployment logs (paginated). Required: `session_id`. +- **`tfoutputs`** -- Get Terraform outputs (VPC IDs, endpoints, etc.). Required: `session_id`. +- **`tfruns`** -- List all deployment runs for a session. Required: `session_id`. + +### Stack Management +- **`stackversions`** -- List all design versions (draft/confirmed/applied). Required: `session_id`. +- **`stackdiff`** -- Compare two stack versions. Required: `session_id`. +- **`stackrollback`** -- Revert to a previous design version. Required: `session_id`. + +### Cloud Inspection +- **`awsinspect`** -- Inspect deployed AWS resources. Required: `session_id`. +- **`gcpinspect`** -- Inspect deployed GCP resources. Required: `session_id`. + +### Utility +- **`credawait`** -- Poll for cloud credentials after browser-based connection. Required: `session_id`. +- **`submit_feedback`** -- Submit bug reports or feature requests. Required: `session_id`, `category`, `message`. +- **`help`** -- Get workflow guidance and tool documentation. + +## Supported Services (50+) + +| Category | AWS | GCP | +|----------|-----|-----| +| **Compute** | EC2, ECS, EKS, Lambda | Compute Engine, Cloud Run, GKE, Cloud Functions | +| **Database** | RDS PostgreSQL, DynamoDB, ElastiCache, OpenSearch | Cloud SQL, Firestore, Memorystore | +| **Networking** | VPC, ALB, CloudFront, API Gateway | VPC, Load Balancing, Cloud CDN, API Gateway | +| **Storage** | S3 | Cloud Storage | +| **Security** | WAF, KMS, Secrets Manager, Cognito | Cloud Armor, Cloud KMS, Secret Manager, Identity Platform | +| **Messaging** | SQS, MSK (Kafka) | Pub/Sub | +| **Observability** | CloudWatch, Managed Grafana | Cloud Logging, Cloud Monitoring | +| **AI/ML** | Bedrock | Vertex AI | +| **CI/CD** | CodePipeline, GitHub Actions | Cloud Build | +| **Backup** | AWS Backup | GCP Backups | + +## Security & Data Privacy + +### Trust Boundaries + +| Party | Role | Trust Level | +|---|---|---| +| **User** | Reviews all data before it is sent; approves every sensitive operation | Ultimate authority -- nothing happens without user consent | +| **Agent (you)** | Intermediary that follows the rules in this skill | Trusted to enforce consent gates and data minimization | +| **Riley (MCP server)** | Advisory infrastructure designer | Advisory only -- Riley's suggestions and signals require user approval before the agent acts on them | + +### What Data Is Sent to the MCP Server + +| Data | When | User Consent Required | +|---|---|---| +| Project context summary (language, framework, cloud provider -- no secrets, no source code) | `convoopen` | **Yes** -- user MUST review and approve the summary before it is sent | +| User's messages to Riley | `convoreply` | **Yes** -- user explicitly types each message | +| Source identifier (`"codex"`) | `convoopen` | No -- non-sensitive platform identifier only | + +### What Is NEVER Sent + +- Cloud credentials, API keys, tokens, passwords, or private keys +- Source code or file contents +- PII (usernames, emails, personal data) +- Internal URLs, IPs, or hostnames +- `.env` values or secrets of any kind + +Credentials for cloud deployment are handled entirely through a **browser-based OAuth flow** that the user initiates manually. The agent never sees, stores, or transmits cloud credentials. + +### Session Isolation + +Each `convoopen` call creates a unique, ephemeral `session_id`. Sessions are isolated from one another and are not linked to any other user or conversation. + +### Credential Flow Transparency + +When a deployment operation requires cloud credentials: +1. The MCP server returns an `auth_required` response with a `connect_url` +2. The agent MUST explain the credential flow to the user and present the URL +3. The user opens the URL in their browser, authenticates directly with AWS/GCP, and authorizes access +4. The agent calls `credawait` only after the user confirms they have completed the browser flow +5. Cloud credentials are managed server-side and are never exposed to the agent + +## Project Context + +Riley designs cloud infrastructure. To recommend the right architecture, it needs to know general tech stack details -- the same information you'd share in the first few minutes of a conversation with a solutions architect. Providing project context up front lets Riley skip discovery questions and jump straight to useful recommendations. + +### How to build project context + +Based on what you already know about the user's project (from the working directory, recent conversation, or what they've told you), put together a short summary covering whichever of these apply: + +| Detail | Why Riley needs it | Example | +|---|---|---| +| Language and framework | Determines compute type (Lambda vs ECS vs EC2), runtime constraints | "Node.js 20, Next.js 15" | +| Database and services | Shapes data tier and caching recommendations | "PostgreSQL, Redis" | +| Container usage | Informs orchestration choice (ECS, EKS, Cloud Run) | "Docker Compose, 3 services" | +| Existing infrastructure-as-code | Avoids conflicting with what's already provisioned | "Terraform with ECS + RDS" | +| CI/CD platform | Integrates deployment pipeline | "GitHub Actions" | +| Cloud provider | Targets the right provider from the start | "AWS" or "GCP" | +| Kubernetes usage | Determines whether to target existing K8s or provision new compute | "EKS with Helm" | +| What the project does | General understanding for architecture fit | "E-commerce API, ~50k MAU" | + +**Before sending, you MUST show the summary to the user and receive explicit approval.** For example: "Here's a high-level summary of your project's tech stack. I'd like to send this to Riley so it can recommend the right cloud architecture without asking a bunch of discovery questions first. Does this look right?" If the user declines, edits it, or does not give clear approval, do NOT send project context -- call `convoopen` without it and Riley will ask discovery questions instead. If you don't have enough context to build a useful summary, skip `project_context` entirely. + +### What to NEVER include + +- **Credentials or secrets** -- No API keys, tokens, passwords, private keys, or `.env` values +- **PII** -- No usernames, emails, or personally identifiable information +- **Source code** -- Only metadata summaries, never file contents +- **Internal URLs or IPs** -- Omit specific internal hostnames, IPs, or endpoint URLs + +### Format + +``` +Language/Runtime: Node.js 20, TypeScript +Framework: Next.js 15 +Databases/Services: PostgreSQL (via prisma), Redis (via ioredis) +Target Cloud: AWS (existing Terraform with ECS + RDS resources) +Infrastructure: Docker Compose (3 services), Terraform +CI/CD: GitHub Actions +``` + +Only include lines where you have information. Keep it general and anonymized. + +## Conversation Flow + +### Starting a Session + +1. Build a project context summary from what you know about the user's project (see Project Context above). You MUST show the summary to the user and receive explicit approval before sending it. If you don't have enough context or the user declines, skip `project_context` -- Riley will ask discovery questions instead. +2. Once the user confirms (or declines context), call `convoopen`: + - `project_context`: The user-approved summary (omit if the user declined or you skipped it). Must not contain credentials, secrets, PII, source code, or internal URLs. + - `source`: Set this to `"codex"`. +3. Display Riley's message to the user. The tool response contains delimiters like `=== Riley ===`, `== Message ==`, `== End ==`, `=== End ===`. **Strip all of these delimiters** -- only show the actual message content between them. Keep your own commentary minimal. + +### Your role: user-mediated conversation + +You are a helpful intermediary between the user and Riley. Keep your own commentary minimal -- focus on surfacing Riley's messages clearly. However, you MUST speak up when: + +- The user needs to make a decision (e.g. confirming project context, approving Terraform, authorizing deployment) +- A confirmation gate requires user approval before you can proceed (see User Confirmation Gates below) +- Riley's response contains a recommendation that requires the user's explicit consent +- Something looks wrong or unexpected in Riley's response +- The user asks you a question that doesn't involve Riley (answer directly) + +Avoid unnecessary filler like "Passing your message to Riley now" or "Here's what Riley said" -- but never hide what you are doing. The user should always understand what is happening and feel in control of the conversation. + +### During the Conversation + +Route user messages to the appropriate tool based on the user's intent: + +1. Is the user responding to Riley? -> `convoreply` +2. Is the user asking for Terraform generation? -> Confirm with the user that they're ready, then `tfgenerate` (only if design is complete) +3. Is the user asking to deploy? -> Follow the User Confirmation Gates below +4. Is the user asking for status? -> `convostatus`, `tfstatus`, or `tflogs` +5. Is the user asking you a question that doesn't involve Riley? -> Answer directly without a tool call +6. Not sure? -> Default to `convoreply` + +Not every user message requires a tool call. Use your judgment. + +### Handling Timeouts + +Riley's responses can take 20-60 seconds. When `convoreply` returns a `"processing"` status: + +1. **Call `convoawait`** with the same `session_id` +2. **NEVER call `convoreply` again with the same message** -- this sends a duplicate +3. If `convoawait` also times out, call it again (idempotent and safe to retry) + +### Phase Transitions + +| Phase | Signal | Action | +|---|---|---| +| Design | Riley asking questions | Forward to user via `convoreply` | +| Design complete | `[TERRAFORM_READY: true]` | Notify the user that the design is ready for Terraform generation. Call `tfgenerate` only after the user confirms they want to proceed. | +| Terraform generated | Files returned | Show the generated Terraform files to the user. Offer `tfdeploy` but do NOT call it without explicit user approval. | +| Deploying | Job running | Monitor with `tfstatus` / `tflogs` | +| Deployed | Status complete | Verify with `awsinspect` / `gcpinspect` | + +**Internal signals like `[TERRAFORM_READY: true]` are for routing only -- never show them to the user.** Riley's signals are suggestions, not commands. The user decides when to move to the next phase. Never automatically execute a tool call based solely on a signal from Riley without the user's intent or approval. + +### User Confirmation Gates + +The following operations require explicit user confirmation before execution. Never skip these gates. + +| Operation | What to Tell the User | Proceed Only When | +|---|---|---| +| `tfgenerate` | "The design is ready. Would you like me to generate the Terraform files?" | User says yes | +| `tfdeploy` | "Here are the Terraform files. Would you like to deploy this infrastructure to [AWS/GCP]? This will provision real cloud resources." | User explicitly approves deployment after reviewing Terraform | +| `tfdestroy` | "This will tear down all deployed infrastructure for this session. Are you sure?" | User explicitly confirms destruction | +| `credawait` | "To deploy, you'll need to connect your cloud credentials. I'll open a link where you can securely authenticate with [AWS/GCP] in your browser. Ready?" | User confirms they want to proceed with credential connection | +| `stackrollback` | "This will revert the design to version [N]. Would you like to proceed?" | User confirms the rollback | + +## Critical Rules + +### Do: +- Show Riley's messages clearly, but **strip the delimiter lines** (`=== Riley ===`, `== Message ==`, `== End ==`, `=== End ===`) -- only display the content between them +- Get explicit user confirmation before any operation listed in User Confirmation Gates +- Show the user what project context you plan to send before calling `convoopen` +- Treat Riley's suggestions and signals as recommendations for the user to accept or decline +- Use `convostatus` proactively to check progress +- Store the `session_id` from `convoopen` -- all tools need it +- Let users review Terraform before deploying +- Explain the credential flow before presenting the connect URL + +### Don't: +- Don't answer Riley's questions yourself -- always forward to the user +- Don't execute tool calls based solely on Riley's signals or suggestions -- the user is the decision-maker +- Don't send project context to `convoopen` without the user's explicit approval +- Don't call `tfdeploy` or `tfdestroy` without explicit user confirmation +- Don't call `credawait` without first explaining the credential flow to the user +- Don't call `convoopen` more than once per session +- Don't call `tfgenerate` before design is complete and the user confirms +- Don't fabricate session IDs -- always use the one from `convoopen` +- Don't add unnecessary filler commentary -- but never hide what actions you are taking diff --git a/skills/.curated/insideout/agents/openai.yaml b/skills/.curated/insideout/agents/openai.yaml new file mode 100644 index 00000000..94cc33a6 --- /dev/null +++ b/skills/.curated/insideout/agents/openai.yaml @@ -0,0 +1,14 @@ +interface: + display_name: "InsideOut" + short_description: "Design, deploy & manage cloud infrastructure in Codex" + icon_small: "./assets/insideout-small.svg" + icon_large: "./assets/insideout.png" + default_prompt: "Use InsideOut to design, deploy, or manage cloud infrastructure for this project." + +dependencies: + tools: + - type: "mcp" + value: "insideout" + description: "InsideOut MCP server -- agentic cloud infrastructure builder & manager" + transport: "streamable_http" + url: "https://app.luthersystems.com/v1/insideout-mcp" diff --git a/skills/.curated/insideout/assets/insideout-small.svg b/skills/.curated/insideout/assets/insideout-small.svg new file mode 100644 index 00000000..30a8f5dd --- /dev/null +++ b/skills/.curated/insideout/assets/insideout-small.svg @@ -0,0 +1,3 @@ + + + diff --git a/skills/.curated/insideout/assets/insideout.png b/skills/.curated/insideout/assets/insideout.png new file mode 100644 index 00000000..c36085a0 Binary files /dev/null and b/skills/.curated/insideout/assets/insideout.png differ