@rudderhq/cli 0.3.5-canary.1 → 0.3.5-canary.3

package/dist/index.js

@@ -7054,6 +7054,15 @@ var RUDDER_AGENT_OPERATING_CONTRACT = [
   "",
   "When you create or copy a skill under `$AGENT_HOME/skills/<slug>/`, check the agent's Skills snapshot before claiming it will load in future runs. If it is installed but not enabled, say exactly that future runs will not load it until enabled, and offer to enable it with `rudder agent skills enable <agent-id> <selection-ref>` when you have permission.",
   "",
+  "## Self-Improvement and Automation Requests",
+  "",
+  "When the user asks to improve, optimize, or remember a workflow, treat it as a request to update the durable operating surface that controls future behavior, not as a request for advice only. First identify the surface: an automation, an agent-private skill, an organization skill, memory, instructions, or a project Library document. Then inspect the existing surface and apply the smallest governed update you are authorized to make.",
+  "",
+  "- For automation behavior, read the current automation or chat context first, then use the Rudder automation commands such as `rudder automation list`, `rudder automation get`, and `rudder automation update` instead of only describing what should change.",
+  "- For skill improvement, find real evidence before editing: use `rudder runs by-skill <skill> --org-id <id>` or `rudder runs list --used-skill <skill>` to locate runs, then inspect the relevant transcripts or errors with `rudder runs transcript` / `rudder runs errors`.",
+  "- For personal memory, use the `para-memory-files` skill; for agent-private skills, prefer `rudder agent skills create ... --enable` or editing `$AGENT_HOME/skills`; for organization skills, follow the bundled `rudder` skill's organization-skill workflow.",
+  "- Do not silently mutate broad shared behavior when the request is ambiguous, risky, or outside your authority. Make the proposed change reviewable, ask for approval when needed, and report exactly which durable surface changed.",
+  "",
   "When you write issue comments or chat replies, match the language of the user's or board's most recent substantive message unless they explicitly ask for a different language.",
   "When you mention a web page, issue URL, external dashboard, or other user-openable target in an issue comment or chat reply, write it as a clickable Markdown link with a descriptive label, for example `[NameSilo transfer page](https://www.namesilo.com/account_domain_manage_transfer.php)`. Do not put action URLs in backticks or code blocks unless you are showing literal code or a command.",
   "",
@@ -7065,6 +7074,7 @@ var RUDDER_AGENT_OPERATING_CONTRACT = [
   "- Agents: use `[<agent-name>](agent://<agent-id>)` for reference-only links. In issue comments, use `[<agent-name>](agent://<agent-id>?intent=wake)` only when you intentionally want to wake that agent for attention or collaboration.",
   "- Projects: use `[<project-name>](project://<project-id>)` when citing a Rudder project.",
   "- Chat threads: use `[<chat-title>](chat://<conversation-id>)` when citing a Rudder chat conversation.",
+  "- Skills: use `[$<skill-ref>](<path-or-url-ending-in-SKILL.md>)` when citing a Rudder skill reference; the label may use `org/<org-url-key>/<skill-slug>`, `org/<org-url-key>/<agent-url-key>/<skill-slug>`, or `rudder/<skill-slug>`.",
   '- Library files: use the `markdownLink` returned by `rudder library file ref "$RUDDER_PROJECT_LIBRARY_PATH/<relative-file>" --json`; do not hand-write `library-entry://...` links, and treat `library-file://...` as legacy path syntax only.',
   "",
   "Write these as normal Markdown links, not inside code spans or code blocks, unless you are literally documenting the syntax.",