Prototyp · Vorschau: alle Server aus der offiziellen Registry, alle 30 Minuten synchronisiert. Mit Google anmelden, um Bewertungen zu schreiben.Prototyp · alle 30 Min. aktualisiert
PopNx MCPMCP-Server für alle, die KI nutzen · in einfachen Worten erklärt

What it does

Agent skills for building with TypeSafe's System One API

  • Connects Instruction files the AI reads, with steps that call an outside service
  • Account or key Some steps need a key for TYPESAFE_API_KEY (per the README)
  • Category Automatisierung und Agenten
Für Anbieter: Badge ins README

Wenn du das gebaut hast, füge diesen Code in dein README ein. Das Badge verlinkt auf diese Seite.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/skill/typesafe-ai-skills.svg)](https://mcp.popnx.com/en/skills/typesafe-ai-skills)

Ähnliche Skills

Gleiche Art Arbeit, sortiert wie die Skill-Liste

Im Vergleich mit ähnlichen
Dieser
skills
skillsnacosanatomyleon
Anbietertypesafe-aivercel-labsalibabawheresryan22leon-ai
Skills11111
GitHub-Sterne2.90539.77833.52427.79917.688
Letzte Codeänderung24. Okt. 202617. Nov. 202617. Nov. 202619. Okt. 202613. Nov. 2026
LizenzMITMITApache-2.0MITMIT

1 Skills (Anweisungssammlungen) von typesafe-ai, die eine KI liest und befolgt · kein MCP-Server

Was einen Skill von MCP unterscheidet

MCP = die Hände

Verbindet die KI mit einem externen Dienst oder Daten, etwa Notion lesen oder eine Rechnung erstellen. Ein Programm oder Server muss laufen.

Skill = das Handbuch

Eine Textdatei, die der KI zeigt, wie eine Aufgabe geht. Sie verbindet sich mit nichts.

Manches überschneidet sich: Einige Skills starten Skripte mit Werkzeugen, einige MCP-Server liefern nur Wissen. Geh von der Aufgabe aus.

Funktioniert mit

Claude Code

Laut README des Anbieters und den Ordnern im Repo

Installieren

Is it safe?

  • Who made it

    GitHub account typesafe-ai (organization), 2 years old

  • Use and upkeep

    ★ 2.905 stars · code last changed 24. Okt. 2026

  • Any scripts?

    No, plain text files the AI reads and follows

  • Uses the internet?

    No scripts, so it does not go online by itself

  • Changes machine-wide settings?

    No hooks or writes to machine settings found

Checked automatically from the repo files at commit 302eea6 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself

Zuerst: Welche KI nutzt du?

Wähle deine App, dann zeigt diese Seite nur die Installation für diese App

Option 1Upload to claude.ai (web and app)

Uploading to claude.ai would fail: the description is over 200 characters (483). Use "Let the AI install it" instead

Option 1Claude Code installieren lassen

Kopiere diesen Satz und füge ihn in einen Claude Code-Chat ein

Where to install
Please install the skill typesafe-ai from https://github.com/typesafe-ai/skills folder skills/typesafe-ai (commit 302eea6) for all my projects, at ~/.claude/skills/typesafe-ai. First show me every file and tell me whether it has scripts or changes machine settings, then tell me the full path you will install to and wait for me to agree.
Please install the skill typesafe-ai from https://github.com/typesafe-ai/skills folder skills/typesafe-ai (commit 302eea6) into the project this chat is open in (at .claude/skills/typesafe-ai). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the project name and the full path you will install to and wait for me to agree.

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Claude Code neu starten, dann /typesafe-ai tippen oder eine passende Aufgabe stellen; Claude nutzt den Skill

Checked against official docs 12. Nov. 2026 · Source: code.claude.com

For Terminal users

Ein Skill sind Anweisungen, denen die KI folgt. Lies die Dateien vor der Installation und installiere nur von vertrauenswürdigen Anbietern.

Vom Anbieter empfohlen

Node.js installieren (falls noch nicht vorhanden)

Schon installiert? Zuerst prüfen · Öffne das Terminal, gib diesen Befehl ein und drücke Enter

node -v
  • Eine Versionsnummer wie v26.13.1 = installiert, diesen Schritt überspringen
  • "command not found" (unter Windows "is not recognized") = noch nicht installiert, oder gerade installiert und das Terminal muss neu geöffnet werden
So öffnest du das Terminal

Mac: ⌘ + Leertaste drücken, Terminal eingeben, Enter

Windows: Start öffnen, Windows PowerShell eingeben, dann Öffnen

Noch nicht installiert: Öffne die offizielle Download-Seite, wähle die LTS-Version und den Klick-Installer: .pkg auf dem Mac · .msi unter Windows. Doppelklicken und bis zum Ende durchklicken. Kein curl-Befehl nötig

Download-Seite von Node.js öffnen ↗

Danach das Terminal schließen, neu öffnen und denselben Befehl erneut ausführen. Es muss eine Versionsnummer erscheinen: node -v

Einmal installieren, gilt für alles, was Node.js braucht

npx skills add typesafe-ai/skills --skill typesafe-ai

Aus dem README des Anbieters; lädt den Code des Anbieters herunter und führt ihn aus

  1. Terminal öffnen

    Mac: Command+Leertaste und Terminal tippen · Windows: Der Befehl unten funktioniert nicht in PowerShell; nutze oben „KI installiert es“

  2. Skill-Ordner nach ~/.claude/skills kopieren

    Lädt das Repo in einen temporären Ordner und kopiert nur Ordner mit einer SKILL.md

    git clone --depth 1 https://github.com/typesafe-ai/skills.git /tmp/popnx-skill-typesafe-ai-skills-302eea6 && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-typesafe-ai-skills-302eea6/skills/typesafe-ai' ~/.claude/skills/typesafe-ai
  3. Claude Code neu starten, dann /typesafe-ai tippen oder eine passende Aufgabe stellen; Claude nutzt den Skill

Selbst installierte Skills funktionieren in der ChatGPT-Desktop-App, in Codex CLI und in der Codex-Erweiterung für die IDE · ChatGPT im Web und auf dem Handy kann selbst installierte Skills nicht nutzen, nur Skills, die mit einem Plugin aus dem Verzeichnis kommen

ChatGPT-Desktop-App

Die ChatGPT-Desktop-App enthält Codex, und Codex liest Skills aus dem Ordner ~/.agents/skills

Option 1ChatGPT installieren lassen

Öffne Codex in der ChatGPT-Desktop-App und füge diesen Satz in den Chat ein

Where to install
Please install the skill typesafe-ai from https://github.com/typesafe-ai/skills folder skills/typesafe-ai (commit 302eea6) for all my projects, at ~/.agents/skills/typesafe-ai. First show me every file and tell me whether it has scripts or changes machine settings, then tell me the full path you will install to and wait for me to agree.
Please install the skill typesafe-ai from https://github.com/typesafe-ai/skills folder skills/typesafe-ai (commit 302eea6) into the project this chat is open in (at .agents/skills/typesafe-ai). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the project name and the full path you will install to and wait for me to agree.

The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Option 2Ordner selbst ablegen

Lege den Ordner typesafe-ai unter ~/.agents/skills/typesafe-ai ab

~ ist dein Home-Ordner ($HOME)

For Terminal users

Ein Skill sind Anweisungen, denen die KI folgt. Lies die Dateien vor der Installation und installiere nur von vertrauenswürdigen Anbietern.

  1. Terminal öffnen

    Mac: Command+Leertaste und Terminal tippen · Windows: Der Befehl unten funktioniert nicht in PowerShell; nutze oben „KI installiert es“

  2. Skill-Ordner nach ~/.agents/skills kopieren

    Lädt das Repo in einen temporären Ordner und kopiert nur Ordner mit einer SKILL.md

    git clone --depth 1 https://github.com/typesafe-ai/skills.git /tmp/popnx-skill-typesafe-ai-skills-302eea6 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-typesafe-ai-skills-302eea6/skills/typesafe-ai' ~/.agents/skills/typesafe-ai

Nach der Installation

  • ChatGPT-Desktop-App: Öffne Skills in der Seitenleiste, um zu sehen, ob der Skill da ist
  • So nutzt du ihn: In ChatGPT @ tippen und den Skill wählen · in Codex CLI oder der IDE-Erweiterung /skills ausführen oder $ und den Skill-Namen tippen
  • Codex erkennt neu installierte Skills selbst; wenn einer nicht erscheint, starte Codex neu

Checked against official docs 15. Nov. 2026 · Source: learn.chatgpt.com

ChatGPT im Web und auf dem Handy

Selbst installierte Skills funktionieren hier nicht, nur Skills, die mit einem Plugin aus dem Verzeichnis kommen

Um diesen Skill mit ChatGPT zu nutzen, verwende die ChatGPT-Desktop-App wie oben beschrieben

Checked against official docs 15. Nov. 2026 · Source: learn.chatgpt.com

Option 1Codex installieren lassen

Kopiere diesen Satz und füge ihn in einen Codex-Chat ein · Funktioniert in Codex in der ChatGPT-Desktop-App, in Codex CLI und in der IDE-Erweiterung

Where to install
Please install the skill typesafe-ai from https://github.com/typesafe-ai/skills folder skills/typesafe-ai (commit 302eea6) for all my projects, at ~/.agents/skills/typesafe-ai. First show me every file and tell me whether it has scripts or changes machine settings, then tell me the full path you will install to and wait for me to agree.
Please install the skill typesafe-ai from https://github.com/typesafe-ai/skills folder skills/typesafe-ai (commit 302eea6) into the project this chat is open in (at .agents/skills/typesafe-ai). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the project name and the full path you will install to and wait for me to agree.

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Codex erkennt neu installierte Skills selbst; wenn einer nicht erscheint, starte Codex neu · So nutzt du ihn: In ChatGPT @ tippen und den Skill wählen · in Codex CLI oder der IDE-Erweiterung /skills ausführen oder $ und den Skill-Namen tippen

Checked against official docs 15. Nov. 2026 · Source: learn.chatgpt.com

For Terminal users

Ein Skill sind Anweisungen, denen die KI folgt. Lies die Dateien vor der Installation und installiere nur von vertrauenswürdigen Anbietern.

  1. Terminal öffnen

    Mac: Command+Leertaste und Terminal tippen · Windows: Der Befehl unten funktioniert nicht in PowerShell; nutze oben „KI installiert es“

  2. Skill-Ordner nach ~/.agents/skills kopieren

    Lädt das Repo in einen temporären Ordner und kopiert nur Ordner mit einer SKILL.md

    git clone --depth 1 https://github.com/typesafe-ai/skills.git /tmp/popnx-skill-typesafe-ai-skills-302eea6 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-typesafe-ai-skills-302eea6/skills/typesafe-ai' ~/.agents/skills/typesafe-ai
  3. Codex neu starten und eine passende Aufgabe stellen; Codex listet den Skill

Option 1Cursor installieren lassen

Kopiere diesen Satz und füge ihn in einen Cursor-Chat ein

Where to install
Please install the skill typesafe-ai from https://github.com/typesafe-ai/skills folder skills/typesafe-ai (commit 302eea6) for all my projects, at ~/.cursor/skills/typesafe-ai. First show me every file and tell me whether it has scripts or changes machine settings, then tell me the full path you will install to and wait for me to agree.
Please install the skill typesafe-ai from https://github.com/typesafe-ai/skills folder skills/typesafe-ai (commit 302eea6) into the project this chat is open in (at .cursor/skills/typesafe-ai). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the project name and the full path you will install to and wait for me to agree.

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Im Agent-Chat von Cursor / tippen und typesafe-ai wählen

Checked against official docs 12. Nov. 2026 · Source: cursor.com

For Terminal users

Ein Skill sind Anweisungen, denen die KI folgt. Lies die Dateien vor der Installation und installiere nur von vertrauenswürdigen Anbietern.

  1. Terminal öffnen

    Mac: Command+Leertaste und Terminal tippen · Windows: Der Befehl unten funktioniert nicht in PowerShell; nutze oben „KI installiert es“

  2. Skill-Ordner nach ~/.cursor/skills kopieren

    Lädt das Repo in einen temporären Ordner und kopiert nur Ordner mit einer SKILL.md

    git clone --depth 1 https://github.com/typesafe-ai/skills.git /tmp/popnx-skill-typesafe-ai-skills-302eea6 && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-typesafe-ai-skills-302eea6/skills/typesafe-ai' ~/.cursor/skills/typesafe-ai
  3. Im Agent-Chat von Cursor / tippen und typesafe-ai wählen

Option 1Let the AI install it

Für andere Apps, die Skills lesen. Der Satz enthält die Pfade für Claude Code, Codex und Cursor, damit die KI den für deine App wählt · Copy this sentence into the app’s chat

Where to install
Please install the skill typesafe-ai from https://github.com/typesafe-ai/skills folder skills/typesafe-ai (commit 302eea6) for all my projects, at ~/.claude/skills/typesafe-ai (in Codex use ~/.agents/skills/typesafe-ai, in Cursor ~/.cursor/skills/typesafe-ai). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the full path you will install to and wait for me to agree.
Please install the skill typesafe-ai from https://github.com/typesafe-ai/skills folder skills/typesafe-ai (commit 302eea6) into the project this chat is open in (at .claude/skills/typesafe-ai; in Codex use .agents/skills/typesafe-ai, in Cursor .cursor/skills/typesafe-ai). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the project name and the full path you will install to and wait for me to agree.

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Checked against official docs 12. Nov. 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com

For Terminal users

Andere Apps mit Agent Skills (etwa Gemini CLI oder GitHub Copilot) nutzen andere Ordner. Sieh in deren Anleitung nach und kopiere den Ordner mit der SKILL.md dorthin.

Auf GitHub ansehen ↗

Skill-Ordner am 11. Nov. 2026 mit den offiziellen Anleitungen von Claude Code, Codex und Cursor geprüft

✓ Befehle geprüft am 18. Nov. 2026

Original-SKILL.md ansehen

Der folgende Text stammt aus dem Repo des Anbieters, nicht von PopNx MCP

Die ersten 8.000 Zeichen · Ganze Datei auf GitHub öffnen

---
name: typesafe-ai
license: MIT
description: >
  TypeSafe integration craft for System One models (sometimes called Decision Models) such as Jev,
  which answer typed questions about text, images, and application state with calibrated
  probabilities. Use when building, reviewing, or debugging code that calls TypeSafe; when writing
  its questions or state; when replacing an LLM prompt-and-parse step, keyword matching, or a
  brittle heuristic with a typed question; or when brainstorming where programmable common sense
  fits in an app.
---

# Build with TypeSafe

TypeSafe's **Jev**, the first public **System One model**, answers typed questions about state your
application supplies. State is the text, images, and application data your code sends with a
request. Jev can answer a Choice among options, a Noul (the probability that a statement is true), a
Score on levels you describe, or a Box that locates something in an image. Each answer comes back as
typed data with calibrated probabilities, for your code to use.

The rest of this skill is guidance: patterns that tend to produce reliable integrations. None of it
is absolute. Models change, applications differ, and edge cases exist. When a situation calls for
something else, test the alternative and use your judgment.

## Judgments from Jev, decisions in code

Integrations tend to work best when Jev makes the judgments and code decides what to do with
them. Think of each decision as a **truth table**. Jev supplies the inputs, such as "Does the
customer sound frustrated?" or "Which product is the message about?". Code holds the logic that
maps those inputs to an action.

A question that asks Jev to make the decision, such as "Should this ticket be escalated?" or "What
should the agent do next?", usually means the question is at the wrong layer. Instead, break the
decision into the judgments it depends on, and write the decision itself in code, where it's
visible and testable. Writing out the table often shows gaps in the business logic too. A
combination of judgments with no defined outcome is a design question about the system, and it is
best settled in code.

## Live docs

The live docs are the source of truth for request syntax, SDKs, question types, limits, and current
model behavior. Read the relevant pages as part of the task.

- Start at the [documentation index](https://docs.typesafe.ai/llms.txt). Append `.md` to a page
  path to get the page as Markdown, and resolve relative links against `https://docs.typesafe.ai`.
- Exact request and response schemas: the [OpenAPI spec](https://api.typesafe.ai/openapi.json) and
  the [HTTP API](https://docs.typesafe.ai/go/api.md) page. For an SDK, see the
  [Python](https://docs.typesafe.ai/go/python-sdk.md) or
  [JavaScript](https://docs.typesafe.ai/go/js-sdk.md) page and the types in the installed package.
- Question types: [primitives](https://docs.typesafe.ai/go/primitives.md) and each type's own page,
  [structured instructions and criteria](https://docs.typesafe.ai/go/advanced.md), and
  [images](https://docs.typesafe.ai/go/images.md).
- Models, context limits, and rate limits: [models](https://docs.typesafe.ai/go/models.md). Known
  model weak spots and their workarounds are on the
  [jaggedness page](https://docs.typesafe.ai/go/jaggedness.md).
- Architecture: [how to build with TypeSafe](https://docs.typesafe.ai/go/how-to-build.md),
  [patterns](https://docs.typesafe.ai/go/patterns.md), and
  [cookbooks](https://docs.typesafe.ai/go/cookbooks.md). The cookbook closest to your use case is a
  good starting point for a new workflow.

If you can't reach the live docs, use the installed SDK's types or local docs, and tell the user
you did. Leave out details that depend on the version rather than guessing them.

## Workflow

1. **Start from the decision logic.** Begin with what the application will show, select, change,
   or hand off. Sketch the truth table or rules that decide it, and list the inputs they need.
   Inputs that need an understanding of language or images make good questions. Arithmetic, dates,
   exact lookups, and policy usually belong in code. Aim for every question to feed the table, and
   give every combination of answers an outcome, including the case where a Noul lands between your
   thresholds. If code alone can already make the decision reliably, tell the user.
2. **Keep all question wording in one place.** Questions, options, criteria, and thresholds are the
   parts of an integration people audit and edit most. Keeping them together in one module makes
   that easier. [Design the state](#design-the-state) and
   [Write the questions](#write-the-questions) describe what tends to work.
3. **Probe the live API**: send test requests as described in
   [Test with the live API](#test-with-the-live-api). Use representative cases, hard cases, and
   negative cases. Keep going until the application behaves as intended.
4. **Integrate.** A few habits help here. Expose or log the exact request payload. When a call to
   the API fails, surface it as an error, not as an answer; for example, don't treat a failed call
   as a "no". Keep API keys on the server.

If the user's request is open-ended, offer the few directions from [Cookbooks](#cookbooks) that
best serve their goal, and recommend one. If the request is concrete, build it.

## Design the state

A useful check for any question is the **human test**: could a smart person, shown only this state
and this question, answer quickly by intuition? When a question fails the test, the fix is usually
in the state, not in the wording.

- **Give what a person would look at.** That means who sent each message, the full thread rather
  than a truncated last line, names rather than raw IDs or @-mention markup, and the item the
  question is about rather than the whole catalogue. State facts your code already knows, such as
  "all messages in `replies` were sent after the refund was issued", rather than leaving the model
  to work them out again.
- **Supply facts the model may lack**, such as what an internal product name or codename refers
  to.
- **Ensure every field in the state is relevant.** Irrelevant detail clutters the context and
  reduces accuracy. A field added for one question can sway the answer to another, and the model
  can read an empty list as a signal.
- **Be mindful when truncating.** Truncate long strings only when you need to, and check that the
  cut doesn't remove context the questions need.
- **Structure with named fields.** JSON objects with descriptive keys work better than a string of
  serialized JSON. They also let a question refer to each part by its path. Stable names such as
  `candidates.refund_policy` are easier to refer to than array positions.
- **Consider leaving out what no person could judge**, such as an unreadable crop or a distinction
  experts dispute. The model's answer there tends to be noise, and code will treat that noise as
  signal.

## Write the questions

Break complex judgments or decisions into their parts, and combine the answers in code with
weighted sums, boolean logic, thresholds, or other heuristics to reach the final decision. For
example, rather than asking "Is this fraud?" or "Is this spam?", ask the set of atomic questions
about what might make something fraud or spam. Each question tends to work best when it asks for
**one judgment** that a person could make at a glance.

- **Ask the concrete, observable thing.** Aim for something a person could point to: "Is a SQL
  query built by string concatenation here?" rather than "Are there SQL injection risks?".
- **One judgment per question; beware the "or".** Two conditions joined by "or" or "and" usually
  work better as two questions. Likewise, a list of rules usually works better as one question per
  rule.
- **Anchor intent to the goal.** When the judgment is about what someone wants, it helps to name
  their goal: "Which of these files does the user want copied?" rather than "Which

Diskussion

Fragen, Tipps teilen oder melden, dass etwas nicht geht. Sortiert nach „hilfreich“.

Noch keine Beiträge. Stell die erste Frage oder teile einen Tipp.

Beiträge hier stammen von Nutzern, nicht vom PopNx-Team.

Anmelden, um zu posten

Von GitHub

GitHub-Sterne
2.905
Anbieter
typesafe-ai
Lizenz
MIT
Letzte Codeänderung
24. Okt. 2026
SKILL.md-Dateien im Repo (mit Übersetzungen und Vorlagen)
1