← Argovance Skill OSCONTENT HISTORY

Update to Argovance Skill OS

Snapshot Sep 30, 2026 · 23:16 UTC · version 1.1.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
{
  "description": "Convert messy notes, chats, files, transcripts, links, and mixed sources into an organized knowledge system with taxonomy, summaries, entities, decisions, procedures, FAQs, provenance, contradictions, gaps, and retrieval paths. Use for knowledge bases, research organization, company wikis, or cleaning information overload.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 229
    },
    {
      "relative_path": "references/legacy-chat-extraction.md",
      "size_in_bytes": 1825
    }
  ],
  "name": "turn-chaos-into-knowledge",
  "skill_md_contents": "---\nname: turn-chaos-into-knowledge\ndescription: Convert messy notes, chats, files, transcripts, links, and mixed sources into an organized knowledge system with taxonomy, summaries, entities, decisions, procedures, FAQs, provenance, contradictions, gaps, and retrieval paths. Use for knowledge bases, research organization, company wikis, or cleaning information overload.\n---\n# Turn Chaos Into Knowledge\n1. Define users, decisions supported, source scope, sensitivity, freshness, and target system.\n2. Inventory and deduplicate sources; preserve provenance, dates, ownership, and access constraints.\n3. Extract concepts, entities, claims, decisions, actions, processes, questions, and relationships.\n4. Design a shallow taxonomy around retrieval tasks; separate canonical records from commentary and archive.\n5. Resolve duplicates without erasing contradictions; label confidence, stale material, and missing sources.\n6. Return information architecture, canonical summaries, index, decision log, FAQs, gaps, maintenance rules, and migration plan.\n\n## Legacy project-chat route\n\nWhen the source is one or more historical project chats, read [references/legacy-chat-extraction.md](references/legacy-chat-extraction.md). Extract attributed candidate knowledge and continuity deltas; do not make the chat or its generated summary authoritative. Route ongoing orientation/checkpoints to `$maintain-project-continuity`, portable session transfer to `$handoff-work-between-chats`, and durable recovery records to `$build-continuity-second-brain`.\n"
}

SHA-256 of public snapshot: 2b3fbb905660eca1e07bbf9db9a90a5142a96d8d9ef936822efe3ae276b92d22