attributes

Propagates attribute additions or renames across event modeling board elements following inbound dependencies.

Updated Aug 10, 2026
One-click install
npx skills add https://github.com/Powerworks/Underwriting --skill attributes-powerworks
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: attributes
Source: https://github.com/Powerworks/Underwriting/tree/main/agentic-modeling/.claude/skills/attributes
Command: npx skills add https://github.com/Powerworks/Underwriting --skill attributes-powerworks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually updating an attribute across every element in an event modeling chain is tedious and error-prone. This Skill automates adding or renaming an attribute from a target cell back to a source cell, ensuring consistency across commands, events, and read models on an eventmodelers board. ## Core Features & Use Cases - Chain Traversal: Walks backwards from a target cell to a source cell by following inbound node edges, with a column-based fallback when edges are missing. - Add or Rename Operations: Adds a new field with a standard schema to each node's meta.fields, or renames an existing field while preserving all other properties. - Safe Execution: Skips nodes where the field already exists or is not found, verifies HTTP 200 on each update, and stops with a report on failure. - Use Case: You renamed customerId to clientId in your read model and need the same rename applied to the upstream event and command. Provide the target cell, source cell, and old/new names, and the Skill updates every element in the chain. ## Quick Start Rename the attribute customerId to clientId across the chain from cell B2 back to cell A2 on my event modeling board.

Frequently Asked Questions about attributes

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

FAQPage Schema
How do I rename an attribute across an event modeling chain?▼

Provide the target cell, source cell, the old attribute name, and the new name. The Skill walks backwards through inbound dependencies from target to source and renames the matching field in each node's meta.fields, skipping nodes where the field is not found.

How do I add a new attribute to all elements on an eventmodelers board?▼

Specify the target cell, source cell, and the new attribute name. The Skill appends a field with default properties (String type, Single cardinality) to every node in the dependency chain, skipping nodes that already contain a field with that name.

What happens if a node has no dependency edges?▼

The Skill falls back to column-based layout inference. It uses the standard event modeling pattern where read models connect to events in the same column, events to commands in the same column, and commands to read models in the previous column.

Is there a limit to how many nodes the chain traversal follows?▼

Yes, traversal stops after visiting 20 nodes as a safety limit, and the Skill warns you if this limit is hit. It also stops when it reaches the source node or when no more inbound nodes exist.

What happens if an update to a node fails?▼

The Skill verifies an HTTP 200 response after each node:changed event. If a node update fails, it reports the error and stops immediately rather than continuing with partial changes to the remaining chain.