Skip to content
Back to skills

Config Improvement

ASecurity

Propose improvements to upstream RAE repository

  • 666 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added February 8, 2026
documentationpython

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add majiayu000/claude-skill-registry --skill config-improvement --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Config Improvement?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Config Improvement
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-config-improvement/badge)](https://www.skillsdirectory.com/skills/majiayu000-config-improvement)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: config-improvement
description: Propose improvements to upstream RAE repository
---

## Overview

When you discover a better pattern, configuration, or guideline during work, this skill guides you through proposing it upstream to the Reproducible Agent Environment repository.

## Parameters

- **improvement_type** (optional): "guideline", "skill", "sop", "config", or "template"
- **description** (required): Brief description of the improvement

## Steps

### 1. Evaluate Scope

Determine if the improvement is universal or project-specific.

**Constraints:**
- You MUST verify the improvement works in the current project
- You MUST check if a similar pattern already exists upstream
- You SHOULD consider if the improvement applies broadly or only to specific domains

**Decision:**
- IF universal → Proceed to step 2
- IF project-specific → Add to local overrides with comment explaining why, then STOP

### 2. Document the Improvement

Prepare a clear description of the change.

**Constraints:**
- You MUST include before/after examples
- You MUST explain the rationale (why is this better?)
- You SHOULD reference any research or sources that informed the improvement
- You MUST specify which file(s) would be modified

### 3. Create Upstream PR

**Constraints:**
- You MUST create a branch with descriptive name (e.g., `improve/ruff-config`, `guideline/async-patterns`)
- You MUST write a clear commit message explaining the improvement
- You SHOULD include test cases or examples if applicable
- You MUST open PR with the documented rationale

### 4. Update Local

After PR is merged:
- Run `scripts/sync.sh` to pull the improvement
- Verify it works correctly in your project

## Examples

**User:** "I found a better ruff configuration for catching common issues"
**Agent:** Evaluates if it's universal (yes), documents the change with before/after examples, creates PR to update templates/pyproject.toml.

**User:** "/config-improvement guideline 'Add guidance on async/await patterns'"
**Agent:** Checks if async guidance exists (no), drafts new section for python-standards.md, creates PR with examples.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.