Skip to content
Development
Skill

/workflow-from-chats

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.

From plugin
cursor-plugins
2.6k82 skills12 agents
Install
$ npx -y skills add cursor/plugins --skill workflow-from-chats --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/workflow-from-chats

Context preview

The summary Claude sees to decide when to auto-load this skill.

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.

SKILL.md

workflow-from-chats.SKILL.md
name: workflow-from-chats
description: 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.

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.
Read more
Ships withcursor-plugins

Official Cursor plugins for popular developer tools, frameworks, and SaaS products. Each plugin is a standalone directory at the repository root with its own .cursor-plugin/plugin.json manifest.

Get the whole plugin