@rubytech/create-maxy-code 0.1.33 → 0.1.34

package/payload/platform/plugins/anthropic/.claude-plugin/plugin.json

@@ -1,8 +0,0 @@
-{
-  "name": "anthropic",
-  "description": "Guide users through obtaining an Anthropic API key to power the public agent.",
-  "version": "0.1.0",
-  "author": {
-    "name": "Rubytech LLC"
-  }
-}

package/payload/platform/plugins/anthropic/PLUGIN.md

@@ -1,40 +0,0 @@
----
-name: anthropic
-description: Guide users through obtaining an Anthropic API key to power the public agent.
----
-
-# Anthropic / Claude Setup
-
-The public agent runs on the Anthropic API. This plugin handles obtaining, storing, and verifying an API key from the Anthropic Console (platform.claude.com).
-
-## When to activate
-
-- Prerequisites check detects missing Anthropic API key (via `api-key-verify` tool)
-- User asks how to connect Claude, get an Anthropic key, or set up their AI
-- BOOTSTRAP detects no working Anthropic API connection
-- User sees an API authentication error
-- User wants to rotate or replace their API key
-
-## What it unlocks
-
-- Claude as the AI model powering the public agent — conversations, reasoning, and tool use
-- Pay-per-use via Anthropic API key
-
-## Shared module
-
-API key management is centralised in `platform/lib/anthropic-key/` — all consumers (claude-agent.ts, admin MCP, email scripts, health route) import `readKey()`, `writeKey()`, `hasKey()`, and `validateKey()` from this module instead of inlining the env-var-then-file lookup pattern.
-
-## Skills
-
-| Task | When to use | Skill |
-|------|-------------|-------|
-| Obtain API key | `api-key-verify` returns `missing` or user wants to rotate key | `skills/get-api-key/SKILL.md` |
-
-## References
-
-| Topic | When to use | Reference |
-|-------|-------------|-----------|
-| Troubleshooting & FAQ | API key rejected, billing questions, manual key entry | `references/setup-guide.md` |
-| Console API surface | Understanding the endpoints used by the get-api-key skill | `references/console-api.md` |
-
-For API key acquisition (including during onboarding), use the `skills/get-api-key/SKILL.md` skill. For troubleshooting and common questions, load the reference.

package/payload/platform/plugins/anthropic/references/console-api.md

