skills.rest
Lonsdale201
Lonsdale201COMMUNITY
Explore all skills by this author →
WebsiteGitHub

wp-presence-api

Document the WordPress Presence API's TTL-based wp_presence table and Heartbeat transport.

21|1|Updated Apr 29, 2026
Search Tags:#architecture#reference#ephemeral#presence#wordpress#heartbeat#online
One-click install
npx skills add https://github.com/Lonsdale201/wp-agent-skills --skill wp-presence-api
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wp-presence-api
Source: https://github.com/Lonsdale201/wp-agent-skills/tree/main/wordpress/wp-presence-api
Command: npx skills add https://github.com/Lonsdale201/wp-agent-skills --skill wp-presence-api

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Awareness of who is logged in, what admin screens they view, and which posts they edit, without mutating core WP tables or relying on unstable core features. This skill serves as a canonical reference for the WordPress Presence API (experimental feature plugin) and demonstrates the architectural pattern (a dedicated wp_presence table with a TTL and Heartbeat transport) to guide developers away from postmeta- or options-based presence implementations.

Core Features & Use Cases

  • Architectural pattern exposure: documents the TTL-based presence table design and Heartbeat transport as a scalable pattern for ephemeral admin state.
  • Awareness reference: helps developers verify existence, state, and intended usage against canonical sources.
  • Decision guidance: clarifies scope, stability, and production readiness for present-ping features in WP projects.

Quick Start

Inspect the canonical sources linked in the References section to understand current state and recommended usage.

Frequently Asked Questions about wp-presence-api

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

FAQPage Schema
How do I track which WordPress admin users are online without modifying core database tables?▼

To track online WordPress admin users without modifying core tables, the WordPress Presence API uses a dedicated wp_presence table with a Time-to-Live (TTL) mechanism. This pattern stores ephemeral presence state separately from core WP tables.

What is the WordPress Presence API and how does its architecture work?▼

The WordPress Presence API is an experimental feature plugin providing an awareness reference for logged-in user activity. Its architecture relies on a TTL-based wp_presence table and the WordPress Heartbeat API transport to manage ephemeral admin state.

Why should I avoid using postmeta or options for WordPress presence features?▼

Using postmeta or options for WordPress presence features creates database bloat because they are not designed for ephemeral state. A dedicated TTL-based presence table is the scalable architectural pattern recommended for tracking transient online status.

Is the WordPress Presence API ready for production use?▼

The WordPress Presence API is not ready for production adoption. Developers evaluating presence features should treat it strictly as an awareness reference and wait for core milestones before implementing the TTL-based table and Heartbeat transport pattern in live projects.

How does the WordPress Heartbeat API transport ephemeral user state?▼

The WordPress Heartbeat API transports ephemeral user state by periodically sending signals to update the TTL-based wp_presence table. This mechanism allows the WordPress Presence API to track who is logged in and what admin screens they view.

Related Skills

Explore More Software Engineering Skills→
jonathanbelolojonathanbelolo
3

composable-svelte-chat

Implement streaming chat with presence tracking for Composable Svelte apps.

Community
Advanced
pubnubpubnub
6

pubnub-presence

Monitor join, leave, timeout, and state-change events on PubNub channels.

Official
Advanced
JDHayesBCJDHayesBC
1

attention

Schedule heartbeat ticks to maintain sovereign AI presence and identity.

Community
Intermediate
myapihqmyapihq
83

my-database-api

Store JSON values in isolated namespaces with etag validation.

Official
Intermediate