← Resolve AICONTENT HISTORY

Update to Resolve AI

Snapshot Sep 30, 2026 · 22:59 UTC · version 1.0.0

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "name": "create-skill",
  "description": "Write or tune a skill for the Resolve plugin — encoding workflow guidance, not tool API details.",
  "included_files": [],
  "skill_md_contents": "---\n# Copyright 2026 Resolve AI, Inc.\n# SPDX-License-Identifier: Apache-2.0\nname: create-skill\ndescription: Write or tune a skill for the Resolve plugin — encoding workflow guidance, not tool API details.\nversion: 0.1.0\nlicense: Apache-2.0\n---\n\n# Write or Tune a Plugin Skill\n\n**New skill** — draft a `SKILL.md` for the workflow the user describes.\n\n**Tuning an existing skill** — read the skill the user points at, apply the boundary rules below, and trim anything that belongs in a tool description instead.\n\n## Before writing\n\n1. **Read the relevant Resolve MCP tool descriptions** — know exactly what each tool already documents so you don't repeat it in the skill.\n2. **Read all the existing skills from this plugin** — know what's already covered so you hand off rather than duplicate.\n\n## What does NOT go in a skill\n\n**Don't repeat tool descriptions** for any tools the skill uses — Resolve MCP, Grafana, Slack, or anything else. Anything the tool description already says stays there:\n\n- Parameter names, enums, defaults, or limits.\n- Stream semantics or protocol details.\n\n**Don't repeat other skills.** If the workflow needs to query Resolve or continue a conversation, hand off to `resolve-ai:ask` rather than re-describing how it works. Skills compose; they don't duplicate.\n"
}

SHA-256: 46df77eb33eb45595797da1611acee0be264ccab0253f6b2ff03c3cda848da23