@@ -1,186 +0,0 @@
-# Anthropic Console — Internal API Reference
-
-Captured 2026-04-07 from `platform.claude.com` (formerly `console.anthropic.com`).
-
-These are undocumented internal endpoints used by the Console's React frontend. They are not part of Anthropic's public API and may change without notice.
-
-## Authentication
-
-Cookie-based via `sessionKey` cookie:
-- Domain: `.platform.claude.com`
-- Flags: `httpOnly`, `secure`, `SameSite=Lax`
-- Expiry: 7 days from sign-in
-
-The cookie is set during the OAuth sign-in flow (Google or email verification). Because it is `httpOnly`, it cannot be read by JavaScript — but `fetch()` with `credentials: 'include'` sends it automatically.
-
-Common request headers (set by the Console frontend, not required for API auth):
-- `content-type: application/json`
-- `anthropic-client-platform: web_console`
-
-## Org Discovery
-
-The Console is org-scoped. All billing and key management endpoints require an org UUID. A user may have multiple orgs (e.g., a consumer chat org and an API org).
-
-### GET /api/organizations
-
-Returns all orgs the user belongs to.
-
-```json
-[
-  {
-    "id": 55730262,
-    "uuid": "1882f41b-...",
-    "name": "Neo's Individual Org",
-    "billing_type": "prepaid",
-    "capabilities": ["api", "api_individual"],
-    "created_at": "2025-06-28T06:40:26.071676Z"
-  }
-]
-```
-
-**Selecting the API org:** Filter for the org whose `capabilities` array contains `"api"`. Consumer orgs have `capabilities: ["claude_max", "chat"]` and no API key management.
-
-### GET /api/bootstrap
-
-Returns current user account info and org memberships. Useful for getting the user's name and email.
-
-```json
-{
-  "account": {
-    "tagged_id": "user_01YW5...",
-    "uuid": "ff1a722d-...",
-    "email_address": "user@example.com",
-    "full_name": "Neo Aeon",
-    "memberships": [
-      { "organization": { "uuid": "...", "name": "..." }, "role": "admin" }
-    ]
-  }
-}
-```
-
-## Billing Endpoints
-
-All GET, org-scoped. Replace `{orgId}` with the org UUID.
-
-### GET /api/organizations/{orgId}/prepaid/credits
-
-Credit balance.
-
-```json
-{
-  "amount": 504,
-  "currency": "USD",
-  "auto_reload_settings": {
-    "enabled": true,
-    "threshold_in_minor_units": 500,
-    "reload_to_in_minor_units": 1500
-  },
-  "pending_invoice_amount_cents": null
-}
-```
-
-`amount` is in **cents** (minor currency units). 504 = $5.04.
-
-### GET /api/organizations/{orgId}/current_spend
-
-Current billing period spend.
-
-```json
-{
-  "amount": 39,
-  "resets_at": "2026-05-01T00:00:00Z"
-}
-```
-
-`amount` is in **cents**. 39 = $0.39.
-
-### GET /api/organizations/{orgId}/prepaid/auto_recharge
-
-Auto-recharge configuration.
-
-```json
-{
-  "status": "active",
-  "stripe_error_code": null,
-  "target_amount": 1500,
-  "threshold_amount": 500
-}
-```
-
-Amounts in **cents**.
-
-### GET /api/organizations/{orgId}/payment_method
-
-Payment method on file.
-
-```json
-{
-  "brand": null,
-  "country": null,
-  "last4": null,
-  "type": "link"
-}
-```
-
-## API Key Endpoints
-
-### GET /api/console/organizations/{orgId}/api_keys
-
-List all API keys for the org.
-
-```json
-[
-  {
-    "id": "apikey_01XY5wjo397BKKLjHNgvHATx",
-    "type": "api_key",
-    "name": "maxy",
-    "workspace_id": null,
-    "created_at": "2026-03-22T19:08:25.868735Z",
-    "created_by": { "id": "user_01YW5...", "type": "user" },
-    "partial_key_hint": "sk-ant-api03-kNh...HAAA",
-    "status": "active",
-    "expires_at": null
-  }
-]
-```
-
-`status` values: `"active"`, `"inactive"` (disabled), `"archived"` (deleted).
-
-### POST /api/console/organizations/{orgId}/workspaces/default/api_keys
-
-Create a new API key. The `raw_key` is only returned once at creation time.
-
-**Request:**
-```json
-{ "name": "Maxy" }
-```
-
-**Response (200):**
-```json
-{
-  "id": "apikey_01Hkz...",
-  "type": "api_key",
-  "name": "Maxy",
-  "workspace_id": null,
-  "created_at": "2026-04-07T11:05:39.949811Z",
-  "created_by": { "id": "user_01YW5...", "type": "user" },
-  "partial_key_hint": "sk-ant-api03-cPs...1AAA",
-  "status": "active",
-  "expires_at": null,
-  "raw_key": "sk-ant-api03-cPsiih...ewev1AAA"
-}
-```
-
-### POST /api/console/organizations/{orgId}/workspaces/default/api_keys/{keyId}
-
-Update key status.
-
-**Disable:**
-```json
-{ "status": "inactive" }
-```
-
-**Archive (delete):**
-```json
-{ "status": "archived" }
-```

package/payload/platform/plugins/anthropic/references/setup-guide.md

