update-parker-skill

Propose and execute system updates with approval for global changes.

44|17|Updated Jun 23, 2026

Search Tags:#dependency management #change management #system updates #context-engineering #cross-referencing

Ready to run

npx skills add https://github.com/real-simple-labs/parker-brain --skill update-parker-skill

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: update-parker-skill
Source: https://github.com/real-simple-labs/parker-brain/tree/main/.claude/skills/update-parker-skill
Command: npx skills add https://github.com/real-simple-labs/parker-brain --skill update-parker-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that updates to Parker's prompts, system docs, rubrics, and more are made correctly and with minimal risk of errors like drift, broken references, or missing impacts.

Core Features & Use Cases

Propose-Then-Execute Workflow: Always proposes changes before executing, requiring human approval for global changes.
Automated Dependency Identification: Identifies which dependent files need updating after a change is made.
Cross-Reference Propagation: Propagates changes across related system components to maintain consistency.

Quick Start

To propose an update to the system, use the command 'update-parker-skill propose --update [path/to/file] --change [description of change]'.

Frequently Asked Questions about update-parker-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate system updates while preventing broken cross-references?▼

Automating system updates safely requires a propose-then-execute workflow that identifies dependencies and propagates changes across related components to prevent drift and broken references.

What is the best way to manage dependency changes across a context-engineering system?▼

Dependency management in a context-engineering system is best handled by automatically identifying dependent files and propagating updates cross-references to maintain consistency before changes are executed.

How do I propose updates to system docs and rubrics without causing drift?▼

Proposing updates to system docs and rubrics without drift involves submitting a description of the change for human approval, ensuring global changes are reviewed before execution.

Can I execute global system changes without manual approval?▼

Global system changes require human approval before execution to ensure proper change management and minimize the risk of errors like missing impacts or broken references.

Why does updating context-engineering prompts cause missing impacts in related files?▼

Updating context-engineering prompts causes missing impacts when cross-reference propagation fails to identify and update dependent files, leading to system inconsistency and drift.

Does the update-parker-skill workflow support custom change descriptions?▼

The update-parker-skill workflow supports custom change descriptions passed as arguments when proposing updates to ensure the system understands the intended modifications before approval.