Index of every page on this site: llms.txt
All skills
cursor avatar

/workflow-from-chats

@0b46ec3
by cursorcursor/plugins18k stars
1,933
Run it yourself

Extract durable working preferences from recent Cursor chats and convert them into skills, rules, or workflow docs. Use when asked to learn preferences, mine feedback, personalize workflows, or generate team/person-specific agent guidance.

Use this Skill: https://skilld.dev/gh/cursor/plugins/workflow-from-chats

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈65 tokens for metadata: the name and description. ≈599 when used: this file.

Description uses 3.3% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈261 characters, or 3.3%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Workflow From Chats

Infer durable working preferences from recent chats. Do not summarize chats; extract reusable workflow guidance.

Scope

  • Default to the last 7 days unless the user asks for a different window.
  • Read parent transcripts and relevant subagent transcripts. Use subagent content as evidence, but cite only parent conversations.
  • Do not expose local transcript paths, secrets, customer data, private chat content, or credentials.

Workflow

  1. State the target workflow or preference surface in one paragraph.
  2. Build an internal transcript inventory: title/topic, parent conversation ID, approximate date, completion state, relevant subagents, and why it may contain preference evidence.
  3. Scan for explicit preferences, corrections, and workflow markers such as "I prefer", "always", "never", "not what I asked", "stop", "review", "PR", "CI", "logs", and "skill".
  4. Extract preference atoms: trigger, workflow step, decision rule, quality bar, stop condition, evidence, and confidence.
  5. Rate confidence as strong, medium, weak, or contradicted.
  6. Cluster by workflow shape rather than transcript: shipping, review, simplification, debugging, capture, communication, delegation, or validation.
  7. Choose the artifact: new skill, skill edit, rule, workflow doc, or no artifact.
  8. Draft only the reusable guidance. Filter anecdotes that will not help future tasks.

Confidence

  • Strong: explicit user preference, workflow-changing correction, repeated parent-chat pattern, or direct request to encode behavior.
  • Medium: accepted workflow, repeated tool/model/validation preference, or subagent consensus that the parent used successfully.
  • Weak: agent-chosen behavior with no user feedback, one ambiguous transcript, or a likely task-specific correction.
  • Contradicted: evidence points in incompatible directions; ask the user before writing files.

Artifact Choice

  • Skill: recurring multi-step workflow with clear triggers.
  • Rule: general behavior that should apply broadly.
  • Workflow doc: useful context that is not reliably triggerable.
  • No artifact: situational, stale, or low-confidence observation.

Output

Return a concise synthesis first:

  • Target workflow.
  • Evidence corpus with parent conversation citations only.
  • Preference profile.
  • Adopt, consider, dismissed.
  • Proposed artifacts.
  • Open questions only if they block writing.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill analyzes chat history to automatically generate agent rules and documentation. While it includes instructions to protect sensitive data, it creates a surface for indirect prompt injection where instructions in chat history could be promoted to durable agent rules.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 0b46ec3. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 7 months ago

README badge

README badge for cursor/plugins/workflow-from-chats