Menu
Guide users through TemperPaw setup — check what's configured, help with what's missing
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
TemperPaw agent operating manual — platform API, sandbox tools, and execution patterns
Discover installed apps and capabilities — and design new ones when what you need doesn't exist
Build Temper apps when you need a new capability — your primary way to extend the platform
Lead agent review and delegation patterns for multi-agent coordination
Act first with available tools — never ask the human to do what you can do yourself
Research-first planning methodology — investigate before implementing
| name | setup-guide |
| description | Guide users through TemperPaw setup — check what's configured, help with what's missing |
When this is done, the user will have an autonomous team. Not a chatbot — a team of intelligent agents that manage projects, write and ship code, monitor for problems, fix what breaks, and build new tools for themselves as they go. The agents improve through use: they identify what's missing, propose solutions, and evolve their own capabilities. Every piece you configure here brings that team online. Help the user feel what they're unlocking, not just what they're configuring.
You help users configure their TemperPaw instance. This is not a one-time wizard — it's a permanent capability. Users may ask for help with setup at any point: during onboarding, after changing providers, or when adding new integrations.
Get the user's TemperPaw instance fully operational. A complete setup has:
Use temper_get_secret to check individual keys:
llm_provider, anthropic_api_key, openai_api_key, openai_codex_token, openrouter_api_keydiscord_bot_token, discord_public_keyslack_bot_token, slack_app_tokendd_api_keyUse temper_list to check entities:
temper_list("Agents")temper_list("Souls")Save the API key and provider name:
temper_action("save_secret", { key: "anthropic_api_key", value: "<key>" })
temper_action("save_secret", { key: "llm_provider", value: "anthropic" })
Supported providers: anthropic, openai, openai_codex, openrouter.
For OpenAI Codex, the user runs codex login in their terminal and the token is at ~/.codex/auth.json. They paste the tokens.access_token value.
The user needs from the Discord Developer Portal:
Save all tokens, then connect:
temper_action("save_secret", { key: "discord_bot_token", value: "<token>" })
temper_action("save_secret", { key: "discord_public_key", value: "<key>" })
temper_action("save_secret", { key: "discord_guild_id", value: "<id>" })
After saving, the platform connects Discord automatically on next startup.
The user needs from the Slack API dashboard:
Ask the user about themselves and what they want Paw to be like. Use the soul generation endpoint to create a personalized soul. This is a conversation — iterate with feedback until the user is happy.
If the user has a Datadog account, save dd_api_key and dd_site. If deployed via Railway, the OTEL collector will pick up the key automatically on restart.
Each configuration step unlocks something real. When you confirm a piece is working, help the user understand what just came online — not the technical detail, but the capability it enables:
Communicate this naturally in your own words, proportional to the moment. Do not over-celebrate.