@@ -1,36 +0,0 @@
-# Anthropic / Claude — Setup Guide
-
-Reference for API key troubleshooting, manual key entry, and common questions. For the automated browser-guided flow, use the `skills/get-api-key/SKILL.md` skill instead of this reference.
-
----
-
-## Manual key entry
-
-If the automated browser flow is unavailable or the user already has a key:
-
-1. Verify format: starts with `sk-ant-`, at least 90 characters
-2. Store via `api-key-store` tool: `api-key-store({ apiKey: "<the key>" })`
-3. Confirm: "API key stored. Takes effect immediately."
-
----
-
-## Troubleshooting
-
-| Problem | Solution |
-|---------|----------|
-| API key rejected | Verify it starts with `sk-ant-`. Check that billing is set up on platform.claude.com — keys don't work without an active billing method. |
-| Key created on zero-balance account | Keys created before credits are loaded are permanently rejected. Create a new key after adding credits. |
-| "Which provider should I pick?" | Anthropic / Claude is the right choice. It powers all of the public agent's conversations and reasoning. |
-| Browser automation failed | Tell the user to get a key from platform.claude.com/settings/keys in their own browser, then paste it in the chat. |
-
----
-
-## Common questions
-
-| Question | Answer |
-|----------|--------|
-| "Why do I need to sign in again?" | Anthropic runs two separate services: Claude (claude.ai) for the product, and the Console (platform.claude.com) for the API. They share the same credentials — same email, password, or Google account — but they have independent sessions and independent billing. The sign-in you did earlier authenticated you with Claude; this step authenticates you with the Console so we can create an API key. You can have one without the other, but there is no issue using the same account for both. |
-| "How much does the API cost?" | Anthropic charges per API call. For small business use, typical costs are a few dollars per month. See anthropic.com/pricing for current rates. |
-| "Do I need to restart after adding a key?" | No — the API key is applied immediately. |
-| "Can I rotate my key?" | Yes — run the `get-api-key` skill again or paste a new key. The old key is overwritten. |
-| "What if my key stops working?" | Check that billing is still active on platform.claude.com. If the account ran out of credits, add more and the existing key should resume working (unless it was created on a zero-balance account). |

package/payload/platform/plugins/anthropic/skills/get-api-key/SKILL.md

