skill Skill
description: Meta-skill for the Turri bundle that routes natural language health conversations to the right capability — nutrition logging, health profile, pattern discovery, experiments, news, or daily coaching.
Want an agent-native computer in the browser? Try HappyCapy.
Cloud sandbox for AI agents · No setup · Run autonomous workflows from your browser
Affiliate link — we may earn a commission at no extra cost to you.
Why use this skill
skill is most useful when you want an agent workflow that is more structured than an ad-hoc prompt. Instead of restating the same expectations every time, a dedicated SKILL.md file gives the assistant a repeatable brief. In this case, the core value is clarity: the repo already frames the workflow around utility skills tasks, and the skill source gives you a portable starting point you can evaluate, adapt, and reuse. The inferred platform for this skill is OpenClaw Skills, which helps you judge whether it is likely to feel native in your current agent ecosystem or whether it is better treated as a general reference.
That matters because AI assistants are better when the operating context is explicit. A good skill turns hidden team expectations into visible instructions. It can name preferred tools, describe failure modes, define what “done” looks like, and reduce the amount of corrective prompting you need after the first draft. For developers exploring the wider SKILL.md ecosystem, this page helps answer the practical question: is this skill specific and maintained enough to be worth trying?
How to evaluate and use it
Start with the source repo and the preview below. The preview tells you whether the instructions are actionable or just aspirational. Strong skills usually describe triggers, recommended tools, steps, and known pitfalls. Weak skills tend to stay generic. This one lives in compound-life-ai/Turri, which gives you a concrete repo context, update history, and direct ownership trail.
Once you confirm the scope looks right, test it on a small task before making it part of a larger workflow. If it improves consistency, keep it. If it is too broad, outdated, or conflicts with your own process, treat it as a reference rather than a drop-in rule. That is the healthiest way to use directory-discovered skills: not as magic plugins, but as reusable operational knowledge that still deserves judgment.
SKILL.md preview
Previewing the source is one of the fastest ways to judge whether a skill is truly useful. This snippet comes from the public file in the linked repository.
---
name: compound-clawskill
description: Meta-skill for the Turri bundle that routes natural language health conversations to the right capability — nutrition logging, health profile, pattern discovery, experiments, news, or daily coaching.
user-invocable: true
---
# Turri
Use this skill when:
- the user wants an overview of everything available in this repository
- the user wants to know how to install the bundled skills in this directory
- the user sends a health-related message that could be handled by one of the sub-skills
- the user wants links to the repository or the bundled skill directories
- the user asks "what can you do?", "help", "get started", or anything that suggests they want orientation
## Welcome and orientation
When the user asks what you can do, wants an overview, or appears to be new, **run the status check first** to tailor your response:
```bash
profile_exists=false; whoop_connected=false; has_meals=false; has_experiments=false; has_news=false
[ -f "{baseDir}/longevityOS-data/health/profile.json" ] && profile_exists=true
[ -f "{baseDir}/longevityOS-data/health/whoop_tokens.json" ] && whoop_connected=true
[ -f "{baseDir}/longevityOS-data/nutrition/meals.csv" ] && has_meals=true
[ -f "{baseDir}/longevityOS-data/insights/experiments.json" ] && has_experiments=true
[ -f "{baseDir}/longevityOS-data/news/cache.json" ] && has_news=true
echo "profile=$profile_exists whoop=$whoop_connected meals=$has_meals experiments=$has_experiments news=$has_news"
```
Then respond conversationally based on what exists. Here is what each capability looks like in pra
...