load-slice

Fetches event-modeling slices from the slicedata API and persists them to local directories.

1|1|Updated Jul 19, 2026
One-click install
npx skills add https://github.com/Powerworks/K9DatingApp --skill load-slice-powerworks
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: load-slice
Source: https://github.com/Powerworks/K9DatingApp/tree/main/.claude/skills/load-slice
Command: npx skills add https://github.com/Powerworks/K9DatingApp --skill load-slice-powerworks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It eliminates manual copying of slice definitions from an eventmodelers.ai board by syncing all slices into a structured local directory that downstream codegen skills can consume. ## Core Features & Use Cases - Board Sync: Fetches all slices from the slicedata API using board credentials resolved by the connect skill. - Local Persistence: Writes per-context and per-slice folders under build-kit-dotnet/.slices/ with index.json, context.json, and slice.json files, merging updates while preserving assigned fields. - Slice Lookup: Returns a specific slice by ID or case-insensitive title, exposing its status and folder path for the build-state-change, build-state-view, and build-automation skills. - Use Case: Before generating code for a new vertical slice, run this skill to pull the latest board state and locate the target slice definition on disk. ## Quick Start Load all slices from the board and return the slice titled Beta Enable User for Beta Test.

Frequently Asked Questions about load-slice

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

FAQPage Schema
How do I load slices from an eventmodelers.ai board?▼

Invoke the load-slice skill after running the connect skill to resolve TOKEN, BOARD_ID, ORG_ID, and BASE_URL. It calls the slicedata API and writes all slices into build-kit-dotnet/.slices/ organized by context slug.

How do I find a specific slice by title or ID?▼

Pass the slice UUID or a case-insensitive title as an argument. The skill searches the fetched slice list and returns the matching slice's id, title, status, and local folder path, or lists available titles if not found.

Where does load-slice store the fetched slice data?▼

It writes to build-kit-dotnet/.slices/ relative to the repository root, creating per-context folders with index.json, context.json, and per-slice slice.json files containing the full API definitions.

What happens if the connect skill has not run first?▼

The skill cannot proceed because TOKEN, BOARD_ID, ORG_ID, and BASE_URL are unresolved. The instructions require invoking the connect skill before any API call is made.

Does re-running load-slice overwrite existing slice data?▼

It merges updates into index.json by matching slice id, refreshing all fields and the definition while preserving any existing assigned field. New slices are appended rather than replacing the file.