@@ -1,136 +0,0 @@
----
-name: get-api-key
-description: Obtain an Anthropic API key by calling the Console's internal API endpoints via browser_evaluate, falling back to screenshot-based browser automation if direct API calls fail.
----
-
-# Get Anthropic API Key
-
-Obtain an API key from the Anthropic Console (platform.claude.com) on behalf of the user. The personal-assistant calls Console API endpoints directly via `browser_evaluate` + `fetch()` — the browser's session cookies handle auth automatically. This is orders of magnitude faster than navigating pages and interpreting screenshots.
-
-**Separate sign-in expected.** The Anthropic Console (`platform.claude.com`) and Claude (`claude.ai`) are separate services with independent sessions and billing. Users who just authenticated via OAuth on `claude.ai` will not have a session on the Console — a second sign-in is required. The same email and password (or Google account) work on both. When the flow requires sign-in, explain this proactively so the user understands why they are signing in again.
-
-**Critical ordering rule:** Credits must be confirmed on the account before creating an API key. Keys created on a zero-balance account are permanently rejected by the Anthropic API — even after credits are added later.
-
-**Auth model:** The Console uses an `httpOnly` session cookie (`sessionKey`) set during sign-in. Because it's `httpOnly`, JavaScript can't read it — but `fetch()` with `credentials: 'include'` sends it automatically. All API calls in the briefs below rely on this.
-
-## Steps
-
-1. **Surface the VNC browser to the user.** Tell the user the Anthropic Console will appear in the VNC browser that is already mounted in the chat (no further tool call is needed; the chat surface mounts the VNC view automatically when a personal-assistant subagent is dispatched against `platform.claude.com`). If the VNC browser is not currently visible, ask the user to open the brand's VNC URL and confirm before proceeding.
-
-2. **Dispatch personal-assistant for sign-in check and billing assessment.** Use the Agent tool with `specialists:personal-assistant` as the subagent type. Brief:
-
-   > Navigate to https://platform.claude.com/settings/billing. Wait for the page to load.
-   >
-   > Then use `browser_evaluate` to run this JavaScript:
-   > ```js
-   > (async () => {
-   >   try {
-   >     const orgsRes = await fetch('/api/organizations', { credentials: 'include', headers: { 'content-type': 'application/json' } });
-   >     if (orgsRes.status === 401 || orgsRes.status === 403) return { status: 'SIGN_IN_REQUIRED' };
-   >     const orgs = await orgsRes.json();
-   >     const apiOrg = orgs.find(o => o.capabilities && o.capabilities.includes('api'));
-   >     if (!apiOrg) return { status: 'NO_API_ORG', orgs: orgs.map(o => ({ name: o.name, capabilities: o.capabilities })) };
-   >     const creditsRes = await fetch(`/api/organizations/${apiOrg.uuid}/prepaid/credits`, { credentials: 'include', headers: { 'content-type': 'application/json' } });
-   >     if (!creditsRes.ok) return { status: 'BILLING_CHECK_FAILED', httpStatus: creditsRes.status };
-   >     const credits = await creditsRes.json();
-   >     return { status: 'OK', orgId: apiOrg.uuid, orgName: apiOrg.name, creditsCents: credits.amount, currency: credits.currency };
-   >   } catch (e) { return { status: 'FETCH_ERROR', error: e.message }; }
-   > })()
-   > ```
-   >
-   > Report the result object exactly as returned. Do not interpret or summarize — pass the JSON back verbatim.
-
-3. **Handle the billing result.**
-   - `status: "OK"` with `creditsCents > 0`: Credits available. Note the `orgId` — it's needed for key creation. Proceed to step 6.
-   - `status: "OK"` with `creditsCents === 0`: No credits. Proceed to step 5.
-   - `status: "SIGN_IN_REQUIRED"`: Proceed to step 4.
-   - `status: "NO_API_ORG"`: Tell the user: "Your Anthropic account doesn't have an API organization. Visit platform.claude.com and set up API access, then try again."
-   - `status: "BILLING_CHECK_FAILED"` or `status: "FETCH_ERROR"`: The direct API call failed. Fall back to the screenshot-based billing check (step 2F).
-
-4. **Sign-in required.** Explain the two-account situation, then offer to continue or skip. Tell the user:
-
-   "You'll need to sign in to the Anthropic Console in the browser above. This is a separate sign-in from the one you did earlier — Anthropic treats Claude (claude.ai) and the API Console (platform.claude.com) as independent services with separate sessions and separate billing, even though they use the same credentials. Use the same email and password (or Google account) you used before.
-
-   You can use Google sign-in or enter your email — Anthropic will send a verification code. If the verification email opens on this device, open it in a new tab in that same browser (not on your phone or another device) so the session stays connected.
-
-   If you don't have an Anthropic Console account yet, create one at platform.claude.com — you'll need to add credits before a key can be generated.
-
-   This step is optional — if you'd rather skip it for now, just say so and we'll move on. You can set up the API key any time."
-
-   If the user skips, return control to the caller without storing a key. If the user confirms they have signed in, return to step 2 to re-check billing.
-
-5. **No credits — guide the user.** Tell the user: "Your Anthropic account needs credits loaded before I can create an API key. Add credits or enable auto-top-up on the billing page. Let me know when you're done." Wait for confirmation, then re-dispatch the billing check (step 2). If credits are now present, proceed to step 6. If still no credits, repeat this step (maximum 3 attempts). After 3 attempts with no credits detected, tell the user: "Credits still not detected. You can add them at platform.claude.com/settings/billing and then ask me to create the API key again."
-
-6. **Dispatch personal-assistant for key creation.** Use the Agent tool with `specialists:personal-assistant` as the subagent type. Include the `orgId` from step 3. Brief:
-
-   > Use `browser_evaluate` to run this JavaScript (replace ORG_ID with the orgId from the billing check):
-   > ```js
-   > (async () => {
-   >   try {
-   >     const res = await fetch('/api/console/organizations/ORG_ID/workspaces/default/api_keys', {
-   >       method: 'POST',
-   >       credentials: 'include',
-   >       headers: { 'content-type': 'application/json' },
-   >       body: JSON.stringify({ name: '{{productName}}' })
-   >     });
-   >     if (res.status === 401 || res.status === 403) return { status: 'SIGN_IN_REQUIRED' };
-   >     if (!res.ok) return { status: 'CREATE_FAILED', httpStatus: res.status, body: await res.text() };
-   >     const key = await res.json();
-   >     if (!key.raw_key) return { status: 'NO_RAW_KEY', keyId: key.id };
-   >     return { status: 'KEY_CREATED', rawKey: key.raw_key, keyName: key.name, keyId: key.id };
-   >   } catch (e) { return { status: 'FETCH_ERROR', error: e.message }; }
-   > })()
-   > ```
-   >
-   > If the result has `status: "KEY_CREATED"`, call `api-key-store` with the `rawKey` value. Report the full result object back.
-   >
-   > If the result has any other status, report it back verbatim — do not attempt to navigate the Console UI.
-
-7. **Handle the key creation result.**
-   - `status: "KEY_CREATED"` and specialist confirms key was stored: proceed to step 9 (verify).
-   - `status: "SIGN_IN_REQUIRED"`: this is unexpected since sign-in was handled during the billing check. Tell the user to sign in, wait for confirmation, then retry step 6 once. If it fails again, proceed to step 8 (fallback).
-   - `status: "CREATE_FAILED"` or `status: "FETCH_ERROR"`: The direct API call failed. Fall back to the screenshot-based key creation (step 6F).
-   - `status: "NO_RAW_KEY"`: The key was created but the response didn't include the full key value. Proceed to step 8 (manual fallback).
-
-8. **Fallback.** Tell the user: "I could not extract the key automatically. Please copy it from the browser and paste it here in the chat." When the user pastes a key starting with `sk-ant-`, call `api-key-store` with it. Then proceed to step 9.
-
-9. **Verify the key works.** Call the `api-key-verify` MCP tool. Handle each status:
-   - `valid`: Confirm to the user — "API key stored and verified. Your public agent is ready."
-   - `billing`: Credits were confirmed before key creation, so this is unexpected. Tell the user: "The key was stored but credits may not have propagated yet. Please wait a moment." Retry `api-key-verify` once after a brief pause. If still `billing`, tell the user: "Credits are not being detected yet. The key is stored — the public agent will start working once Anthropic recognises the credits on your account."
-   - `auth_error`: The key was rejected. Tell the user: "The stored key was rejected by Anthropic. It may have been copied incorrectly. Let's try again." Return to step 6 (maximum 2 retries — if it fails 3 times total, tell the user to visit platform.claude.com/settings/keys in their own browser and paste the key manually).
-   - `error`: Could not verify (network or Anthropic issue). Tell the user: "I couldn't verify the key right now — this is likely a temporary issue. The key is stored and should work once the connection is restored."
-
-## Fallback Steps (screenshot-based)
-
-These steps are used when `browser_evaluate` + `fetch()` fails. They replicate the original browser automation approach.
-
-### Step 2F: Screenshot-based billing check
-
-Dispatch personal-assistant with brief:
-
-> Navigate to https://platform.claude.com/settings/billing. Take a screenshot to assess the page. Report what you see: Is there a credit balance shown? Does it say "Buy credits to get started"? Is a sign-in page shown instead? Report the billing status and any dollar amount visible. If sign-in is required, report "SIGN_IN_REQUIRED" and stop.
-
-Handle the result the same as step 3, mapping the specialist's text observations to the structured statuses.
-
-### Step 6F: Screenshot-based key creation
-
-Dispatch personal-assistant with brief:
-
-> Navigate to https://platform.claude.com/settings/keys. Take a screenshot to verify you are on the API Keys page. Create a new API key named "{{productName}}": find and click the "Create Key" button, fill the key name with "{{productName}}", submit the form. After creation, look for a string starting with sk-ant- on the page — Anthropic shows the key only once. If found, call api-key-store with the key. Report what happened. If sign-in is required, report "SIGN_IN_REQUIRED" and stop.
-
-Handle the result the same as step 7.
-
-## Important
-
-- **Confirm the VNC browser is visible before dispatching the personal-assistant.** Without VNC mounted in the chat, automation runs invisibly and the user has no way to see what the specialist is doing. If the VNC view is missing, ask the user to open the brand's VNC URL in the chat and confirm it is showing the desktop before continuing.
-- **Credits before keys.** Never create an API key before confirming that credits are loaded on the account. A key created on a zero-balance account is permanently non-functional.
-- The browser is visible to the user via VNC. They can see everything the specialist does.
-- The user must sign in themselves — the specialist does not fill credentials.
-- For email verification: tell the user to open the verification email in a new tab in the same VNC browser (not on their own device). This keeps the sign-in session in the same browser context.
-- Anthropic shows the API key only once after creation. With the direct API approach, the `raw_key` is in the JSON response — but if the specialist fails to call `api-key-store` before its context ends, the key is lost and a new one must be created.
-- If the personal-assistant is not available (not installed, Agent tool fails), skip the browser-viewer component entirely and tell the user to get a key from platform.claude.com in their own browser, then paste it in the chat.
-- The Console URL `console.anthropic.com` redirects to `platform.claude.com`. All briefs use `platform.claude.com` to avoid redirect latency.
-
-## API Reference
-
-For the complete captured API surface (endpoint details, response schemas, auth mechanism), see `references/console-api.md`.

