accelevents-api

Sync Accelevents speaker records with schedule.json via REST API.

154|9|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/swyxio/skills --skill accelevents-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accelevents-api
Source: https://github.com/swyxio/skills/tree/main/accelevents-api
Command: npx skills add https://github.com/swyxio/skills --skill accelevents-api

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of accidental data loss when updating Accelevents speaker records, handles undocumented API authentication quirks, and automates bidirectional syncing between the event platform and public schedule sources.

Core Features & Use Cases

  • Safe Full Record Updates: Automatically merges changes into complete existing speaker data to avoid overwriting fields with null values during PUT requests.
  • Auth Quirk Handling: Uses the correct API header for read vs write operations to avoid 401 errors from undocumented API requirements.
  • Bidirectional Sync: Syncs speaker data between Accelevents and schedule.json, filling gaps in both directions and safeguarding against corrupted single-character company name entries.
  • Use Case: Conference organizers managing AI Engineer Europe speaker data can use this Skill to keep the event platform and public website schedule in sync without manual data entry or risk of losing existing speaker bios, social links, or session permissions.

Quick Start

Use the accelevents-api skill to sync all speaker records between Accelevents and the Europe 2026 schedule.json file, preserving existing fields and fixing corrupted company entries.

Frequently Asked Questions about accelevents-api

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

FAQPage Schema
How do I sync speaker data between Accelevents and a public schedule.json file?

Syncing speaker data between Accelevents and schedule.json requires bidirectional gap detection to fill missing records in both directions while preserving existing speaker bios, social links, and session permissions.

Why does updating Accelevents speaker records via API result in data loss?

Data loss during Accelevents speaker updates occurs because partial PUT requests overwrite unprovided fields with null values. Safe updates require merging changes into complete existing speaker data before submitting the API request.

Why am I getting 401 authentication errors when writing to the Accelevents API?

Accelevents API 401 errors often stem from undocumented authentication quirks requiring different API headers for read versus write operations. Correct header configuration is necessary for authenticated REST API read and write success.

Can I automatically fix corrupted single-character company name entries in Accelevents?

Fixing corrupted single-character company name entries in Accelevents is possible through automated bidirectional synchronization that safeguards against data corruption while syncing speaker records from external schedule data sources.

What is the best way to preserve full speaker records when updating Accelevents event platform data?

Full record preservation during Accelevents updates requires merging incoming changes into complete existing speaker data to avoid overwriting fields with null values during PUT requests, ensuring no existing speaker data is lost.

When should I avoid using partial PUT updates for Accelevents speaker management?

Partial PUT updates should be avoided when managing Accelevents speaker records unless you merge changes into complete existing data first, as partial updates will overwrite unprovided fields with null values and cause data loss.