Skip to content

skills(experimental/databricks-execution-compute): tighten description to ≤200 chars#107

Open
jamesbroadhead wants to merge 1 commit into
mainfrom
jb/tighten-execution-compute-desc
Open

skills(experimental/databricks-execution-compute): tighten description to ≤200 chars#107
jamesbroadhead wants to merge 1 commit into
mainfrom
jb/tighten-execution-compute-desc

Conversation

@jamesbroadhead
Copy link
Copy Markdown
Contributor

@jamesbroadhead jamesbroadhead commented May 27, 2026

Summary

Replaces a 9-line, 26-trigger description in experimental/databricks-execution-compute/SKILL.md with a 175-char clinical sentence.

Before (482 chars, 26 trigger phrases):

Execute code and manage compute on Databricks. Use this skill when the user mentions: "run code", "execute", "run on databricks", "serverless", "no cluster", "run python", "run scala", "run sql", "run R", "run file", "push and run", "notebook run", "batch script", "model training", "run script on cluster", "create cluster", "new cluster", "resize cluster", "modify cluster", "delete cluster", "terminate cluster", "create warehouse", "new warehouse", "resize warehouse", "delete warehouse", "node types", "runtime versions", "DBR versions", "spin up compute", "provision cluster".

After (175 chars):

Execute code and manage compute on Databricks: run Python/Scala/SQL/R via serverless, classic, or interactive clusters, and create/resize/delete clusters and SQL warehouses.

Why

Stable-side descriptions are tight (≤200-ish chars, 1–3 sentences, no demand verbs). This experimental import still ships the 26-trigger paragraph from a-d-k. Trigger lists in frontmatter compete with the agent's own keyword extraction and bloat manifest.json without measurable benefit.

Test plan

  • python3 scripts/skills.py validate passes — description propagates cleanly into manifest.json.
  • CI green.

This pull request and its description were written by Claude.

…n to ≤200 chars

The frontmatter description was a 9-line, 26-trigger paragraph naming
every plausible synonym for "run code" and "manage cluster". Replaces
with a 175-char clinical sentence that mirrors the stable-side
description style (cf. databricks-apps, databricks-dabs, databricks-jobs):
state what the skill does, list the languages and compute modes, no
'MUST be invoked' / 'ALWAYS prefer' demands.

## Test plan

- `python3 scripts/skills.py validate` passes (description propagates
  cleanly into manifest.json).

This PR was prepared by Claude.
@jamesbroadhead jamesbroadhead force-pushed the jb/tighten-execution-compute-desc branch from b814525 to 198bc2f Compare May 27, 2026 23:14
jamesbroadhead added a commit that referenced this pull request May 28, 2026
- Drop ../../../experimental/... cross-skill links that 404 when installed
  (skills install flat under ~/.claude/skills/, not under stable/ vs
  experimental/). Use plain skill-name references instead.
- Replace ai-dev-kit-specific tag examples ("aidevkit_project") with a
  neutral "project": "demo" so a d-a-s skill doesn't bleed a-d-k convention.
- Tighten SKILL.md description from ~870 chars to ~290 chars, matching the
  convention being established in PR #107.

Co-authored-by: Isaac
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant