npx skills add smithery/majesticlabs-dev --skill add-config-field
majesticlabs-dev/majestic-marketplace
add-config-field
Add new field to .agents.yml config schema (updates init.md templates, version, migration)
Installation
npx skills add majesticlabs-dev/majestic-marketplace --skill add-config-field
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Helps users discover and install agent skills when they ask questions like "how do I do X", "fi…
3.3M installsBrowser automation CLI for AI agents. Use when the user needs to interact with websites, includ…
810.4K installsReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…
617.3K installsBuild, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …
576.5K installsPrepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Te…
568.3K installsAlso in this package
Other skills from majesticlabs-dev/majestic-marketplace · top by installs.
npx skills add majesticlabs-dev/majestic-marketplace
More details
Agent compatibility
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Also listed on
Alternate registries and mirrors of this skill.
Repository health
master
Skill metadata
Parsed from SKILL.md frontmatter.
Read, Edit, Glob, GrepPackage contents
Files included with this skill beyond the listing page.
-
skill md
SKILL.md2,456 B -
docs
SUMMARY.md114 B
History
- First seen on skills.sh
- First recorded snapshot · 80 installs
SKILL.md
Add Config Field
Add a new field to the .agents.yml config schema with proper versioning and migration support.
Files Changed
| File | Purpose |
|---|---|
plugins/majestic-engineer/commands/workflows/init.md |
4 YAML templates that generate .agents.yml |
plugins/majestic-engineer/config-schema-version |
Schema version number |
plugins/majestic-engineer/agents/config-reader.md |
Changelog + migration logic |
plugins/majestic-engineer/.claude-plugin/plugin.json |
Plugin version |
.claude-plugin/marketplace.json |
Marketplace version |
Input
- Field name: e.g.,
auto_commit - Default value: e.g.,
falseor multi-line YAML - Section: Where in template (Workflow, Quality Gate, etc.)
- Comment: Inline explanation
- Used by: Agent/command that reads this field
Steps
1. Update init.md Templates
File: plugins/majestic-engineer/commands/workflows/init.md
Add field to ALL 4 templates (Rails, Python, Node, Generic). Find the appropriate section and add:
new_field: value # Comment explaining purpose
Or for multi-line:
new_field: # Comment
- item1
- item2
2. Bump Schema Version
File: plugins/majestic-engineer/config-schema-version
Increment: 1.1 → 1.2
3. Update config-reader.md
File: plugins/majestic-engineer/agents/config-reader.md
A) Add to Version Changelog table:
| 1.2 | `new_field` | Description |
B) Update migration YAML block (in "Outdated config_version" section):
new_field: default_value
4. Bump Plugin Versions
Files:
plugins/majestic-engineer/.claude-plugin/plugin.json:3.15.0→3.16.0.claude-plugin/marketplace.json: Update majestic-engineer entry version
5. Update Consumer Docs (if needed)
If a specific agent/command reads this field, update its documentation to mention the config.
Verification
# Count field in init.md (should be 4 - one per template)
grep -c "new_field" plugins/majestic-engineer/commands/workflows/init.md
# Check schema version
cat plugins/majestic-engineer/config-schema-version
# Check changelog entry
grep "new_field" plugins/majestic-engineer/agents/config-reader.md