Version Packages

[gtbuchanan]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@gtbuchanan/eslint-plugin-agent-skills@1.0.0

Major Changes

• 79c96d0: Gate skill length on tokens rather than lines

  configs.recommended now caps both SKILL.md and
  **/skills/*/references/**/*.md with agent-skills/max-tokens at 5000,
  and applies agent-skills/max-lines to neither. The rule still ships, so
  a repo wanting the spec's 500-line figure can wire it explicitly:

  {
    files: ['**/skills/*/SKILL.md'],
    rules: { 'agent-skills/max-lines': ['warn', { max: 500 }] },
  }

  Both rules proxy for how much context a skill costs to load, and tokens
  measure it directly. At the ~10-14 tokens per line typical of prose
  skills, 500 lines works out to 5200-7000 tokens, so the token cap is the
  one that fires. The line cap leads only below ~10 tokens per line, where
  it reports formatting — semantic line breaks and dense lists raise a line
  count without changing what the agent loads.

  The 300-line cap on references/ had no upstream basis: the spec's third
  tier is "Resources (as needed)" and skill-creator calls bundled
  resources "unlimited, loaded as needed". The 5000 there is a backstop for
  a reference file costing more to load than the instructions tier it was
  split out of.

@gtbuchanan/cli@0.7.1

Patch Changes

• 23ae7e2: Generate deploy:skills for skills at the workspace root

  A monorepo whose skills/ sits at the root got no deploy:skills task
  at all: the capability was read from the packages alone, so the root's
  copy — which capabilitiesFor already detects — went unused. The task
  disappeared the moment packages: globs were added to
  pnpm-workspace.yaml and the root stopped being the lone package.

  gtb sync now emits a //#deploy:skills root task and the root
  deploy:skills script backing it whenever a monorepo root carries its
  own skills/, with build depending on it — the shape
  //#lint:eslint already uses. gtb verify covers it for free, since a
  generated task is one it can report as missing.

  Root skills are not a fallback for per-package ones: both are emitted
  when both exist. They are the case a package can't serve — skills
  consumed as <root>/skills/<name>/SKILL.md are invisible inside a
  package, and a private workspace package reaches no consumer at all.

  Because turbo dispatches //#deploy:skills through the root script of
  that name, such a root no longer gets the gtb turbo run deploy:skills
  alias — it would re-enter turbo and trip the
  recursive_turbo_invocations guard. Reach every package's copy through
  pnpm build or gtb turbo run deploy:skills.

@gtbuchanan/eslint-config@0.5.2

Patch Changes

• Updated dependencies [79c96d0]
  • @gtbuchanan/eslint-plugin-agent-skills@1.0.0