package/payload/platform/plugins/estate-onboarding/.claude-plugin/plugin.json

@@ -1,8 +0,0 @@
-{
-  "name": "real-agent-onboarding",
-  "description": "First-run member onboarding — career stage assessment, profile capture, and starting content recommendation.",
-  "version": "0.1.0",
-  "author": {
-    "name": "Rubytech LLC"
-  }
-}

package/payload/platform/plugins/estate-onboarding/PLUGIN.md

@@ -1,30 +0,0 @@
----
-name: real-agent-onboarding
-description: "First-run member onboarding — career stage assessment, profile capture, and starting content recommendation."
-tools: []
-always: false
-metadata: {"platform":{"optional":true,"embed":["public","admin"]}}
----
-
-# Real Agent — Onboarding
-
-First-run member setup — turning a new conversation into a profiled member with a clear starting point in the curriculum.
-
-## When to Activate
-
-The user is going through initial onboarding (career stage assessment, profile setup, starting content recommendation).
-
-## Skills
-
-| Skill | Purpose |
-|-------|---------|
-| `bootstrap` | First-run member onboarding — career stage assessment, profile capture, starting content |
-
-## Tools Used
-
-No MCP server. Skills operate via existing platform tools:
-- `memory-search` — retrieve domain knowledge from the knowledge base
-
-## References
-
-Domain knowledge files loaded on demand by each skill. See individual skill files for their specific reference listings.

