skills.rest
thesyntaxninja
thesyntaxninjaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

propose-skill-update

Propose skill definition updates after three documented recurring occurrences.

2|Updated Mar 4, 2026
Search Tags:#automation#verification#skill-management#knowledge-management#pattern-detection#propose#skill-update
One-click install
npx skills add https://github.com/thesyntaxninja/syntaxninja-dojo --skill propose-skill-update
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: propose-skill-update
Source: https://github.com/thesyntaxninja/syntaxninja-dojo/tree/main/skills/propose-skill-update
Command: npx skills add https://github.com/thesyntaxninja/syntaxninja-dojo --skill propose-skill-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill captures recurring triggers, anti-patterns, or missing verification steps observed multiple times and formalizes them into a proposed update, preventing one-off edits and ensuring changes are evidence-driven and user-approved.

Core Features & Use Cases

  • Evidence collection: Guides the agent to gather and format three distinct occurrences as a formal proposal.
  • User approval workflow: Presents the proposed addition to the user and requires explicit consent before applying changes.
  • Controlled edits: Adds only allowed items (new triggers, anti-patterns, verification steps), updates frontmatter if needed, and instructs index rebuilds; used during code reviews, repeated linting failures, or when compound-docs accumulates similar learnings.

Quick Start

Propose a skill update by presenting three documented occurrences, the exact text to add to the target skill, and a clear request for user approval.

Frequently Asked Questions about propose-skill-update

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

FAQPage Schema
How do I update skill definitions from recurring code review patterns?▼

To update skill definitions from recurring patterns, gather three documented occurrences of a trigger, anti-pattern, or verification need. Propose the exact text addition and require explicit user approval before editing SKILL.md files.

What is the best way to formalize recurring anti-patterns into skill updates?▼

Formalizing recurring anti-patterns requires collecting three distinct occurrences as evidence. The agent formats these into a formal proposal, presents it for explicit user consent, and then applies controlled edits to frontmatter and triggers.

How do I automate skill management for repeated linting failures?▼

Automating skill management for repeated linting failures involves detecting three similar occurrences across commits or diffs. The agent captures these recurring issues, proposes a formal update, and awaits user approval before modifying the skills index.

Can I propose skill updates without explicit user approval?▼

No, proposing skill updates requires explicit user approval before applying any changes. The workflow presents the proposed addition and necessitates direct consent to prevent one-off edits and ensure changes remain evidence-driven.

When should I not use automated pattern detection for skill management?▼

You should not use automated pattern detection for skill management when you have fewer than three documented occurrences of an issue. The system requires three distinct occurrences as evidence to generate a formal proposal.

Related Skills

Explore More Software Engineering Skills→
softwaresaltsoftwaresalt
1

compound-refresh

Review docs/compound entries against current repository reality and classify them.

Community
Intermediate
SimpleEveSimpleEve
30

eo-archive

Merge approved Spec Deltas into a module's spec.md and archive the change.

Community
Advanced
shakedfbshakedfb

rethink

Analyze accumulated observations and tensions to triage, detect patterns, and propose system changes.

Community
Advanced
rezicsrezics
6

discuss-first

Require explicit user approval before executing proposed code changes.

Official
Advanced