/ Verzeichnis / Playground / swing-skills
← Alle Server ↗ GitHub
● Community TheStack-ai ⚡ Sofort

swing-skills

von TheStack-ai · TheStack-ai/swing-skills

6 cognitive firewalls for AI agents — clarify, research, options, review, trace, mortem — each targeting a named bias: premature closure, hallucination, anchoring, confirmation, black-box reasoning, optimism.

A skill pack of 6 self-contained cognitive tools that plug specific biases. swing-clarify forces 5W1H on ambiguous requests. swing-research runs a 4-stage verified pipeline with S/A/B/C source grading. swing-options generates 5 probability-weighted alternatives including unconventional ones. swing-review does structured devil's advocacy (steel-man first, then 3-vector attack). swing-trace inventories assumptions and surfaces weakest links. swing-mortem does prospective failure analysis.

▶ Demo ansehen 📦 Installieren 💡 Anwendungsfälle

Warum nutzen

Hauptfunktionen

Live-Demo

In der Praxis

swing-skill.replay ▶ bereit
0/0

Installieren

Wählen Sie Ihren Client

~/Library/Application Support/Claude/claude_desktop_config.json  · Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "swing-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/TheStack-ai/swing-skills",
        "~/.claude/skills/swing-skills"
      ],
      "_inferred": true
    }
  }
}

Öffne Claude Desktop → Settings → Developer → Edit Config. Nach dem Speichern neu starten.

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "swing-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/TheStack-ai/swing-skills",
        "~/.claude/skills/swing-skills"
      ],
      "_inferred": true
    }
  }
}

Cursor nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "swing-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/TheStack-ai/swing-skills",
        "~/.claude/skills/swing-skills"
      ],
      "_inferred": true
    }
  }
}

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "Edit Configuration".

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "swing-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/TheStack-ai/swing-skills",
        "~/.claude/skills/swing-skills"
      ],
      "_inferred": true
    }
  }
}

Gleiche Struktur wie Claude Desktop. Windsurf neu starten zum Übernehmen.

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "swing-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/TheStack-ai/swing-skills",
        "~/.claude/skills/swing-skills"
      ]
    }
  ]
}

Continue nutzt ein Array von Serverobjekten statt einer Map.

~/.config/zed/settings.json
{
  "context_servers": {
    "swing-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/TheStack-ai/swing-skills",
          "~/.claude/skills/swing-skills"
        ]
      }
    }
  }
}

In context_servers hinzufügen. Zed lädt beim Speichern neu.

claude mcp add swing-skill -- git clone https://github.com/TheStack-ai/swing-skills ~/.claude/skills/swing-skills

Einzeiler. Prüfen mit claude mcp list. Entfernen mit claude mcp remove.

Anwendungsfälle

Praxisnahe Nutzung: swing-skills

Force clarification before an ambiguous task is executed

👤 Anyone who's seen AI agents gallop off in the wrong direction ⏱ ~10 min beginner

Wann einsetzen: A stakeholder dropped a short, ambiguous request.

Voraussetzungen
  • Skill installed — git clone https://github.com/TheStack-ai/swing-skills ~/.claude/skills/swing-skills
Ablauf
  1. Run swing-clarify
    Use swing-clarify. Request: 'make the dashboard better'. Decompose 5W1H.✓ Kopiert
    → What/who/when/where/why/how decomposition + clarifying questions

Ergebnis: A concrete scope you can actually execute against.

Kombinieren mit: agent-skill-tdd-skill

Research a topic with graded sources, not a wall of links

👤 Analysts, researchers ⏱ ~45 min intermediate

Wann einsetzen: You want a defensible brief, not hallucinated bullet points.

Ablauf
  1. Run swing-research
    Use swing-research. Question: 'what's the state of Rust in web backends (2025)?' Output claims with S/A/B/C grades.✓ Kopiert
    → Claim table with tier + source

Ergebnis: A brief you could defend to a skeptical stakeholder.

Fallstricke
  • B/C-tier claims treated as fact — The grade is there to weight; read them as weaker
Kombinieren mit: firecrawl · brave-search

Break anchoring by generating five weighted alternatives

👤 Decision-makers who notice they're anchoring ⏱ ~20 min beginner

Wann einsetzen: You've got a favorite solution and want a sanity check.

Ablauf
  1. Run swing-options
    Use swing-options. Decision: which DB for our new service? Give 5 probability-weighted options including unconventional.✓ Kopiert
    → 5 options with weights + rationale

Ergebnis: A decision made from options, not one default.

Structured review: steel-man then attack from 3 vectors

👤 Teams wanting a real review, not rubber-stamps ⏱ ~30 min intermediate

Wann einsetzen: Before committing to a plan or design.

Ablauf
  1. Run swing-review
    Use swing-review on design.md. Steel-man it first, then attack from correctness, operability, and cost.✓ Kopiert
    → Strong version of the design, then 3 attack surfaces

Ergebnis: A design that either holds or gets better.

Run a pre-mortem on a plan before execution

👤 PMs and leads about to green-light something important ⏱ ~30 min intermediate

Wann einsetzen: Right before kickoff on risky work.

Ablauf
  1. Run swing-mortem
    Use swing-mortem. Assume plan.md failed in 6 months. List 5 failure scenarios with leading indicators.✓ Kopiert
    → 5 scenarios + early-warning signals

Ergebnis: Early-warning instrumentation built in from day one.

Expose the weakest assumption in a decision tree

👤 Engineers debugging reasoning, not just code ⏱ ~20 min intermediate

Wann einsetzen: A decision feels off but you can't articulate why.

Ablauf
  1. Run swing-trace
    Use swing-trace on this decision: 'we'll use Kafka'. Inventory assumptions; call out the weakest.✓ Kopiert
    → Assumption list ranked by risk

Ergebnis: The weakest link exposed before it breaks.

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

swing-skill + skills-skill-6

Layer Swing's firewalls with InfraNodus graph analysis

After swing-review, run InfraNodus critical-perspective for graph-based critique.✓ Kopiert
swing-skill + agent-skill-tdd-skill

Clarify + research before the TDD flow

Start with swing-clarify + swing-research, then hand off to agent-skill-tdd.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

WerkzeugEingabenWann aufrufenKosten
swing-clarify ambiguous request Any vague task 0
swing-research question Research with defensibility 0
swing-options decision Anchoring risk 0
swing-review plan/design Pre-commit review 0
swing-trace decision Reasoning audit 0
swing-mortem plan Before kickoff 0

Kosten & Limits

Was der Betrieb kostet

API-Kontingent
None
Tokens pro Aufruf
Moderate per skill (research is highest)
Kosten in €
Free
Tipp
Use swing-clarify by default; others on-demand

Sicherheit

Rechte, Secrets, Reichweite

Credential-Speicherung: None
Datenabfluss: None beyond your LLM calls

Fehlerbehebung

Häufige Fehler und Lösungen

swing-research cites sources that don't check out

Cross-check S-tier sources manually; lower grades are weaker by design

swing-review feels like a formality

Force adversarial framing: 'what would an angry senior engineer say?'

Alternativen

swing-skills vs. andere

AlternativeWann stattdessenKompromiss
InfraNodus skillsYou want graph-based thinking augmentationNo bias-specific firewalls
Manual reviewOne-off trivial decisionsNo structure

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen