Automated summary
Adds a new property to the AI agents database by modifying four key files and GitHub issue templates.
Strengths
- Step-by-step guide to avoid omissions
- Handles both data schema and display
- Automates updating GitHub issue templates
Limitations
- Requires prior knowledge of project structure
- Does not handle migration of existing data
Use this skill when you need to add a new field, column, or property to track for all agents in the comparison matrix.
Avoid this skill if you only want to modify an existing property or delete a property.
Security analysis
SafeThe skill only instructs editing static files (JSON, JSX, Markdown) within a project. It does not execute any commands, access external resources, or handle sensitive data. No risky operations like shell execution, network requests, or data exfiltration are involved.
No concerns found
How this analysis is madeExamples
Add a new property called 'contextWindow' with label 'Context Window' and tooltip 'The maximum number of tokens the agent can handle in a single request.' It should be a badge type and belong to the features group.I need to add a 'pricingTier' property to the agents database. It's a text field under the 'identity' group. Display label 'Pricing Tier', tooltip 'Free, Pro, or Enterprise tier'.name: add-agent-property description: 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.
Add Agent Property
Add a new property to the agents board by modifying four files in sequence.
Schema reference: See 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) ortext(free-form) - Group:
identity,packaging, orfeatures
2. Update agents-detailed.json
Add the property to every agent in src/data/agents-detailed.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:
{
"id": "features",
"label": "Features",
"columns": ["existingProp", "propertyKey"]
}
4. Update AgentTable.jsx
Add column definition to the columns array in src/components/AgentTable.jsx:
{ 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:
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:
{ 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:
- [ ] **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.md
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/add-agent-property-mm5t89vm/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/add-agent-property-mm5t89vm' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/add-agent-property-mm5t89vm/download' --output '.skill-downloads/add-agent-property-mm5t89vm/SKILL.md.part' && mv '.skill-downloads/add-agent-property-mm5t89vm/SKILL.md.part' '.skill-downloads/add-agent-property-mm5t89vm/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/add-agent-property-mm5t89vm/SKILL.md' && test -s '.skill-downloads/add-agent-property-mm5t89vm/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/add-agent-property' && cp -R '.skill-downloads/add-agent-property-mm5t89vm' '.claude/skills/add-agent-property'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/add-agent-property-mm5t89vm'openskills read 'add-agent-property-mm5t89vm'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/add-agent-property-mm5t89vm/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.