agentleFS
Sign inStart free
Itsokay-coItsokay-co/bio-vibing/skills/connect/SKILL.md

connect

Skill17 starsChanged 8 months agoApache-2.0View on GitHub

Test wearable API connection and show available data. Use when the user wants to verify their setup or see what data is accessible. Currently supports Oura Ring, Whoop, Fitbit, and Apple Health.

  • Reads credentials

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 52 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Test the wearable API connection and report what data is available.

    line 13

“Common” is measured: kept by at least 6 in 10 of the 52 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Connect

Test the wearable API connection and report what data is available.

Steps

  1. Detect which wearable is configured and test the connection:
python3 << 'PYEOF'
import sys, os
sys.path.insert(0, os.path.join(os.environ.get('CLAUDE_PLUGIN_ROOT', '.'), 'lib'))
from providers import detect_provider, get_provider, list_configured_providers, PROVIDERS

# Show detection result
configured = list_configured_providers()
if not configured:
    env_vars = [f"  {v['env']} ({k})" for k, v in PROVIDERS.items()]
    print("ERROR: No wearable configured.")
    print("Set one of these environment variables:")
    print("\n".join(env_vars))
    sys.exit(1)

active = detect_provider()
print(f"Detected provider: {active}")
if len(configured) > 1:
    print(f"All configured: {', '.join(configured)}")
    print(f"(Override with BIOMETRIC_PROVIDER env var)")

# Test connection
provider = get_provider(active)
result = provider.test_connection()

if not result["connected"]:
    print(f"\nERROR: Connection failed — {result['info']}")
    sys.exit(1)

print(f"\nConnected to {active}")
print(f"  {result['info']}")

# Check available data
from datetime import datetime, timedelta
end = datetime.now().strftime("%Y-%m-%d")
start = (datetime.now() - timedelta(days=365)).strftime("%Y-%m-%d")

print(f"\nAvailable data:")
counts = provider.fetch_available_data(start, end)
for endpoint, count in counts.items():
    print(f"  {endpoint.replace('_', ' ').title()}: {count} records")

# Fetch user profile
profile = provider.fetch_user_profile()
if profile:
    parts = []
    if profile.age: parts.append(f"{profile.age}y")
    if profile.biological_sex: parts.append(profile.biological_sex)
    if profile.weight_kg: parts.append(f"{profile.weight_kg}kg")
    if profile.height_m: parts.append(f"{profile.height_m}m")
    if parts:
        print(f"\nUser: {', '.join(parts)}")

print(f"\nReady to biohack.")
PYEOF

Output Format

Present the results as:

Detected provider: [provider]

Connected to [provider]
  [user info]

Available data:
  Sleep:     [N] records
  Readiness: [N] records
  Activity:  [N] records
  Stress:    [N] records

User: [age]y, [sex], [weight]kg

Ready to biohack.

Download now (ZIP)

  • Other versions60 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use connect-apps, skill-share and 10 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • ArogyaReddySkill

      connect-apps

      Connect Claude to external apps like Gmail, Slack, GitHub. Use this skill when the user wants to send emails, create issues, post messages, or take actions in external services.

      Also in 19 projects that use this

    • ArogyaReddySkill

      skill-share

      A skill that creates new Claude skills and automatically shares them on Slack using Rube for seamless team collaboration and skill discovery.

      Also in 17 projects that use this

    • ComposioHQSkill

      agent-deep-links

      Build, validate, and troubleshoot deep links for Codex, Cursor, VS Code, Visual Studio, and similar tools. Use when users ask for clickable links (especially in Slack) that open threads, files, folders, or app settings.

      Also in 3 projects that use this

    • ComposioHQSkill

      helium-mcp

      Search real-time news with bias scoring, get live stock/ETF/crypto data with AI analysis, ML options pricing, balanced news synthesis, and meme search via the Helium MCP server.

      Also in 3 projects that use this

    • trendinuxSkill

      twitter-algorithm-optimizer

      Analyze and optimize tweets for maximum reach using Twitter's open-source algorithm insights. Rewrite and edit user tweets to improve engagement and visibility based on how the recommendation system ranks content.

      Also in 12 projects that use this

    • LangChainSkill

      langsmith-fetch

      Fetches LangSmith traces for debugging agent behavior. Use when troubleshooting agent issues, reviewing conversation history, or investigating tool calls.

      Also in 18 projects that use this

    • +1 more from ComposioHQ
    • +5 more from ArogyaReddy
  • In this repository7 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free