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 자동화와 에이전트
제작자용: README에 배지 달기
제작자라면 이 코드를 README에 붙여 넣으세요. 배지는 이 페이지로 연결됩니다.
[](https://mcp.popnx.com/en/skills/typesafe-ai-skills)비슷한 Skill
같은 종류의 작업, Skill 목록과 같은 순서
typesafe-ai의 Skill(지시 묶음) 1개, AI가 읽고 그대로 일해요 · MCP server가 아니에요
Skill과 MCP의 차이
MCP = 손
AI를 외부 서비스나 데이터에 연결합니다(예: Notion 읽기, 청구서 만들기). 프로그램이나 서버가 실행 중이어야 합니다.
Skill = 안내서
작업 방법을 AI에게 가르치는 텍스트 파일. 어떤 서비스에도 연결되지 않습니다.
겹치는 경우도 있습니다. 도구를 부르는 스크립트가 있는 Skill도, 지식만 보내는 MCP도 있습니다. 하려는 작업을 기준으로 고르세요.
쓸 수 있는 앱
Claude Code
제작자 README와 repo 폴더 기준
설치
Is it safe?
- Who made it
GitHub account typesafe-ai (organization), 2 years old
- Use and upkeep
★ 2,905 stars · code last changed 2026년 10월 24일
- 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
먼저: 어떤 AI를 쓰시나요
쓰는 앱을 고르면 그 앱의 설치 방법만 보여 드립니다
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에게 설치 맡기기
이 문장을 복사해 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
Claude Code를 다시 열고 /typesafe-ai를 입력하거나 관련 작업을 요청하면 Claude가 알아서 써요
Checked against official docs 2026년 11월 12일 · Source: code.claude.com
For Terminal users
Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
제작자가 권하는 방법
Node.js 설치 (아직 없다면)
이미 설치했나요? 먼저 확인 · 터미널을 열고 이 명령을 입력한 뒤 Enter
node -v- 버전 번호(예: v26.13.1)가 나오면 설치된 것입니다. 이 단계는 건너뛰세요
- "command not found"(Windows는 "is not recognized")가 나오면 아직 설치하지 않았거나, 방금 설치해서 터미널을 닫았다가 다시 열어야 합니다
터미널 여는 법
Mac: ⌘ + Space를 누르고 Terminal 입력 후 Enter
Windows: 시작 메뉴를 열고 Windows PowerShell 입력 후 "열기"
아직 설치하지 않았다면: 공식 다운로드 페이지에서 LTS 버전과 클릭형 설치 파일을 고르세요: Mac은 .pkg · Windows는 .msi. 더블클릭 후 끝까지 진행하면 됩니다. curl 명령은 필요 없습니다
설치가 끝나면 터미널을 닫았다가 다시 열고 같은 명령을 실행하세요. 버전 번호가 나와야 합니다: node -v
한 번 설치하면 Node.js가 필요한 모든 도구에서 쓸 수 있습니다
npx skills add typesafe-ai/skills --skill typesafe-ai제작자 README에서 가져온 명령으로, 제작자 코드를 내려받아 실행해요
터미널 열기
Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요
skill 폴더를 ~/.claude/skills에 복사
repo를 임시 폴더에 내려받고 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-aiClaude Code를 다시 열고 /typesafe-ai를 입력하거나 관련 작업을 요청하면 Claude가 알아서 써요
ChatGPT 데스크톱 앱
ChatGPT 데스크톱 앱에는 Codex가 들어 있고, Codex는 ~/.agents/skills 폴더에서 Skill을 읽습니다
Option 1ChatGPT에게 설치 맡기기
ChatGPT 데스크톱 앱에서 Codex를 열고 이 문장을 채팅에 붙여 넣으세요
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 2폴더를 직접 넣기
typesafe-ai 폴더를 ~/.agents/skills/typesafe-ai에 넣으세요
~는 홈 폴더($HOME)입니다
For Terminal users
Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
터미널 열기
Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요
skill 폴더를 ~/.agents/skills에 복사
repo를 임시 폴더에 내려받고 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
설치한 뒤
- ChatGPT 데스크톱 앱: 사이드바에서 Skills를 열어 Skill이 보이는지 확인하세요
- 쓰는 법: ChatGPT에서는 @를 입력하고 Skill을 고르세요 · Codex CLI나 IDE 확장 프로그램에서는 /skills를 실행하거나 $ 뒤에 Skill 이름을 입력하세요
- Codex는 새로 설치한 Skill을 스스로 찾습니다. 보이지 않으면 Codex를 다시 시작하세요
Checked against official docs 2026년 11월 15일 · Source: learn.chatgpt.com
웹과 모바일의 ChatGPT
직접 설치한 Skill은 쓸 수 없고, 디렉터리의 플러그인에 들어 있는 Skill만 쓸 수 있습니다
이 Skill을 ChatGPT에서 쓰려면 위 방법대로 ChatGPT 데스크톱 앱을 쓰세요
Checked against official docs 2026년 11월 15일 · Source: learn.chatgpt.com
Option 1Codex에게 설치 맡기기
이 문장을 복사해 Codex 채팅에 붙여 넣으세요 · ChatGPT 데스크톱 앱 안의 Codex, Codex CLI, 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는 새로 설치한 Skill을 스스로 찾습니다. 보이지 않으면 Codex를 다시 시작하세요 · 쓰는 법: ChatGPT에서는 @를 입력하고 Skill을 고르세요 · Codex CLI나 IDE 확장 프로그램에서는 /skills를 실행하거나 $ 뒤에 Skill 이름을 입력하세요
Checked against official docs 2026년 11월 15일 · Source: learn.chatgpt.com
For Terminal users
Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
터미널 열기
Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요
skill 폴더를 ~/.agents/skills에 복사
repo를 임시 폴더에 내려받고 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-aiCodex를 다시 열고 관련 작업을 요청하면 Codex가 skill을 목록에 보여 줘요
Option 1Cursor에게 설치 맡기기
이 문장을 복사해 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
Cursor Agent 채팅에서 /를 입력하고 typesafe-ai 선택
Checked against official docs 2026년 11월 12일 · Source: cursor.com
For Terminal users
Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
터미널 열기
Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요
skill 폴더를 ~/.cursor/skills에 복사
repo를 임시 폴더에 내려받고 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-aiCursor Agent 채팅에서 /를 입력하고 typesafe-ai 선택
Option 1Let the AI install it
Skill을 읽을 수 있는 다른 앱용입니다. 이 문장에는 Claude Code, Codex, Cursor 경로가 들어 있어 AI가 쓰는 앱에 맞게 고릅니다 · 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 2026년 11월 12일 · Source: code.claude.com, learn.chatgpt.com, cursor.com
For Terminal users
Gemini CLI, GitHub Copilot 같은 다른 Agent Skills 지원 앱은 폴더가 달라요. 그 앱 안내를 보고 SKILL.md가 있는 폴더를 복사하세요.
2026년 11월 11일에 Claude Code, Codex, Cursor 공식 안내로 skill 폴더 확인
✓ 명령 확인 2026년 11월 18일
원본 SKILL.md 보기
아래 글은 제작자 repo에서 온 것이며 PopNx MCP의 지시가 아니에요
처음 8,000자 표시 · 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 "Which토론
질문하고, 팁을 나누고, 안 되는 점을 알려 주세요. "도움이 됨"이 많은 순서예요.
GitHub 정보
- GitHub 스타
- 2,905
- 제작자
- typesafe-ai
- 라이선스
- MIT
- 최근 코드 수정
- 2026년 10월 24일
- repo 안 SKILL.md(번역본과 템플릿 포함)
- 1