1.0.0

Highlights

Agent Skills 1.0 establishes a canonical, category-based bundle workflow for defining, generating, shipping, and validating product-owned skills. Product repositories can keep authored definitions separate from generated packages, let the CLI reconcile bundle versions, and automate generation through the provided GitHub Actions.

Added

• Added canonical skill bundles with a source bundle.json, fixed-depth definitions/<category>/<skill-name> inputs, a generated bundle descriptor, complete package manifests, and deterministic digests.
• Added agent-skills build --root <path>. It reconciles source definitions, generated output, and skillBundleVersion; --check validates the same contract without writing files.
• Added separate verify and sync composite GitHub Actions. verify performs read-only source and generated-output validation. sync can generate changed output, advance the bundle version, create a github-actions[bot] commit, and push it to the current branch.
• Added the bundled basic/agent-skills-packaging skill and its public source-definition contract for adding, updating, and reviewing skills in Agent Skills products.
• Added typed bundle, category, host, and SHA-256 contracts, including SkillCategory, SkillHostKind, and Sha256Digest.
• Added public documentation for the source bundle.json and skill.json shapes, generated bundle and manifest metadata, and their ownership boundaries.

Changed

• Breaking: Replaced tiers with categories throughout source definitions, generated manifests, CLI selectors, Hosting requests, operation reports, and Core APIs. Use --category and the category-based APIs instead of --tier and tier types.
• Breaking: Source definitions now use definitions/<category>/<skill-name>. Category and skill name are derived from the directory structure, and references are derived from files under references; they are no longer repeated in skill.json.
• Breaking: Generated packages now require a root generated/bundle.json. Catalog identity, bundle version, and available categories are read from the shipped generated bundle instead of being configured separately by product code.
• Breaking: The build command now accepts one bundle --root instead of separate --definitionsRoot and --generatedRoot values. The generator replaces the complete generated bundle; generated files must not be edited manually.
• Breaking: AgentSkillsCommandRuntimeOptions.CatalogId and .Tiers were removed. Hosting consumers now configure the product and package location while catalog and category data come from the generated bundle.
• Breaking: Public request, report, host, digest, and manifest models now enforce their invariants through immutable and typed contracts. Code that constructed or deconstructed the previous record models, consumed tier properties, or treated host and digest values as strings must migrate to the 1.0 APIs.
• Breaking: Pre-1.0 generated and installed manifests containing tier are no longer accepted.
• Changed list without selectors to return every category in the shipped bundle. Other standard operations still require --category, --skill, or both.

Fixed

• Fixed operation and doctor reports so custom product emitters can obtain the normalized project repository root directly from the report. Doctor reports now also include host-specific reload guidance without requiring access to internal host adapters.

Migration

1. Update all MackySoft.AgentSkills NuGet package references and the MackySoft.AgentSkills.Cli local tool reference together to 1.0.0.
2. Add skills/bundle.json with an initial skillBundleVersion of 1. Move each definition to skills/definitions/<category>/<skill-name>, move catalog and bundle-wide values to bundle.json, and keep only schemaVersion, displayName, description, and dependencies in each skill.json.
3. Delete the old generated package set and run agent-skills build --root skills. Ship the complete new skills/generated directory, including its root bundle.json.
4. Remove CatalogId and Tiers assignments from Hosting registration. Update tier-based requests, reports, selectors, custom emitters, and manifest consumers to the category-based and typed 1.0 contracts.
5. Before replacing an existing product CLI, uninstall managed skills with the pre-1.0 CLI or remove their old managed skill directories. Tier-based installed manifests cannot be updated in place by 1.0.
6. Use actions/verify@1.0.0 for read-only checks. Use actions/sync@1.0.0 only in a branch workflow that grants contents: write and permits the bot to push to that branch.

Included changes

• Added and refined the Agent Skills packaging skill. (#58)
• Introduced the category-based 1.0 bundle contract and synchronization Actions. (#59)
• Completed operation and doctor report context for product-owned emitters. (#60)
• Published bundle metadata contracts and self-hosted the synchronization workflow. (#61)

Full Changelog: 0.8.2...1.0.0