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 Automatización y agentes
Para autores: añade una insignia a tu README
Si lo creaste tú, pega este código en tu README. La insignia enlaza a esta página.
[](https://mcp.popnx.com/en/skills/typesafe-ai-skills)Skills parecidas
Mismo tipo de trabajo, ordenadas como la lista de Skills
1 skills (conjuntos de instrucciones) de typesafe-ai que la IA lee y sigue · no es un MCP server
En qué se diferencia un Skill de MCP
MCP = las manos
Conecta la IA a un servicio o dato externo, como leer Notion o crear una factura. Necesita un programa o servidor en marcha.
Skill = el manual
Un archivo de texto que enseña a la IA cómo hacer una tarea. No se conecta a nada.
A veces se parecen: algunas Skills ejecutan scripts que llaman herramientas y algunos MCP solo envían conocimiento. Empieza por la tarea que quieres hacer.
Funciona con
Claude Code
Según el README del autor y las carpetas del repo
Instalar
Is it safe?
- Who made it
GitHub account typesafe-ai (organization), 2 years old
- Use and upkeep
★ 2905 stars · code last changed 24 oct 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
Primero: ¿qué IA usas?
Elige tu app y esta página mostrará solo cómo instalarlo en ella
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 1Deja que Claude Code lo instale
Copia esta frase y pégala en un chat de Claude Code
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
Vuelve a abrir Claude Code y escribe /typesafe-ai, o pide una tarea relacionada y Claude lo usará
Checked against official docs 12 nov 2026 · Source: code.claude.com
For Terminal users
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
La forma que recomienda el autor
Instala Node.js (si no lo tienes)
¿Ya está instalado? Compruébalo primero · Abre la Terminal, escribe este comando y pulsa Enter
node -v- Aparece un número de versión, p. ej. v26.13.1 = ya está instalado, sáltate este paso
- Aparece "command not found" (en Windows, "is not recognized") = aún no está instalado, o acabas de instalarlo y debes cerrar y volver a abrir la Terminal
Cómo abrir la Terminal
Mac: pulsa ⌘ + Espacio, escribe Terminal y pulsa Enter
Windows: abre Inicio, escribe Windows PowerShell y elige Abrir
Si no está instalado: Abre la página oficial de descargas, elige la versión LTS y el instalador de clics: .pkg en Mac · .msi en Windows. Haz doble clic y sigue hasta el final. No necesitas ningún comando curl
Abrir la página de descarga de Node.js ↗
Al terminar, cierra la Terminal, ábrela de nuevo y ejecuta el mismo comando. Debe aparecer un número de versión: node -v
Se instala una vez y sirve para todo lo que usa Node.js
npx skills add typesafe-ai/skills --skill typesafe-aiCopiado del README del autor; descarga y ejecuta su código
Abre la Terminal
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Copia la carpeta del skill a ~/.claude/skills
Descarga el repo a una carpeta temporal y copia solo las carpetas con 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-aiVuelve a abrir Claude Code y escribe /typesafe-ai, o pide una tarea relacionada y Claude lo usará
App de escritorio de ChatGPT
La app de escritorio de ChatGPT incluye Codex, y Codex lee las skills de la carpeta ~/.agents/skills
Option 1Deja que ChatGPT lo instale
Abre Codex en la app de escritorio de ChatGPT y pega esta frase en el chat
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 2Coloca la carpeta tú mismo
Coloca la carpeta typesafe-ai en ~/.agents/skills/typesafe-ai
~ es tu carpeta de inicio ($HOME)
For Terminal users
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Abre la Terminal
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Copia la carpeta del skill a ~/.agents/skills
Descarga el repo a una carpeta temporal y copia solo las carpetas con 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
Después de instalar
- App de escritorio de ChatGPT: abre Skills en la barra lateral para ver que la skill está
- Para usarla: en ChatGPT escribe @ y elige la skill · en Codex CLI o la extensión del IDE ejecuta /skills o escribe $ y el nombre de la skill
- Codex detecta solo las skills recién instaladas; si una no aparece, reinicia Codex
Checked against official docs 15 nov 2026 · Source: learn.chatgpt.com
ChatGPT en la web y el móvil
Las skills que instalas tú no funcionan aquí; solo las que vienen con un plugin del directorio
Para usar esta skill con ChatGPT, usa la app de escritorio de ChatGPT como se indica arriba
Checked against official docs 15 nov 2026 · Source: learn.chatgpt.com
Option 1Deja que Codex lo instale
Copia esta frase y pégala en un chat de Codex · Sirve en Codex dentro de la app de escritorio de ChatGPT, en Codex CLI y en la extensión del IDE
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 detecta solo las skills recién instaladas; si una no aparece, reinicia Codex · Para usarla: en ChatGPT escribe @ y elige la skill · en Codex CLI o la extensión del IDE ejecuta /skills o escribe $ y el nombre de la skill
Checked against official docs 15 nov 2026 · Source: learn.chatgpt.com
For Terminal users
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Abre la Terminal
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Copia la carpeta del skill a ~/.agents/skills
Descarga el repo a una carpeta temporal y copia solo las carpetas con 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-aiVuelve a abrir Codex y pide una tarea relacionada; Codex mostrará el skill
Option 1Deja que Cursor lo instale
Copia esta frase y pégala en un chat de Cursor
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
En el chat Agent de Cursor escribe / y elige typesafe-ai
Checked against official docs 12 nov 2026 · Source: cursor.com
For Terminal users
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Abre la Terminal
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Copia la carpeta del skill a ~/.cursor/skills
Descarga el repo a una carpeta temporal y copia solo las carpetas con 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-aiEn el chat Agent de Cursor escribe / y elige typesafe-ai
Option 1Let the AI install it
Para otras apps que leen skills. La frase incluye las rutas de Claude Code, Codex y Cursor para que la IA elija la de tu app · Copy this sentence into the app’s chat
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
Otras apps con Agent Skills (como Gemini CLI o GitHub Copilot) usan otras carpetas. Mira la guía de esa app y copia allí la carpeta con el SKILL.md.
Carpetas de skills comprobadas con las guías oficiales de Claude Code, Codex y Cursor el 11 nov 2026
✓ Comandos revisados el 18 nov 2026
Ver el SKILL.md original
El texto siguiente viene del repo del autor, no de PopNx MCP
Se muestran los primeros 8000 caracteres · Abrir el archivo completo en GitHub
---
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 "WhichConversación
Pregunta, comparte un consejo o avisa de que no funciona. Ordenado por lo que la gente marcó como útil.
Aún no hay publicaciones. Sé la primera persona en preguntar o compartir.
Lo publicado aquí lo escriben usuarios, no el equipo de PopNx.
Desde GitHub
- Estrellas en GitHub
- 2905
- Autor
- typesafe-ai
- Licencia
- MIT
- Último cambio de código
- 24 oct 2026
- Archivos SKILL.md del repo (con traducciones y plantillas)
- 1