join-step-counter-tasker

Fetch Pixel step counts via Tasker and Join webhook payloads.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/gevrey/openclaw_backup --skill join-step-counter-tasker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: join-step-counter-tasker
Source: https://github.com/gevrey/openclaw_backup/tree/main/skills/join-step-counter-tasker
Command: npx skills add https://github.com/gevrey/openclaw_backup --skill join-step-counter-tasker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Read Google Pixel step count via Tasker+Join webhook, similar to GPS flow. Use when user asks for pedometer/steps from phone, fresh step pull, last known steps, or setup of Tasker webhook for steps.

Core Features & Use Cases

  • Automates retrieval of live or recent Pixel steps via Tasker and a local webhook hub.
  • Maintains latest and historical data in local files: latest.json and events.jsonl under data/webhooks/join-steps.
  • Supports a simple one-time webhook route initialization and a command-based workflow to fetch and store payloads.

Quick Start

Run the get command to trigger Tasker and wait for a fresh payload to be written to data/webhooks/join-steps/latest.json.

Frequently Asked Questions about join-step-counter-tasker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fetch Google Pixel step counts using Tasker and Join?

To fetch Google Pixel step counts, trigger the get command to instruct Tasker and Join to transmit the latest pedometer payload via webhook, which is then stored locally in latest.json.

Do I need a secret token and local webhook route to pull Pixel pedometer data?

Yes, pulling Pixel pedometer data requires configuring a local webhook route, a secret token, and a registered device to receive and authenticate the Join payload securely.

What is the best way to automate retrieving live step data from an Android phone?

Automating live step data retrieval involves coordinating Tasker on Android with the Join webhook hub to push fresh pedometer payloads directly to your local storage files.

Where are Pixel step count payloads stored after the Join webhook receives them?

Pixel step count payloads are written to local storage, maintaining the most recent data in latest.json and recording historical events in events.jsonl under the join-steps directory.

Can I get last known steps from my phone if a fresh Tasker webhook pull fails?

Yes, the system supports retrieving the last known steps by reading the existing payload stored in latest.json, ensuring pedometer data availability even if a fresh Tasker trigger fails.

Why does my Tasker Join webhook setup for Android step counts require initialization?

A one-time webhook route initialization is required to establish the local endpoint and configure the device connection, enabling Tasker to successfully push step count payloads via Join.