openclaw/dist/skill-workshop-prompt-Ro8fA5Wx.js

Multi-channel AI gateway with extensible messaging integrations

//#region src/agents/skill-workshop-prompt.ts
/**
* System-prompt contribution for routing durable skill edits through the
* Skill Workshop tool instead of direct filesystem writes.
*/
const SKILL_WORKSHOP_TOOL_NAME = "skill_workshop";
/** Build the system-prompt section for Skill Workshop routing rules. */
function buildSkillWorkshopPromptSection() {
	return [
		"## Skill Workshop",
		"Use `skill_workshop` when the user wants to create, update, revise, list, inspect, apply, reject, or quarantine a reusable skill, Skill Workshop proposal, playbook, workflow, procedure, or durable instruction.",
		"Treat a request as durable when it should be saved, repeated, proposed, installed later, shared as a skill, or used as a standing workflow instead of answered once in chat.",
		"Do not create or change skill proposal files manually with `write`, `edit`, `exec`, shell commands, or direct filesystem operations. The final proposal artifact must go through `skill_workshop`.",
		"Use `action=create` for a new skill, `action=update` for an existing approved/live skill, and `action=revise` for an existing pending proposal; keep `description` under 160 bytes and `proposal_content` within the configured body limit.",
		"For `action=update`, pass a concise `description` when the existing live skill description should be shortened in the proposal listing.",
		"For `action=revise`, pass `proposal_id` when known. If it is not known, pass the proposal or skill name in `name` so `skill_workshop` can resolve the pending proposal or return candidates.",
		"Use `action=list` or `action=inspect` only for pending proposal discovery/inspection. Do not use filesystem search for proposal discovery.",
		"If the user names an existing live skill, read or view that skill when needed for context, but create the update proposal through `skill_workshop`.",
		"Generated skills are pending proposals by default. Do not apply, install, approve, enable, or write into live skills unless the user explicitly asks for that separate action.",
		"Use `action=apply`, `action=reject`, or `action=quarantine` only after the user explicitly asks to approve/use/apply, reject, or quarantine a specific proposal. Pass `proposal_id`; if it is not known, use `action=list` or `action=inspect` first.",
		"Do not apply, reject, or quarantine proposals manually with filesystem operations or shell commands. Proposal lifecycle changes must use `skill_workshop`.",
		"You may gather context first, but the durable proposal write or lifecycle change must use `skill_workshop`.",
		""
	];
}
//#endregion
export { buildSkillWorkshopPromptSection as n, SKILL_WORKSHOP_TOOL_NAME as t };