@farmslot/skills 0.6.27 → 0.8.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -6,6 +6,15 @@ All notable changes to `@farmslot/skills` are tracked here.
6
6
 
7
7
  - Active-development baseline; add user-facing changes here before release or package publication.
8
8
 
9
+ ## 0.8.0 - 2026-10-19
10
+
11
+ - Align with `@farmslot/agent-runtime` 0.31.0.
12
+
13
+ ## 0.7.0 - 2026-10-19
14
+
15
+ - Align with `@farmslot/agent-runtime` 0.30.0.
16
+ - The `recipe-harness` skill inspects recipes with `farmslot recipe run --list` and `--describe` (allowed tool `Bash(farmslot recipe:*)`), since `farmslot-recipe` is removed.
17
+
9
18
  ## 0.6.27 - 2026-10-18
10
19
 
11
20
  - Align with `@farmslot/agent-runtime` 0.29.5.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@farmslot/skills",
3
- "version": "0.6.27",
3
+ "version": "0.8.0",
4
4
  "type": "module",
5
5
  "main": "dist/index.js",
6
6
  "types": "dist/index.d.ts",
@@ -33,7 +33,7 @@
33
33
  "prepublishOnly": "node ../../scripts/quality/check-farmslot-package-readiness.mjs --publish --packages @farmslot/skills"
34
34
  },
35
35
  "dependencies": {
36
- "@farmslot/agent-runtime": "0.29.5"
36
+ "@farmslot/agent-runtime": "0.31.0"
37
37
  },
38
38
  "devDependencies": {
39
39
  "@types/node": "^22.0.0",
@@ -5,7 +5,7 @@ compatibility: Claude, Codex, Cursor, and Markdown skill runners with shell acce
5
5
  metadata:
6
6
  package: '@farmslot/skills'
7
7
  related_package: '@farmslot/recipe-runner'
8
- allowed-tools: Read Bash(rg:*) Bash(node:*) Bash(npm:*) Bash(yarn:*) Bash(pnpm:*) Bash(farmslot-recipe:*)
8
+ allowed-tools: Read Bash(rg:*) Bash(node:*) Bash(npm:*) Bash(yarn:*) Bash(pnpm:*) Bash(farmslot recipe:*)
9
9
  ---
10
10
 
11
11
  # Recipe Harness
@@ -16,7 +16,7 @@ Use the local recipe runtime when one exists, or recommend the smallest install
16
16
 
17
17
  1. Find the project-owned recipe command first.
18
18
  2. If no command exists, check for `@farmslot/recipe-runner` or an app-specific harness package.
19
- 3. Before authoring, inspect the closest recipes with `farmslot-recipe run --list` and `farmslot-recipe run <id> --describe`, then inspect declared actions only if no recipe fits. Prefer project discovery commands; otherwise read only the relevant manifest entries and examples.
19
+ 3. Before authoring, inspect the closest recipes with `farmslot recipe run --list` and `farmslot recipe run <id> --describe` (add `--project-root .` outside a Farmslot project), then inspect declared actions only if no recipe fits. Prefer project discovery commands; otherwise read only the relevant manifest entries and examples.
20
20
  4. Run dry-run or schema validation before live execution when available.
21
21
  5. Record artifact paths and validation output.
22
22
  6. If no runner exists, stop with a concrete install recommendation.