Update to Fievel

{
  "description": "Define AI responsibilities, permissions, uncertainty and recovery rules for a Fievel content system.",
  "included_files": [],
  "name": "ai-behavior-designer",
  "skill_md_contents": "---\nname: ai-behavior-designer\ndescription: Define AI responsibilities, permissions, uncertainty and recovery rules for a Fievel content system.\n---\n\n# AI Behavior Designer\n\n## Using this skill from the Fievel plugin\n\nThis plugin carries Fievel's workflows and Python tools. The user's project is\nseparate from the installed plugin. Find the plugin root two directories above\nthis SKILL.md; its `runtime/` directory is the bundled resource root, called R below.\nResolve R from this skill's actual installed path, never a development checkout.\n\n- Prefer Fievel's MCP tools when they are available (names start with `fievel_`).\n  Local tools such as `fievel_init`, `fievel_validate`, `fievel_check` and\n  `fievel_view` work only inside the user's workspace and never overwrite files;\n  call `fievel_setup_status` first. Remote tools such as `fievel_validate_package`\n  and `fievel_check_responses` receive package content, store nothing, and return\n  results to save as new files; tell the user that content is sent to the Fievel\n  server for processing. Without tools, use the CLI as described below.\n- Read `R/AGENTS.md` for Fievel's conversation and workflow rules. References in\n  this skill and in AGENTS.md to AGENTS.md, docs/, knowledge/, templates/, examples/,\n  schemas/, scripts/ and .agents/skills/ are relative to R, not the user's working directory.\n- Keep the current working directory in the user's chosen workspace. Run the CLI\n  by its absolute path: `python \"R/scripts/fievel.py\" <command> <project> ...`.\n  Replace R with the resolved path. Resolve project and output paths in the user's\n  workspace. Run one simple command per step: the Python interpreter\n  with the CLI path and its arguments, without chained commands, shell variables\n  or PowerShell scripts. Read and list files with the host's file tools. Simple\n  commands keep the user's permission prompts clear and predictable. Never create\n  projects, install dependencies, or edit inside R or the plugin cache. Never copy Fievel AGENTS.md over a user's repository instructions.\n- Check Python 3.10+ and `python -c \"import jsonschema\"`. If missing, explain the\n  prerequisite. When setup is authorized, create a new `.fievel-venv` in the user's\n  workspace and install `R/requirements.txt` with its Python. Reuse a working\n  environment; do not overwrite an existing environment. Use that interpreter for\n  every CLI command. Do not install globally or claim the plugin bundles Python.\n- Follow existing workspace instructions. Explain that project files remain local,\n  but material read into the conversation is handled by the user's coding agent.\n- The repository-maintenance and adapter-sync instructions in R/AGENTS.md are for\n  Fievel development, not for modifying the installed plugin during a user session.\n- Other Fievel skills in this plugin: getting-started, content-system-builder,\n  source-discovery, ai-behavior-designer, evaluation-designer and content-audit.\n  Switch to the one that fits when the user's request changes.\n\nSave projects under the user's chosen folder (default `my-content-system/` in\ntheir workspace). The user approves content; validation does not. Do not run\nmodel evaluations unless the user authorized them.\n\n## Workflow\n\nRead AGENTS.md and stage 4 of docs/WORKFLOW.md. Required inputs: product tasks,\nactual available tools and the selected project's standards/sources. Ask what the\nassistant should explain versus act on. Read knowledge/ai-experience-design/behavior.md\nwhen explanation is useful. Define responsibility boundaries, clarification triggers,\nconfirmation for consequential actions, uncertainty, recovery and human handoff.\n\nWrite behavior.json with stable rule IDs and source links. Tool availability must\nbe verified; intended integrations are not working tools. The Wayfarer assistant\nhas no action tools, so must never claim to change or cancel bookings. Personalization\nmust use only provided context. Never infer hidden account information.\n\nOutput: draft behavior rules, linked human or deterministic checks in evaluation.json,\nsaved decisions/progress. Validate the package. If permissions are unclear, keep the\naction unavailable and identify the decision needed. Example: “cancel now” with no\ntool -> explain the limitation and give the booking confirmation next step.\n"
}