Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.selftune.dev/llms.txt

Use this file to discover all available pages before exploring further.

​
Usage

selftune improve [options]
selftune improve --scope body [options]
selftune improve --scope package [options]
selftune improve is the unified evolution command. Without --scope it still uses description evolution for skills that only have description-level evidence, but it now auto-selects bounded package search when the target skill already has package evidence or a draft package manifest. Use --scope body to restrict changes to the skill body only, or --scope package to force the package-search path explicitly.

​
Flags

FlagDescription
--scope bodyLimit evolution to body content only; leaves triggers, metadata, and structure unchanged
--scope packageRun bounded package search across routing/body candidate variants
--skill-path <path>Path to the skill package to improve
--dry-runPreview proposed changes without writing them

​
Examples

Run a full improvement cycle on a skill: 
selftune improve --skill-path ./my-skill
When ./my-skill is a draft package or already has package-frontier evidence, that same command now routes into bounded package search automatically. Improve only the body of a skill without touching triggers or metadata: 
selftune improve --scope body --skill-path ./my-skill
Run a bounded package search across routing and body variants: 
selftune improve --scope package --skill-path ./my-skill
Preview what would change without applying it: 
selftune improve --dry-run --skill-path ./my-skill
The older low-level commands remain available when you want direct control over the underlying improvement path.
CommandRelationship
selftune evolveDescription-surface improvement path behind selftune improve
selftune evolve-bodyLow-level routing/body path behind selftune improve --scope body
selftune search-runLow-level bounded package-search command behind selftune improve --scope package
For lifecycle surfaces, prefer selftune improve. Use the lower-level commands when you need a specific mutation path for debugging or review.