haskell-pro
Build Reliable Haskell Systems
Complex Haskell designs can hide unsafe assumptions, unclear effects, and performance problems. This skill provides practical guidance for typed architecture, concurrency, parsing, testing, and builds.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "haskell-pro" from https://skillstore.io/skills/sickn33-haskell-pro.md and its manifest at https://skillstore.io/api/skills/sickn33-haskell-pro/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 "haskell-pro". Review a parser that mixes validation, file access, and error formatting.
Expected outcome:
The response separates pure parsing from file access, recommends typed errors, identifies partial cases, and proposes parser properties.
Using "haskell-pro". Design an order workflow that prevents payment before validation.
Expected outcome:
The response models workflow states with distinct types, limits valid transitions, explains constructor visibility, and outlines property-based tests.
Using "haskell-pro". Investigate unstable latency in an STM worker system.
Expected outcome:
The response requests profiling evidence, reviews transaction size and contention, checks cancellation behavior, and defines measurable verification steps.
Security Audit
SafeThe only static finding is false: line 24 formats a relative documentation path with Markdown backticks and does not execute a command. No prompt injection or other intent-level security issue was found in SKILL.md.
Risk Factors
⚙️ External commands (1)
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-haskell-pro/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-haskell-pro?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-haskell-pro?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-haskell-pro/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-haskell-pro.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). haskell-pro security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-haskell-pro/audits/5BibTeX citation
@techreport{sickn33-sickn33-haskell-pro-2026,
author = {sickn33},
title = {haskell-pro security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-haskell-pro/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: "haskell-pro security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/sickn33-haskell-pro/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-haskell-pro:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Model a New Domain
Turn business rules into explicit types, validated constructors, and pure transformations.
Review Concurrent Code
Assess STM, async, cancellation, and exception handling for clear ownership and reliable behavior.
Strengthen a Haskell Project
Improve module boundaries, build configuration, parsing, tests, and dependency practices.
Try These Prompts
Explain and improve this Haskell function: [paste function]. Identify partial behavior, clarify its type signature, and propose focused tests.
Model these domain rules in Haskell: [rules]. Use the simplest types that prevent invalid states and explain each design decision.
Review this concurrent Haskell design: [description or code]. Analyze STM boundaries, cancellation, exceptions, resource cleanup, and test strategy.
Create a staged refactor plan for this Haskell project: [context]. Address module design, effects, dependencies, profiling, compatibility, migration risks, and verification.
Best Practices
- Provide compiler version, dependency versions, constraints, and expected behavior.
- Include minimal relevant code and exact build, test, or profiling errors.
- Validate recommendations with compilation, tests, benchmarks, and representative workloads.
Avoid
- Do not request advanced type features without a concrete invariant or maintenance benefit.
- Do not optimize from source inspection alone when profiling data is available.
- Do not apply generated changes without checking compiler compatibility and project tests.