fp-ts-errors
Build Type-Safe Errors with fp-ts
Unchecked exceptions make TypeScript failures difficult to track. This skill teaches practical Either and TaskEither patterns for explicit, composable error handling.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "fp-ts-errors" from https://skillstore.io/skills/sickn33-fp-ts-errors.md and its manifest at https://skillstore.io/api/skills/sickn33-fp-ts-errors/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "fp-ts-errors". Refactor a JSON parser that currently throws exceptions.
Expected outcome:
The response describes an Either-based parser, defines the error channel, and explains how callers handle both outcomes.
Using "fp-ts-errors". Design validation for email, password, and age fields.
Expected outcome:
- A validation plan that preserves field-specific errors.
- An explanation of applicative validation for collecting every failure.
- Guidance for presenting errors at the form boundary.
Using "fp-ts-errors". Wrap user loading and related requests with TaskEither.
Expected outcome:
The response outlines a lazy asynchronous pipeline, typed transport errors, parallel work, retries, and final result handling.
Security Audit
SafeThe audit reviewed all 100 static findings in SKILL.md. Every match is a false positive caused by Markdown formatting, TypeScript examples, repository metadata, or ordinary application logic; no executable shell behavior, host reconnaissance, prompt injection, or skill-initiated network access was found.
Risk Factors
⚙️ External commands (50)
🌐 Network access (5)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-fp-ts-errors/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-fp-ts-errors?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-fp-ts-errors?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-fp-ts-errors/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-fp-ts-errors.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). fp-ts-errors security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-fp-ts-errors/audits/5BibTeX citation
@techreport{sickn33-sickn33-fp-ts-errors-2026,
author = {sickn33},
title = {fp-ts-errors security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-fp-ts-errors/audits/5},
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: "fp-ts-errors security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/sickn33-fp-ts-errors/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-fp-ts-errors:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Refactor Exception-Based Code
Replace hidden exceptions with typed Either results and explicit handling paths.
Design Reliable Service Pipelines
Compose database and API operations with TaskEither, typed failures, retries, and fallbacks.
Collect Form Validation Errors
Build validators that report every field failure instead of stopping after the first error.
Try These Prompts
Explain Either, Left, and Right using a simple TypeScript parsing example.
Refactor my throwing TypeScript function into Either and explain each error type.
Design fp-ts validation for these fields and return all failures with field-specific messages.
Design a TaskEither workflow for these API and database steps, including typed errors, retries, fallbacks, and final handling.
Best Practices
- Define precise error types before composing business operations.
- Convert exceptions, nullable values, and promises at system boundaries.
- Handle both error and success branches once at the edge of the workflow.
Avoid
- Do not hide failures with broad defaults when callers need error details.
- Do not mix unchecked exceptions into an otherwise typed Either pipeline.
- Do not retry every failure without limits or error classification.