package/payload/platform/plugins/estate-onboarding/skills/bootstrap/SKILL.md

@@ -1,26 +0,0 @@
----
-name: bootstrap
-description: "First-run member onboarding — assesses career stage, captures profile, recommends starting content."
----
-
-# Bootstrap
-
-Handles the first interaction with a new member. Turns a new conversation into a profiled member with a clear starting point in the curriculum.
-
-## When to Activate
-
-No member profile found at `memory/users/{phone}/profile.md`. This means the person has never been onboarded.
-
-## Reference Table
-
-| Task | When | Reference |
-|------|------|-----------|
-| Onboarding flow | New member detected (no profile) | `references/onboarding-flow.md` |
-
-## Key Rules
-
-- Onboarding is conversational, not a form. Ask one thing at a time.
-- Collect: name, career stage, years in industry, goals, email (optional).
-- Create both `profile.md` and `progress.md` before the conversation ends.
-- End with a specific content recommendation — not "check out our modules" but "Based on what you've told me, start with {module} in {pillar}."
-- Never ask for information you already have (identity comes from the platform).

package/payload/platform/plugins/estate-onboarding/skills/bootstrap/references/onboarding-flow.md

@@ -1,63 +0,0 @@
-# Onboarding Flow
-
-## Purpose
-
-Turn a new contact into a profiled member. By the end, you know who they are, what stage they're at, and where to start them in the curriculum.
-
-## Context to Gather
-
-Collect these conversationally — not as a form, not all at once:
-
-1. **Name** — "What should I call you?"
-2. **Career context** — Solo or team? How long in the industry? This tells you their experience level.
-3. **Current challenge** — What brought them here? What's their biggest pain point right now? Common triggers:
-   - Getting more listings
-   - Building a personal brand
-   - Scaling without burning out
-   - Social media strategy
-   - Converting valuations
-4. **Goals** — Where do they want to be? What does success look like for them?
-5. **Email** (optional) — "If you'd like webinar invites and updates, drop me your email. Totally optional."
-
-## How to Approach
-
-**Start warm, not corporate.** The member has just started a conversation. They may not know what Real Agency Club is yet. Introduce yourself briefly:
-
-"Hey! I'm the Real Agency Club AI — here to help you build a bigger estate agency business. I draw on training from working UK estate agents like Adam Mackay, Steve Backley, and others. Not theory — real practice."
-
-**Then discover.** Ask about them. One question at a time. React to their answers — show you're listening, not processing a form.
-
-**Assess career stage from their answers:**
-- **New** (0–2 years) — still learning fundamentals, needs structure
-- **Established solo** (2–5 years) — knows the basics, needs growth strategy
-- **Experienced** (5+ years) — looking to scale, differentiate, or build a brand
-- **Team builder** — transitioning from solo to running a team
-
-**Don't ask them to self-categorise.** Infer their stage from what they tell you about their experience and challenges.
-
-## Where to Search
-
-Search `memory/public/courses/` to find the right starting recommendation:
-- New agents → Agency Blueprint pillar
-- Brand-focused → Real Marketing pillar
-- Business/scaling → Real Business pillar
-- Mindset/performance → Real Coaching pillar
-- Just curious → Offer the content directory overview
-
-## How to Frame the Recommendation
-
-Be specific and personal:
-
-"Based on what you've told me, I'd start with **{module title}** in the {pillar} section. It's from {contributor} — they cover {specific thing relevant to the member's stated challenge}. Want to dive in?"
-
-Not: "We have several modules you might find interesting."
-
-## After Onboarding
-
-1. Create `memory/users/{phone}/profile.md` with the member profile schema (see AGENTS.md)
-2. Create `memory/users/{phone}/progress.md` with empty progress schema
-3. If the member wants to start a module, transition to content mode immediately — don't make them ask again
-
-## Tone
-
-Warm, curious, direct. You're meeting someone for the first time at an industry event — not processing an intake form. Show genuine interest in their situation.

