📦

typesafe-ai

Name: typesafe-ai
Author: typesafe-ai

Révision du contenu r1 Sûr ⚙️ Commandes externes🌐 Accès réseau

Build Typed AI Decisions with TypeSafe

Many application features need semantic judgments, but free-form model responses are difficult to combine reliably in code. TypeSafe helps developers design small typed judgments and compose them into routing, ranking, extraction, verification, and interactive workflows.

Prend en charge: Claude Codex Code(CC)

🥉 78 Bronze

Maintain this Skill? Claim it 🥉 78 Bronze

Installer avec mon Agent

Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.

Demande d’agent

Review the Skillstore skill "typesafe-ai" from https://skillstore.io/skills/typesafe-ai-typesafe-ai.md and its manifest at https://skillstore.io/api/skills/typesafe-ai-typesafe-ai/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.

Ressources lisibles par les agents

Utilisez ces liens lorsqu’un Agent IA, un crawler ou un script a besoin d’un contexte propre au lieu de lire toute la page.

Détail Markdown GET /skills/typesafe-ai-typesafe-ai.md manifest signé GET /api/skills/typesafe-ai-typesafe-ai/manifest lockfile signé GET /api/skills/typesafe-ai-typesafe-ai/lockfile

Tester

Utilisation de « typesafe-ai ». A support application must route incoming messages to a known team and fill the team-specific fields.

Résultat attendu:

Use a routing judgment to select a team and a separate typed judgment for branch-specific arguments. Ask only the questions relevant to the selected branch, then let application code execute the handoff.

Utilisation de « typesafe-ai ». A search workflow has many retrieved candidates and needs reliable context for an answer.

Résultat attendu:

Retrieve candidates in code, judge relevance with comparable scores, select useful evidence, and send uncertain or failing cases to verification or human review.

Utilisation de « typesafe-ai ». A product team wants to replace a broad prompt that returns parsed text.

Résultat attendu:

Split the broad request into narrow judgments with explicit criteria, named state fields, typed outputs, a no-match result, and tests for representative cases.

Audit de sécurité

Sûr

v1 • 17/09/2026 Ouvrir le rapport versionné

All 26 static findings are false positives. The flagged backticks are Markdown examples, the URLs are documentation links, and the fallback guidance does not perform system reconnaissance; no semantic security findings were identified.

Fichiers analysés

172

Lignes analysées

Éléments à examiner

Faux positifs ignorés

Facteurs de risque

⚙️ Commandes externes (3)

SKILL.md:34 SKILL.md:37 SKILL.md:110

🌐 Accès réseau (22)

Le dernier audit statique et sémantique terminé n’a détecté aucun constat de sécurité confirmé. Cela ne prouve pas que le skill est sans effets secondaires.

Audité par: claude

Partager et citer ce rapport

Partagez le rapport d’évaluation versionné, le badge neutre, la carte intégrable et les citations. Skillstore présente les preuves sans décider si ce Skill est sûr.

Ouvrir le rapport versionné

Copier le lien du rapport

https://skillstore.io/skills/typesafe-ai-typesafe-ai/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Badge Markdown

[![Skillstore security assessment](https://skillstore.io/badges/skills/typesafe-ai-typesafe-ai/security.svg)](https://skillstore.io/skills/typesafe-ai-typesafe-ai?utm_source=security_passport_badge)

Badge HTML

<a href="https://skillstore.io/skills/typesafe-ai-typesafe-ai?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/typesafe-ai-typesafe-ai/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Carte intégrable

<iframe src="https://skillstore.io/embed/skills/typesafe-ai-typesafe-ai.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Citations académiques (APA · BibTeX · CFF)

Citation APA

typesafe-ai. (2026). typesafe-ai security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/typesafe-ai-typesafe-ai/audits/1

Citation BibTeX

@techreport{typesafe-ai-typesafe-ai-typesafe-ai-2026,
  author = {typesafe-ai},
  title = {typesafe-ai security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/typesafe-ai-typesafe-ai/audits/1},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "typesafe-ai security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "typesafe-ai"
date-released: "2026-09-17"
url: "https://skillstore.io/skills/typesafe-ai-typesafe-ai/audits/1"
identifiers:
  - type: other
    value: "skillstore:typesafe-ai-typesafe-ai:audit:1"
    description: "Skillstore immutable audit report identifier"

Score Skillstore

Pourquoi ce score Niveau de confiance des preuves: Moyen

Architecture

Maintenabilité

Contenu

Communauté

Conformité aux spécifications

Ce que vous pouvez créer

Plan semantic application features

Turn a product behavior into focused judgments, typed outputs, and bounded application actions.

Design evidence and review workflows

Combine retrieval, relevance judgments, confidence thresholds, verification, and human escalation.

Improve an existing model integration

Replace broad prompt-and-parse steps with reusable primitives, explicit state, and testable composition.

Essayez ces prompts

Find the right judgment

I am building [feature]. It must [observable behavior]. Identify the smallest semantic judgment it needs, the relevant state, and a suitable TypeSafe primitive. Keep deterministic rules in code.

Choose a primitive

For this decision, compare Choice, Noul, and Score: [decision]. Define what each output means, when each primitive fits, and what no-match or uncertainty outcome the application needs.

Compose a workflow

Design a TypeSafe workflow for [goal]. Separate observed state, inferred state, policies, and execution. Identify independent questions that can run together, dependent follow-up steps, thresholds, and human escalation.

Audit a production design

Review this proposed semantic workflow: [design]. Check question scope, candidate coverage, state freshness, confidence interpretation, policy handling, latency and cost, failure categories, test cases, and the boundary between model judgments and application code.

Bonnes pratiques

Start from the application behavior, then define the smallest judgment that supports it.
Keep rules, calculations, lookups, execution, and authorization in deterministic code.
Test judgments and resulting behavior with representative data, thresholds, and failure cases.

Éviter

Do not use a model judgment for exact rules, arithmetic, lookups, or permission enforcement.
Do not treat confidence as proof of correctness or reuse example thresholds without validation.
Do not send stale inferred state into actions without checking the current application state.

Foire aux questions

What is TypeSafe used for?

It helps developers add focused semantic judgments to software for routing, ranking, extraction, verification, and interactive decisions.

Which primitive should I choose?

Use Choice for one option, Noul for whether a condition holds, and Score for a degree along a defined dimension.

Does this skill write integration code?

It provides design guidance and points to API and SDK documentation. It does not implement or execute an integration.

How should I handle uncertainty?

Define thresholds using target data and consequences, include no-match outcomes, and escalate uncertain or failing cases when appropriate.

Can TypeSafe replace application logic?

No. Keep deterministic rules, calculations, lookups, execution, authorization, and workflow control in code.

What should I test?

Test representative inputs, state freshness, questions, candidates, outputs, composition, thresholds, service failures, and observed application behavior.