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 Automation and agents
For makers: add a badge to your README
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/skills/typesafe-ai-skills)Similar Skills
Same kind of work, ordered like the Skills list
1 skills (instruction sets) by typesafe-ai that an AI reads and follows · not an MCP server
How a Skill differs from MCP
MCP = the hands
Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.
Skill = the manual
A text file that teaches the AI how to do a task. It connects to nothing.
Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.
Works with
Claude Code
From the maker’s README and the folders in the repo
Install
Is it safe?
- Who made it
GitHub account typesafe-ai (organization), 2 years old
- Use and upkeep
★ 2,905 stars · code last changed Oct 24, 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
First: which AI do you use?
Pick your app and this page shows only how to install it there
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 1Let Claude Code install it
Copy this sentence and paste it into a Claude Code 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
Restart Claude Code, then type /typesafe-ai or ask for a matching task and Claude picks it up
Checked against official docs Nov 12, 2026 · Source: code.claude.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
The maker’s recommended way
Install Node.js (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
node -v- A version number such as v26.13.1 = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
npx skills add typesafe-ai/skills --skill typesafe-aiCopied from the maker’s README; it downloads and runs the maker’s code
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.claude/skills
This downloads the repo to a temporary folder and copies only the folders that contain a 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-aiRestart Claude Code, then type /typesafe-ai or ask for a matching task and Claude picks it up
ChatGPT desktop app
The ChatGPT desktop app has Codex built in, and Codex reads skills from ~/.agents/skills
Option 1Let ChatGPT install it
Open Codex in the ChatGPT desktop app and paste this sentence into the 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 2Put the folder there yourself
Put the typesafe-ai folder at ~/.agents/skills/typesafe-ai
~ is your home folder ($HOME)
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.agents/skills
This downloads the repo to a temporary folder and copies only the folders that contain a 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
After installing
- ChatGPT desktop app: open Skills in the sidebar to see that the skill is there
- To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
- Codex picks up newly installed skills by itself; if one does not show up, restart Codex
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
ChatGPT on the web and mobile
Skills you install yourself do not work here; only skills that come with a plugin from the directory
To use this skill with ChatGPT, use the ChatGPT desktop app as above
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
Option 1Let Codex install it
Copy this sentence and paste it into a Codex chat · Works in Codex inside the ChatGPT desktop app, Codex CLI and the IDE extension
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 picks up newly installed skills by itself; if one does not show up, restart Codex · To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.agents/skills
This downloads the repo to a temporary folder and copies only the folders that contain a 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-aiRestart Codex, then ask for a matching task; Codex lists the skill
Option 1Let Cursor install it
Copy this sentence and paste it into a Cursor 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
In Cursor’s Agent chat, type / and pick typesafe-ai
Checked against official docs Nov 12, 2026 · Source: cursor.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.cursor/skills
This downloads the repo to a temporary folder and copies only the folders that contain a 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-aiIn Cursor’s Agent chat, type / and pick typesafe-ai
Option 1Let the AI install it
For other apps that read skills. The sentence gives the paths for Claude Code, Codex and Cursor so the AI picks the one for your 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 Nov 12, 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
For Terminal users
Other apps that support Agent Skills (such as Gemini CLI or GitHub Copilot) use different folders. Check that app’s guide, then copy the folder with the SKILL.md there.
Skill folders checked against the official Claude Code, Codex and Cursor guides on Nov 11, 2026
✓ Commands checked Nov 18, 2026
View the original SKILL.md
The text below comes from the maker’s repo, not from PopNx MCP
Showing the first 8,000 characters · Open the full file on 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 "WhichDiscussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
From GitHub
- GitHub stars
- 2,905
- Maker
- typesafe-ai
- License
- MIT
- Last code change
- Oct 24, 2026
- SKILL.md files in the repo (including translated copies and templates)
- 1