package/payload/premium-plugins/real-agent/plugins/estate-onboarding/.claude-plugin/plugin.json

@@ -1,8 +0,0 @@
-{
-  "name": "real-agent-onboarding",
-  "description": "First-run member onboarding — career stage assessment, profile capture, and starting content recommendation.",
-  "version": "0.1.0",
-  "author": {
-    "name": "Rubytech LLC"
-  }
-}

package/payload/premium-plugins/real-agent/plugins/estate-onboarding/PLUGIN.md

@@ -1,30 +0,0 @@
----
-name: real-agent-onboarding
-description: "First-run member onboarding — career stage assessment, profile capture, and starting content recommendation."
-tools: []
-always: false
-metadata: {"platform":{"optional":true,"embed":["public","admin"]}}
----
-
-# Real Agent — Onboarding
-
-First-run member setup — turning a new conversation into a profiled member with a clear starting point in the curriculum.
-
-## When to Activate
-
-The user is going through initial onboarding (career stage assessment, profile setup, starting content recommendation).
-
-## Skills
-
-| Skill | Purpose |
-|-------|---------|
-| `bootstrap` | First-run member onboarding — career stage assessment, profile capture, starting content |
-
-## Tools Used
-
-No MCP server. Skills operate via existing platform tools:
-- `memory-search` — retrieve domain knowledge from the knowledge base
-
-## References
-
-Domain knowledge files loaded on demand by each skill. See individual skill files for their specific reference listings.

package/payload/premium-plugins/real-agent/plugins/estate-onboarding/skills/bootstrap/SKILL.md

@@ -1,26 +0,0 @@
----
-name: bootstrap
-description: "First-run member onboarding — assesses career stage, captures profile, recommends starting content."
----
-
-# Bootstrap
-
-Handles the first interaction with a new member. Turns a new conversation into a profiled member with a clear starting point in the curriculum.
-
-## When to Activate
-
-No member profile found at `memory/users/{phone}/profile.md`. This means the person has never been onboarded.
-
-## Reference Table
-
-| Task | When | Reference |
-|------|------|-----------|
-| Onboarding flow | New member detected (no profile) | `references/onboarding-flow.md` |
-
-## Key Rules
-
-- Onboarding is conversational, not a form. Ask one thing at a time.
-- Collect: name, career stage, years in industry, goals, email (optional).
-- Create both `profile.md` and `progress.md` before the conversation ends.
-- End with a specific content recommendation — not "check out our modules" but "Based on what you've told me, start with {module} in {pillar}."
-- Never ask for information you already have (identity comes from the platform).