Automated summary
This skill helps locate and run a project's local recipe runtime, or recommend the minimal installation of the @farmslot/recipe-harness package when no runner exists.
Strengths
- Discovers the project-owned recipe command first before suggesting alternatives
- Favors dry-run and schema validation before any live execution
- Works without the full Farmslot framework, Gateway, slots, or pool files
- Reports back the command run, exit status, artifacts written, and next install step
Limitations
- Assumes shell access and the allowed tools (rg, node, npm, yarn, pnpm, farmslot-recipe)
- Does not cover installing or configuring the broader Farmslot framework beyond the harness
- Stops with an install recommendation rather than improvising a command when no runner is present
Use it when you need to run or validate a local recipe in a project, or check whether a recipe runtime is already available.
Avoid it when the task requires the full Farmslot framework, slot management, or Gateway-based orchestration.
Security analysis
CautionThe skill is intended for legitimate local recipe discovery, validation, and execution, and it includes guardrails such as preferring dry-runs and avoiding direct state mutation. However, its allowed Bash and package-manager scopes can install dependencies and run project-defined commands, so it carries moderate execution risk rather than being purely read-only.
- •Allows package-manager commands (npm/yarn/pnpm) that can install and execute third-party packages over the network.
- •Allows running `farmslot-recipe` and project recipe commands, which may execute project code or mutate application state if live execution is used.
- •Trusts locally discovered recipe commands; no explicit sandboxing or approval gate is described beyond dry-run/validation preference.
Examples
Trouve le runtime de recettes de ce projet et liste les recettes disponibles avec leurs descriptions.Lance un dry-run de la recette de connexion utilisateur et montre-moi la sortie de validation ainsi que les artefacts générés.Il n'y a pas de commande de recettes dans ce dépôt : indique-moi le chemin d'installation minimal via @farmslot/recipe-harness.name: recipe-harness description: Help run or install a local recipe runtime without assuming the full Farmslot framework compatibility: Claude, Codex, Cursor, and Markdown skill runners with shell access metadata: package: '@farmslot/skills' related_package: '@farmslot/recipe-harness' allowed-tools: Read Bash(rg:) Bash(node:) Bash(npm:) Bash(yarn:) Bash(pnpm:) Bash(farmslot-recipe:)
Recipe Harness
Use the local recipe runtime when one exists, or recommend the smallest install path when it does not.
Workflow
- Find the project-owned recipe command first.
- If no command exists, check for
@farmslot/recipe-harnessor an app-specific harness package. - Before authoring, inspect the closest recipes with
farmslot-recipe run --listandfarmslot-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. - Run dry-run or schema validation before live execution when available.
- Record artifact paths and validation output.
- If no runner exists, stop with a concrete install recommendation.
Hard Rules
- Do not invent runner commands.
- Do not require Farmslot Gateway, pool files, slots, Command Center, or Companion for first use.
- Do not bypass project fixtures or user-journey validation by directly mutating app state.
Output
Return the command run, exit status, artifacts written, and any next install step.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/recipe-harness-mrzxupjr/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/recipe-harness-mrzxupjr' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/recipe-harness-mrzxupjr/download' --output '.skill-downloads/recipe-harness-mrzxupjr/SKILL.md.part' && mv '.skill-downloads/recipe-harness-mrzxupjr/SKILL.md.part' '.skill-downloads/recipe-harness-mrzxupjr/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Environment declared by the author: Claude, Codex, Cursor, and Markdown skill runners with shell access
Tools declared by the author (check availability in your agent): Read Bash(rg:*) Bash(node:*) Bash(npm:*) Bash(yarn:*) Bash(pnpm:*) Bash(farmslot-recipe:*)
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/recipe-harness-mrzxupjr/SKILL.md' && test -s '.skill-downloads/recipe-harness-mrzxupjr/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/recipe-harness' && cp -R '.skill-downloads/recipe-harness-mrzxupjr' '.claude/skills/recipe-harness'Cursor
test -f '.skill-downloads/recipe-harness-mrzxupjr/SKILL.md' && test -s '.skill-downloads/recipe-harness-mrzxupjr/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/recipe-harness' && cp -R '.skill-downloads/recipe-harness-mrzxupjr' '.cursor/skills/recipe-harness'Codex
test -f '.skill-downloads/recipe-harness-mrzxupjr/SKILL.md' && test -s '.skill-downloads/recipe-harness-mrzxupjr/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/recipe-harness' && cp -R '.skill-downloads/recipe-harness-mrzxupjr' '.agents/skills/recipe-harness'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/recipe-harness-mrzxupjr'openskills read 'recipe-harness-mrzxupjr'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/recipe-harness-mrzxupjr/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.