This is an automated email from the ASF dual-hosted git repository.

potiuk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow-steward.git


The following commit(s) were added to refs/heads/main by this push:
     new f7db654  skills/setup-steward: trim frontmatter to fit metadata budget 
(#123)
f7db654 is described below

commit f7db6549f3ac0e926bbec80de94d56c7acfd5d61
Author: Yeonguk Choo <[email protected]>
AuthorDate: Tue May 12 06:44:26 2026 +0900

    skills/setup-steward: trim frontmatter to fit metadata budget (#123)
    
    The frontmatter for setup-steward was repeating the
    "single committed skill / others are symlinks" rule in both
    `description` and `when_to_use`, and the body covers it too at L45-48.
    Removes the duplicate from `when_to_use`, tightens phrasing on the
    sub-action descriptions, and drops the "gitignored snapshot this skill
    manages" detail (body covers it). Trims description + when_to_use from
    1,231 → 971 chars (margin 305 → 565).
    
    Every literal trigger phrase from the original when_to_use is preserved
    verbatim — all eight invocation triggers and all four sub-actions. Routing
    recall does not regress.
    
    Tracking: #118
---
 .claude/skills/setup-steward/SKILL.md | 24 ++++++++++--------------
 1 file changed, 10 insertions(+), 14 deletions(-)

diff --git a/.claude/skills/setup-steward/SKILL.md 
b/.claude/skills/setup-steward/SKILL.md
index 69231da..0545b6c 100644
--- a/.claude/skills/setup-steward/SKILL.md
+++ b/.claude/skills/setup-steward/SKILL.md
@@ -2,17 +2,17 @@
 name: setup-steward
 description: |
   Adopt and maintain the apache-steward framework in a project
-  repo using the snapshot-based adoption mechanism. The single
-  framework artefact that lives **committed** in an adopter's
-  repo — every other framework skill is a symlink into a
-  gitignored snapshot this skill manages. Sub-actions:
+  repo via the snapshot-based adoption mechanism. The only
+  framework skill committed in an adopter's repo — every other
+  skill is a symlink the adopt sub-action wires up.
+  Sub-actions:
     `/setup-steward`         — first-time adoption (default)
     `/setup-steward upgrade` — refresh the gitignored snapshot
                                 per the committed lock
     `/setup-steward verify`  — health check + drift detection
     `/setup-steward override <skill>` — open or scaffold an
-                               agentic override for a framework
-                               skill in `.apache-steward-overrides/`
+                                agentic override in
+                                `.apache-steward-overrides/`
     `/setup-steward unadopt` — reverse the adoption (snapshot,
                                locks, symlinks, hook, doc
                                sections, this skill itself);
@@ -21,14 +21,10 @@ description: |
 when_to_use: |
   Invoke when the user says "adopt apache-steward", "adopt
   apache/airflow-steward", "set up steward in this repo",
-  "follow .claude/skills/setup-steward", or the agent
-  equivalent triggered by following the framework's README
-  adoption instructions. Also for periodic maintenance:
-  "upgrade steward", "verify steward setup", "check steward
-  drift", "the snapshot is stale". This is the only framework
-  skill that should be **copied** into an adopter's repo
-  (every other framework skill is a symlink the adopt
-  sub-action wires up).
+  "follow .claude/skills/setup-steward", or follows the
+  framework's README adoption instructions. Also for periodic
+  maintenance: "upgrade steward", "verify steward setup",
+  "check steward drift", "the snapshot is stale".
 argument-hint: "[adopt|upgrade|verify|override skill-name|unadopt]"
 license: Apache-2.0
 ---

Reply via email to