agentleFS
Sign inStart free
yogsoth-aiyogsoth-ai/knowledge-structuring/skills/argument-visualization/SKILL.md

argument-visualization

Skill2 starsChanged 6 months agoApache-2.0View on GitHub

SOP for generating argument structure visualization — query graph for argument chains, format as mermaid diagram or indented tree, write to vault.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Write/update wiki/topics/<topic-slug>.md with the argument map section

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Argument Visualization

Generate a visual representation of the argument structure for a topic.

Tool

vault_query_graph + CC file write

Protocol

  1. Query graph starting from the topic node, traversing supported_by, contradicts, and derived_from edges
  2. Collect all claims, evidence, and their relationships
  3. Format as a mermaid diagram in the wiki page:
    • Green nodes: strong claims (strength ≥ 7)
    • Yellow nodes: moderate claims (strength 4-6)
    • Red nodes: weak claims (strength ≤ 3)
    • Solid edges: supported_by
    • Dashed edges: contradicts
  4. Write/update wiki/topics/<topic-slug>.md with the argument map section
  5. Include a summary: total claims, strongest/weakest, key contradictions

HARD-GATE

<HARD-GATE> Visualization must include at least 3 claims and their relationships. A single-node diagram is not useful. </HARD-GATE>

Yield

Returns: { topic: string, claims_shown: number, edges_shown: number, format: "mermaid" }

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free