workflow-from-chats
Extract durable working preferences from recent OpenCode sessions and convert them into skills, rules, or workflow docs.
Skill by neronlux
Chalk Labs
Need help deploying workflow-from-chats?
Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/neronlux-workflow-from-chats
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: productivity, agent-building
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/workflow-from-chats
What's inside
- Skill name
workflow-from-chats- Description
- Extract durable working preferences from recent OpenCode sessions 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.
- License
- MIT
- Compatibility
- opencode
- Instructions
- 47 lines in SKILL.md · view on GitHub
Files (1)
- SKILL.md
SKILL.md (first lines)
# Workflow From Sessions Infer durable working preferences from recent sessions. Do not summarize sessions; 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.
From neronlux/ntech-team-kit, MIT.
Signals
- Stars
- 3
- Forks
- 0
- Open issues
- 0
- Last commit (this folder)
- May 22, 2026 (5 months ago)
- Last release
- May 28, 2026 (5 months ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- Repository
- github.com/neronlux/ntech-team-kit
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
Done for you
Rather not set it up yourself?
Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.
See how we build AI agents →Read the case studies
Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.
- launches shipped
- 50+
- launches shipped
- media placements
- 500+
- media placements
- founders on every account
- 2
- founders on every account
Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block
Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.
Get workflow-from-chats running in your business
Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.
Cite this page
workflow-from-chats skill. Agent Mart. https://agentmart.dev/skills/neronlux-workflow-from-chats (last updated 2026-10-24)