Automated summary
This skill manages persistent command configuration storage, including execution history, acceptable warnings, and adaptive timeouts.
Strengths
- Persistent storage of command configurations
- Execution history tracking per command
- Management of acceptable warnings and skip lists
- Configuration structure validation
Limitations
- Fixed, predefined configuration schema
- Relies on a specific JSON format
- Requires use of Python scripts only
Use this skill when you need to persistently store and manage command execution configurations, including history and warning management.
Do not use this skill if you need a dynamic or flexible configuration system that does not fit the predefined schema.
Security analysis
SafeThe skill only uses Python stdlib and standard file operations to manage JSON config files; no destructive, exfiltrating, or obfuscated actions are instructed. Bash usage is limited to safe script invocation.
No concerns found
How this analysis is madeExamples
Initialize a new run configuration for this project using the manage-run-config skill.Add the warning pattern 'unchecked conversion' to the acceptable warnings list for the 'build' command.Validate the run configuration file to ensure it conforms to the expected schema.name: manage-run-config description: Run configuration handling for persistent command configuration storage allowed-tools: Read, Write, Edit, Bash
Run Config Skill
Run configuration handling for persistent command configuration storage.
What This Skill Provides
- Read and update run configuration entries
- Track command execution history
- Manage acceptable warnings and skip lists
- Adaptive timeout management
- Validate run configuration format
When to Activate This Skill
Activate this skill when:
- Recording command execution results
- Managing acceptable warnings lists
- Managing command timeouts
- Validating run configuration structure
Run Configuration Structure
{
"version": 1,
"commands": {
"<command-name>": {
"last_execution": {"date": "...", "status": "SUCCESS|FAILURE"},
"acceptable_warnings": [],
"skipped_files": []
}
},
"maven": {
"acceptable_warnings": {
"transitive_dependency": [],
"plugin_compatibility": [],
"platform_specific": []
}
},
"ci": {
"authenticated_tools": [],
"verified_at": null
}
}
See references/run-config-format.md for complete schema.
Scripts
| Script | Notation |
|--------|----------|
| init | plan-marshall:manage-run-config:run_config init |
| validate | plan-marshall:manage-run-config:run_config validate |
| timeout get | plan-marshall:manage-run-config:run_config timeout get |
| timeout set | plan-marshall:manage-run-config:run_config timeout set |
| warning add | plan-marshall:manage-run-config:run_config warning add |
| warning list | plan-marshall:manage-run-config:run_config warning list |
| warning remove | plan-marshall:manage-run-config:run_config warning remove |
| cleanup | plan-marshall:manage-run-config:cleanup |
Script characteristics:
- Uses Python stdlib only (json, argparse, pathlib)
- Outputs JSON (init/validate) or TOON (timeout/cleanup) to stdout
- Exit code 0 for success, 1 for errors
- Supports
--helpflag
Standards
| Document | Purpose | When to Read | |----------|---------|--------------| | timeout-handling.md | Adaptive timeout management | Managing command timeouts | | warning-handling.md | Acceptable warning patterns | Filtering build warnings | | cleanup-operations.md | Directory cleanup | Cleaning old files |
Quick Start
Initialize Configuration
python3 .plan/execute-script.py plan-marshall:manage-run-config:run_config init
Validate Configuration
python3 .plan/execute-script.py plan-marshall:manage-run-config:run_config validate
Integration Points
With json-file-operations Skill
- Uses generic JSON operations for field access and updates
- All CRUD operations delegate to json-file-operations
With planning Bundle
- Commands record execution history to run configuration
With lessons-learned Skill
- Lessons learned are stored separately via
plan-marshall:manage-lessonsskill - Run configuration tracks execution state only
References
references/run-config-format.md- Complete schema documentationstandards/timeout-handling.md- Adaptive timeout managementstandards/warning-handling.md- Acceptable warning patternsstandards/cleanup-operations.md- Directory cleanup operations
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/run-configuration-management-mm5t8aos/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/run-configuration-management-mm5t8aos' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/run-configuration-management-mm5t8aos/download' --output '.skill-downloads/run-configuration-management-mm5t8aos/SKILL.md.part' && mv '.skill-downloads/run-configuration-management-mm5t8aos/SKILL.md.part' '.skill-downloads/run-configuration-management-mm5t8aos/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.
Tools declared by the author (check availability in your agent): Read, Write, Edit, Bash
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/run-configuration-management-mm5t8aos/SKILL.md' && test -s '.skill-downloads/run-configuration-management-mm5t8aos/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/manage-run-config' && cp -R '.skill-downloads/run-configuration-management-mm5t8aos' '.claude/skills/manage-run-config'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/run-configuration-management-mm5t8aos'openskills read 'run-configuration-management-mm5t8aos'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/run-configuration-management-mm5t8aos/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.