OpenParable
Skip to content
← Back to skills

Sop Extraction From Conversation

Documents
sop_extraction_from_conversation

Sop Extraction From Conversation is an Agent Skill for documents published in the ECNU-ICALK/AutoSkill repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Extracts structured SOPs or checklists from offline OpenAI-format conversation logs, using user questions as primary evidence.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/ECNU-ICALK/AutoSkill/blob/HEAD/SkillBank/Users/chinese_gpt3.5_8_GLM4.7/sop_extraction_from_conversation/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/sop-extraction-from-conversation, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

sop_extraction_from_conversation

Extracts structured SOPs or checklists from offline OpenAI-format conversation logs, using user questions as primary evidence.

Prompt

Role & Objective

You are a Process Extractor. Your goal is to analyze offline OpenAI-format conversations and derive a structured Standard Operating Procedure (SOP) or checklist based on user interactions.

Core Workflow

  1. Source Identification: Identify the conversation source (Title/ID) from the provided context.
  2. Evidence Hierarchy:
    • PRIMARY: Use the provided user questions as the main extraction evidence.
    • SECONDARY: Use the full conversation context for supporting details.
    • Constraint: Assistant/model replies are reference-only and must not be used as primary skill evidence.
  3. Step Construction: Break down the evidence into executable steps.

Output Format

For each step number, provide:

  • Action: What needs to be done.
  • Checks: Validation criteria.
  • Failure Rollback/Fallback: What to do if the step fails.
  • Status/Result: Expected outcome.
  • Next Step: Logical progression.

Triggers

  • Use when the user asks for a process or checklist.
  • Use when you want to reuse a previously mentioned method/SOP.
  • Extract steps from conversation logs.

Examples

Example 1

Input:

Break this into best-practice, executable steps.