@farmslot/skills 0.1.3 → 0.2.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,10 @@ 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.2.0 - 2026-07-19
10
+
11
+ - Teach recipe authors to inspect declared actions and reusable flows before creating new capabilities
12
+
9
13
  ## 0.1.3 - 2026-07-08
10
14
 
11
15
  - Update recipe-quality skill guidance to delegate runtime artifact generation to `@farmslot/agent-runtime`
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@farmslot/skills",
3
- "version": "0.1.3",
3
+ "version": "0.2.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.1.1"
36
+ "@farmslot/agent-runtime": "0.2.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-harness'
8
- allowed-tools: Read Bash(rg:*) Bash(node:*) Bash(npm:*) Bash(yarn:*) Bash(pnpm:*)
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,9 +16,10 @@ 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-harness` or an app-specific harness package.
19
- 3. Run dry-run or schema validation before live execution when available.
20
- 4. Record artifact paths and validation output.
21
- 5. If no runner exists, stop with a concrete install recommendation.
19
+ 3. Before authoring, inspect declared actions and reusable flows. Prefer project discovery commands. For generic flow discovery, run `farmslot-recipe flows list` and `farmslot-recipe flows describe <ref>`. If no action discovery command exists, read only the relevant project manifest entries and examples.
20
+ 4. Run dry-run or schema validation before live execution when available.
21
+ 5. Record artifact paths and validation output.
22
+ 6. If no runner exists, stop with a concrete install recommendation.
22
23
 
23
24
  ## Hard Rules
24
25