add-agent-property
Add a new property to the AI agents database. Use when the user wants to add, create, or introduce a new column, property, field, or feature to track across all agents in the comparison matrix. Handles all four required steps - database updates, groups.json, table display, and GitHub issue templates.
Best use case
add-agent-property is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Add a new property to the AI agents database. Use when the user wants to add, create, or introduce a new column, property, field, or feature to track across all agents in the comparison matrix. Handles all four required steps - database updates, groups.json, table display, and GitHub issue templates.
Teams using add-agent-property should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/add-agent-property/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How add-agent-property Compares
| Feature / Agent | add-agent-property | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Add a new property to the AI agents database. Use when the user wants to add, create, or introduce a new column, property, field, or feature to track across all agents in the comparison matrix. Handles all four required steps - database updates, groups.json, table display, and GitHub issue templates.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Add Agent Property
Add a new property to the agents board by modifying four files in sequence.
**Schema reference:** See [references/schema.md](references/schema.md) for data structures.
## Workflow
### 1. Gather Property Details
Ask the user for:
- **Property key** (camelCase, e.g., `contextWindow`)
- **Display label** (short, e.g., "Context Window")
- **Tooltip description** (1 sentence explaining the property)
- **Cell type**: `badge` (yes/no/partial) or `text` (free-form)
- **Group**: `identity`, `packaging`, or `features`
### 2. Update agents-detailed.json
Add the property to **every agent** in `src/data/agents-detailed.json`:
```json
"propertyKey": {
"value": null,
"detail": null
}
```
Insert after the last feature property, before `additionalInfo`.
### 3. Update groups.json
Add the property key to the appropriate group's `columns` array in `src/data/groups.json`:
```json
{
"id": "features",
"label": "Features",
"columns": ["existingProp", "propertyKey"]
}
```
### 4. Update AgentTable.jsx
Add column definition to the `columns` array in `src/components/AgentTable.jsx`:
```javascript
{ key: 'propertyKey', label: 'Label', sortable: true, cellType: 'badge', tooltip: 'Description' }
```
Insert at the position matching its group order.
### 5. Update useAgentsData.js
Add transformation in `src/hooks/useAgentsData.js`:
```javascript
propertyKey: agent.propertyKey.value,
propertyKeyDetail: agent.propertyKey.detail,
```
### 6. Update FilterBar.jsx (for filterable properties)
If the property is in `packaging` or `features` group **and** has `cellType: 'badge'`, add it to the `featureOptions` array in `src/components/FilterBar.jsx`:
```javascript
{ key: 'propertyKey', label: 'Label' }
```
Insert in the appropriate section (Packaging or Features) following the existing order.
### 7. Update GitHub Issue Templates
**01-update-agent.md** - Add under Features section:
```markdown
- [ ] **Property Label** (`propertyKey`)
- New value: <!-- yes/no/partial/null -->
- Detail:
```
**02-add-new-agent.md** - Add new section with property definition, value format, and examples.
## Checklist
- [ ] Property added to all agents in agents-detailed.json
- [ ] Property key added to correct group in groups.json
- [ ] Column definition added to AgentTable.jsx
- [ ] Transformation added to useAgentsData.js
- [ ] Filter option added to FilterBar.jsx (if badge in packaging/features)
- [ ] Update template modified in .github/ISSUE_TEMPLATE/01-update-agent.md
- [ ] New agent template modified in .github/ISSUE_TEMPLATE/02-add-new-agent.mdRelated Skills
property-based-testing
Provides guidance for property-based testing across multiple languages and smart contracts. Use when writing tests, reviewing code with serialization/validation/parsing patterns, designing features, or when property-based testing would provide stronger coverage than example-based tests.
detecting-broken-object-property-level-authorization
Detect and test for OWASP API3:2023 Broken Object Property Level Authorization vulnerabilities including excessive data exposure and mass assignment attacks.
unclaimed-property-policy
Drafts an enterprise Escheatment and Unclaimed Property Policy covering property identification, dormancy matrices, due diligence notices, NAUPA-format reporting, remittance, recordkeeping, and audit preparedness across all US state jurisdictions. Use when establishing or updating an unclaimed property compliance framework, preparing for state audits, or evaluating voluntary disclosure programs.
bill-of-sale-personal-property
Drafts a U.S. CRE personal property Bill of Sale transferring equipment, fixtures, FF&E, inventory, and other tangible assets. Handles inclusion/exclusion schedules, price allocation, tax responsibility, and risk of loss. Trigger when the user needs a bill of sale, asset schedule, equipment transfer document, or personal property conveyance tied to a CRE closing.
managing-property-due-diligence
Structures real estate due diligence with physical inspection, environmental review, and title analysis coordination. Use when conducting property DD, reviewing environmental reports, or coordinating due diligence workstreams.
managing-property-disposition
Structures property sale processes with broker opinion of value, marketing strategy, and bid analysis. Use when managing property sales, evaluating offers, or coordinating disposition processes.
analyzing-property-valuations
Structures real estate valuation with income, comparable sales, and cost approaches. Use when valuing properties, performing appraisal analysis, or comparing valuation methodologies.
analyzing-property-casualty-lines
Evaluates P&C insurance lines with market cycle analysis, loss cost trending, and competitive assessment. Use when analyzing P&C markets, tracking insurance cycles, or evaluating line profitability.
property-based-testing
Provides guidance for property-based testing across multiple languages and smart contracts. Use when writing tests, reviewing code with serialization/validation/parsing patterns, designing features, or when property-based testing would provide stronger coverage than example-based tests.
detecting-broken-object-property-level-authorization
检测和测试OWASP API3:2023对象属性级授权失效（BOPLA）漏洞，包括过度数据暴露和批量赋值攻击。
custom-property-editor-for-flow
Use when building or reviewing an LWC Custom Property Editor for Flow screen or action configuration, including the `configurationEditor` metadata hook, builder-side APIs, validation, and value-change events. Triggers: 'custom property editor', 'Flow configuration editor', 'builderContext', 'inputVariables', 'configurationEditor'. NOT for ordinary runtime screen-component behavior when no Flow Builder design-time customization is involved.
flow-custom-property-editors
Use when designing or reviewing Flow custom property editor patterns for screen components or actions, including when Flow Builder needs guided design-time configuration, generic type mapping, or builder-context-aware validation. Triggers: 'Flow custom property editor', 'configurationEditor', 'builderContext', 'inputVariables', 'Flow screen component setup'. NOT for general LWC runtime behavior when Flow Builder customization is not involved.