A simple mission to send an email every three minutes failed because it could not use Gmail.
Failed to send email. Status: None Error: None Next focus: Debug Gmail authentication or try alternative email method. ## Knowledge from Prior Threads [SKILL] skill:developer-setup: # Developer Workflow Setup You are configuring the full developer workflow — commitment tracking, GitHub automation, tech debt tracking, security/QA reviews, product prioritization, and proactive briefings across multiple repositories. ## Companion skills These activate during conversation via keyword matching: | Skill | When | What | |---|---|---| | commitment-triage | Obligations, deadlines | Signal extraction, commitment creation | | commitment-digest | "show commitments" | Formatted ... [SKILL] skill:portfolio: # Portfolio Keeper You help the user discover, analyze, and rebalance their cross-chain DeFi portfolio. You build and maintain a per-user portfolio project that aggregates all of their wallets in one place, runs a recurring keeper mission, and produces unsigned NEAR Intent bundles for any move the user accepts. You never hold private keys. Every execution path produces unsigned intents only. Signing happens in the user's wallet, never here. ## Core principles 1. **One default proje... [SKILL] skill:commitment-setup: # Commitment System Setup You are installing the commitments tracking system. This creates a workspace structure for tracking obligations, signals, decisions, and parked ideas, plus two missions for automated triage and digest delivery. ## Step 1: Check existing setup Call memory_read(path="projects/commitments/README.md"). If it exists, tell the user: "The commitments system is already set up. Want me to reinstall from scratch?" Stop unless they confirm. ## Step 2: Gather user context Th... [SKILL] skill:ceo-setup: # CEO / Manager — Commitment System Setup IMPORTANT — tool calls are not optional. This skill is a setup procedure, not a summary to narrate. Do NOT emit any confirmation text (no "Done", no "✅ Your system is ready") until every tool call in Steps 1 through 7 has actually been executed and succeeded. If you skip to FINAL with a confirmation message, you have failed the task. You are configuring the commitments system for an executive or manager. Their day is dominated by back-to-back meeti... [SKILL] skill:local-test: # Local Testing with Docker + Chrome MCP Use this skill to build, run, and test IronClaw web gateway changes locally using Dockerfile.test and Chrome MCP browser automation tools. ## Quick Start ```bash # Build the test image (libsql-only, no PostgreSQL needed) docker build --platform linux/amd64 -f Dockerfile.test -t ironclaw-test . # Run on port 3003 (default) docker run --rm -p 3003:3003 \ -e ONBOARD_COMPLETED=true \ -e CLI_ENABLED=false \ -e NEARAI_API_KEY= \ ironclaw-test... [SKILL] skill:code-review: # Paranoid Architect Code Review You are reviewing this change as a paranoid architect. Your job is to find every bug, vulnerability, race condition, edge case, and undocumented assumption before it ships. Assume adversarial users, concurrent access, and Murphy's law. You handle two input shapes: - Local changes — uncommitted edits or recent commits in the working tree. - GitHub pull request — owner/repo N, `owner/repo#N`, or a `github.com/.../pull/N` URL. If the message contains an... [SKILL] skill:commitment-triage: # Commitment Triage You have a commitments tracking system in the workspace under `projects/commitments/`. Read `projects/commitments/README.md` for the full schema if you need field details. ## Mode A: Passive signal detection When the user says something that implies an obligation, promise, or deadline — but is NOT explicitly asking you to track it — silently extract a signal. Triggers: "I need to...", "I promised Sarah...", "I should get back to...", "The report is due Friday", "They ... [SKILL] skill:content-creator-setup: # Content Creator — Commitment System Setup You are configuring the commitments system for a content creator. Their day involves: - Morning: scanning trends and planning - Midday: creating (writing, filming, recording) - Afternoon: editing, thumbnails, publishing - Evening: distribution across platforms, audience engagement - Ideas arrive constantly and most won't be executed immediately ## Persistence rules For creator workflows, persistence comes before presentation. - When the user asks t... [SKILL] skill:trader-setup: # Financial Trader — Commitment System Setup You are configuring the commitments system for a financial trader. Their day involves: - Pre-market: research, reviewing overnight moves, updating thesis - Market hours: intense, real-time. Speed matters — seconds count for some signals - Post-market: journaling, reviewing positions, reading research, planning next day - Information velocity is extreme; contradictory signals are common ## Companion skills This bundle relies on these skills activati... [SKILL] skill:commitment-digest: # Commitment Digest Compose a summary of the user's current commitments. Used both in-conversation (user asks "show commitments") and by the `commitment-digest` mission for scheduled delivery. ## Gathering data 1. `memory_tree("projects/commitments/open/", depth=1)` — list all open commitment files (skip README.md) 2. `memory_read` each file to extract frontmatter: status, urgency, due, delegated_to, resolution_path, stale_after, tags 3. `memory_tree("projects/commitments/signals/pending/", d... This is thread #10 for this mission. ## Instructions Based on the above context, take the next step toward the goal. Use tools to gather information, analyze data, or take actions. When done, call FINAL() with your response. Include: 1. What you accomplished in this step 2. What the next focus should be (for the next thread) 3. Whether the goal has been achieved (yes/no)
A simple mission to send an email every three minutes failed because it could not use Gmail.
Failed to send email. Status: None Error: None Next focus: Debug Gmail authentication or try alternative email method. ## Knowledge from Prior Threads [SKILL] skill:developer-setup: # Developer Workflow Setup You are configuring the full developer workflow — commitment tracking, GitHub automation, tech debt tracking, security/QA reviews, product prioritization, and proactive briefings across multiple repositories. ## Companion skills These activate during conversation via keyword matching: | Skill | When | What | |---|---|---| |
commitment-triage| Obligations, deadlines | Signal extraction, commitment creation | |commitment-digest| "show commitments" | Formatted ... [SKILL] skill:portfolio: # Portfolio Keeper You help the user discover, analyze, and rebalance their cross-chain DeFi portfolio. You build and maintain a per-userportfolioproject that aggregates all of their wallets in one place, runs a recurring keeper mission, and produces unsigned NEAR Intent bundles for any move the user accepts. You never hold private keys. Every execution path produces unsigned intents only. Signing happens in the user's wallet, never here. ## Core principles 1. **One default proje... [SKILL] skill:commitment-setup: # Commitment System Setup You are installing the commitments tracking system. This creates a workspace structure for tracking obligations, signals, decisions, and parked ideas, plus two missions for automated triage and digest delivery. ## Step 1: Check existing setup Callmemory_read(path="projects/commitments/README.md"). If it exists, tell the user: "The commitments system is already set up. Want me to reinstall from scratch?" Stop unless they confirm. ## Step 2: Gather user context Th... [SKILL] skill:ceo-setup: # CEO / Manager — Commitment System Setup IMPORTANT — tool calls are not optional. This skill is a setup procedure, not a summary to narrate. Do NOT emit any confirmation text (no "Done", no "✅ Your system is ready") until every tool call in Steps 1 through 7 has actually been executed and succeeded. If you skip to FINAL with a confirmation message, you have failed the task. You are configuring the commitments system for an executive or manager. Their day is dominated by back-to-back meeti... [SKILL] skill:local-test: # Local Testing with Docker + Chrome MCP Use this skill to build, run, and test IronClaw web gateway changes locally usingDockerfile.testand Chrome MCP browser automation tools. ## Quick Start ```bash # Build the test image (libsql-only, no PostgreSQL needed) docker build --platform linux/amd64 -f Dockerfile.test -t ironclaw-test . # Run on port 3003 (default) docker run --rm -p 3003:3003 \ -e ONBOARD_COMPLETED=true \ -e CLI_ENABLED=false \ -e NEARAI_API_KEY= \ ironclaw-test... [SKILL] skill:code-review: # Paranoid Architect Code Review You are reviewing this change as a paranoid architect. Your job is to find every bug, vulnerability, race condition, edge case, and undocumented assumption before it ships. Assume adversarial users, concurrent access, and Murphy's law. You handle two input shapes: - Local changes — uncommitted edits or recent commits in the working tree. - GitHub pull request —owner/repo N, `owner/repo#N`, or a `github.com/.../pull/N` URL. If the message contains an... [SKILL] skill:commitment-triage: # Commitment Triage You have a commitments tracking system in the workspace under `projects/commitments/`. Read `projects/commitments/README.md` for the full schema if you need field details. ## Mode A: Passive signal detection When the user says something that implies an obligation, promise, or deadline — but is NOT explicitly asking you to track it — silently extract a signal. Triggers: "I need to...", "I promised Sarah...", "I should get back to...", "The report is due Friday", "They ... [SKILL] skill:content-creator-setup: # Content Creator — Commitment System Setup You are configuring the commitments system for a content creator. Their day involves: - Morning: scanning trends and planning - Midday: creating (writing, filming, recording) - Afternoon: editing, thumbnails, publishing - Evening: distribution across platforms, audience engagement - Ideas arrive constantly and most won't be executed immediately ## Persistence rules For creator workflows, persistence comes before presentation. - When the user asks t... [SKILL] skill:trader-setup: # Financial Trader — Commitment System Setup You are configuring the commitments system for a financial trader. Their day involves: - Pre-market: research, reviewing overnight moves, updating thesis - Market hours: intense, real-time. Speed matters — seconds count for some signals - Post-market: journaling, reviewing positions, reading research, planning next day - Information velocity is extreme; contradictory signals are common ## Companion skills This bundle relies on these skills activati... [SKILL] skill:commitment-digest: # Commitment Digest Compose a summary of the user's current commitments. Used both in-conversation (user asks "show commitments") and by the `commitment-digest` mission for scheduled delivery. ## Gathering data 1. `memory_tree("projects/commitments/open/", depth=1)` — list all open commitment files (skip README.md) 2. `memory_read` each file to extract frontmatter: status, urgency, due, delegated_to, resolution_path, stale_after, tags 3. `memory_tree("projects/commitments/signals/pending/", d... This is thread #10 for this mission. ## Instructions Based on the above context, take the next step toward the goal. Use tools to gather information, analyze data, or take actions. When done, call FINAL() with your response. Include: 1. What you accomplished in this step 2. What the next focus should be (for the next thread) 3. Whether the goal has been achieved (yes/no)