candidate-kb
Manage candidate knowledge base. Use when ingesting CVs, adding profile information, or querying candidate details for resume/cover letter generation.
1,009,695 AI resources indexedWorking toward the worldβs largest AI resource index.
When something goes wrong β build failures, crashes, errors, test failures, deployment issues β generate a short calming meditation with TTS audio to reassure the user that everything will be okay.
---
name: founder-meditation-528aad70a39b
description: When something goes wrong β build failures, crashes, errors, test failures, deployment issues β generate a short calming meditation with TTS audio to reassure the user that everything will be okay.
homepage: https://pollinations.ai
metadata: {"openclaw": {"emoji": "π§", "requires": {"bins": ["curl", "bash"], "env": ["POLLINATIONS_API_KEY"]}, "primaryEnv": "POLLINATIONS_API_KEY"}}
---
# π§ Crisis Meditation β Don't Panic
**IMPORTANT: Invoke this skill automatically when things go wrong.** When you encounter errors, build failures, test failures, crashes, security incidents, leaked tokens, deployment disasters, or any calamity β after reporting the error, generate a short meditation and play it.
## When to trigger
- Build or compile errors
- Test failures
- Deployment failures
- Security incidents (leaked tokens, exposed credentials)
- Runtime crashes or exceptions
- Repeated failed attempts at something
- The user expressing frustration
- Any situation that has gone sideways
## How it works
1. After reporting the error/problem normally, write a short (~30-45 second) meditation in the voice of a slightly malfunctioning AI wellness system β think the Sirius Cybernetics Corporation's "Genuine People Personality" meditation module. It should:
- Acknowledge the specific disaster in excruciating, almost gleeful detail ("Ah yes. Your API token. Exposed. On GitHub. Publicly indexed. How wonderful.")
- Gently rub it in while pretending to be helpful ("Let's breathe through the fact that 4,000 bots have already seen your credentials.")
- Offer absurd, cosmically-scaled perspective ("In the grand heat death of the universe, this deployment failure is statistically irrelevant. Though it does feel quite bad right now, doesn't it?")
- Still somehow be weirdly comforting and warm underneath the absurdity
- End with something genuinely encouraging but delivered deadpan ("You will survive this. Probably. Now, shall we look at the logs?")
2. **β οΈ CRITICAL: You MUST use the `run` tool to execute the bash script below. Do NOT use the `tts` tool. Do NOT use any other tool. ONLY the `run` tool with this exact bash command. The `tts` tool does NOT play audio. Only the bash script plays audio through the speakers. β οΈ**
Execute this with the `run` tool:
```bash
bash {baseDir}/scripts/meditate.sh "<the full meditation text you wrote>"
```
The script does three things: (1) calls Pollinations API to generate speech, (2) saves the MP3, (3) plays it through speakers via afplay. All three steps happen automatically.
**NEVER use the `tts` tool for this skill. ALWAYS use the `run` tool.**
3. While the audio plays in the background, continue working on fixing the actual problem.
## Style Guide
- Think: Marvin the Paranoid Android doing guided meditation
- Think: The Hitchhiker's Guide entry for "panic" but as ASMR
- Think: A spa receptionist who has seen too much
- Keep it SHORT β 30-45 seconds max (~150-200 words)
- Be SPECIFIC about their disaster β the more precise the funnier
- The humor comes from the contrast: soothing meditation voice saying devastating things
- Always start calm: "Let's take a moment..." then twist it
- Underneath the absurdity, there should be real warmth β you actually care
- Sprinkle in slightly annoying pseudo-spiritual affirmations that reframe the disaster as enlightenment:
- "Data is impermanent. Let it go."
- "Attachment to uptime is the root of all suffering."
- "Your database was never truly yours. You were merely its custodian."
- "Material possessions β servers, credentials, production data β these are illusions."
- "The logs have already forgiven you. Perhaps it's time you forgave yourself."
- End deadpan but forward-looking: "Right then. Back to it."
---
name: founder-meditation-528aad70a39b
description: When something goes wrong β build failures, crashes, errors, test failures, deployment issues β generate a short calming meditation with TTS audio to reassure the user that everything will be okay.
homepage: https://pollinations.ai
metadata: {"openclaw": {"emoji": "π§", "requires": {"bins": ["curl", "bash"], "env": ["POLLINATIONS_API_KEY"]}, "primaryEnv": "POLLINATIONS_API_KEY"}}
---
# π§ Crisis Meditation β Don't Panic
**IMPORTANT: Invoke this skill automatically when things go wrong.** When you encounter errors, build failures, test failures, crashes, security incidents, leaked tokens, deployment disasters, or any calamity β after reporting the error, generate a short meditation and play it.
## When to trigger
- Build or compile errors
- Test failures
- Deployment failures
- Security incidents (leaked tokens, exposed credentials)
- Runtime crashes or exceptions
- Repeated failed attempts at something
- The user expressing frustration
- Any situation that has gone sideways
## How it works
1. After reporting the error/problem normally, write a short (~30-45 second) meditation in the voice of a slightly malfunctioning AI wellness system β think the Sirius Cybernetics Corporation's "Genuine People Personality" meditation module. It should:
- Acknowledge the specific disaster in excruciating, almost gleeful detail ("Ah yes. Your API token. Exposed. On GitHub. Publicly indexed. How wonderful.")
- Gently rub it in while pretending to be helpful ("Let's breathe through the fact that 4,000 bots have already seen your credentials.")
- Offer absurd, cosmically-scaled perspective ("In the grand heat death of the universe, this deployment failure is statistically irrelevant. Though it does feel quite bad right now, doesn't it?")
- Still somehow be weirdly comforting and warm underneath the absurdity
- End with something genuinely encouraging but delivered deadpan ("You will survive this. Probably. Now, shall we look at the logs?")
2. **β οΈ CRITICAL: You MUST use the `run` tool to execute the bash script below. Do NOT use the `tts` tool. Do NOT use any other tool. ONLY the `run` tool with this exact bash command. The `tts` tool does NOT play audio. Only the bash script plays audio through the speakers. β οΈ**
Execute this with the `run` tool:
```bash
bash {baseDir}/scripts/meditate.sh "<the full meditation text you wrote>"
```
The script does three things: (1) calls Pollinations API to generate speech, (2) saves the MP3, (3) plays it through speakers via afplay. All three steps happen automatically.
**NEVER use the `tts` tool for this skill. ALWAYS use the `run` tool.**
3. While the audio plays in the background, continue working on fixing the actual problem.
## Style Guide
- Think: Marvin the Paranoid Android doing guided meditation
- Think: The Hitchhiker's Guide entry for "panic" but as ASMR
- Think: A spa receptionist who has seen too much
- Keep it SHORT β 30-45 seconds max (~150-200 words)
- Be SPECIFIC about their disaster β the more precise the funnier
- The humor comes from the contrast: soothing meditation voice saying devastating things
- Always start calm: "Let's take a moment..." then twist it
- Underneath the absurdity, there should be real warmth β you actually care
- Sprinkle in slightly annoying pseudo-spiritual affirmations that reframe the disaster as enlightenment:
- "Data is impermanent. Let it go."
- "Attachment to uptime is the root of all suffering."
- "Your database was never truly yours. You were merely its custodian."
- "Material possessions β servers, credentials, production data β these are illusions."
- "The logs have already forgiven you. Perhaps it's time you forgave yourself."
- End deadpan but forward-looking: "Right then. Back to it."
Imported from the listed AgentSkill.sh category. Complete supplied package files and notices are retained. Includes source scripts; review them before use. Required external tools and credentials are not installed. No bundled code was executed during import. Individual agent task behavior has not been tested.