How do I install the Arrow Resource skill?

Run npx skillmds@latest add alexandru/arrow-resource in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Arrow Resource safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Arrow Resource?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Arrow Resource free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Arrow Resource?

alexandru (@alexandru) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Arrow Resource by alexandru — Agent Skill

Name: Arrow Resource
Author: alexandru

Arrow Resource

Kotlin + Arrow Resource lifecycle discipline with `Resource`, `ResourceScope`, `resourceScope`, and context parameters. Use for safe acquisition/release of files, streams, DB pools/connections, HTTP clients, background scopes, or multipart parts; preventing resource leaks and use-after-close bugs; designing companion `Resource` builders; using `arrow-autoclose` when only synchronous `AutoCloseable` cleanup is possible; composing resources with typed errors, cancellation, or parallel acquisition.

alexandru c1015a7 3 files · 17.2 KB Updated Sep 17, 2026

File contents

Arrow Resource (Kotlin)

Quick start

Treat every disposable handle as scoped: wrap it in Resource and acquire it only inside resourceScope, resource {}, or Resource.use.
Prefer arrow.fx.coroutines.resource.context imports for context-parameter-friendly resource, resourceScope, bind, install, and autoCloseable.
Never return a disposable value from resourceScope { ... }, resource { ... }, or resource.use { ... }; that returns a closed handle.
Classes must not allocate owned resources in ordinary constructors. Use a companion builder returning Resource<Class> or requiring context(ResourceScope).
If suspend Resource cannot be used, use arrow-autoclose/AutoCloseable with the same no-leak discipline.
Read references/resource.md before writing examples, reviews, or new APIs.

Workflow

Identify every owned disposable dependency and its release action.
Move acquisition into a Resource recipe or context(ResourceScope) builder.
Compose resources into higher-level resources with .bind() or context-parameter builders.
Keep resource handles private to the scoped object; expose operations, not the raw handle.
Execute at lifecycle boundaries with resourceScope/.use, and keep finalizers idempotent.

Usage guidance

Prefer Resource over use/try/finally for suspend finalizers, cancellation awareness, composition, or multiplatform code.
Use context parameters for scoped capabilities: context(_: ResourceScope) suspend fun acquire....
Use ExitCase when release behavior depends on success, failure, or cancellation.
Resource is FP-style ownership: acquisition and finalization are values/effects that compose; hidden side-effectful constructors are a design smell.
When changing examples, update and run the bundled scripts/verify-examples.kt check.

References

Load references/resource.md for rules, source links, and typechecked examples.

---name: arrow-resourcedescription: Kotlin + Arrow Resource lifecycle discipline with `Resource`, `ResourceScope`, `resourceScope`, and context parameters. Use for safe acquisition/release of files, streams, DB pools/connections, HTTP clients, background scopes, or multipart parts; preventing resource leaks and use-after-close bugs; designing companion `Resource` builders; using `arrow-autoclose` when only synchronous `AutoCloseable` cleanup is possible; composing resources with typed errors, cancellation, or parallel acquisition.---# Arrow Resource (Kotlin)## Quick start- Treat every disposable handle as scoped: wrap it in `Resource` and acquire it only inside `resourceScope`, `resource {}`, or `Resource.use`.- Prefer `arrow.fx.coroutines.resource.context` imports for context-parameter-friendly `resource`, `resourceScope`, `bind`, `install`, and `autoCloseable`.- Never return a disposable value from `resourceScope { ... }`, `resource { ... }`, or `resource.use { ... }`; that returns a closed handle.- Classes must not allocate owned resources in ordinary constructors. Use a companion builder returning `Resource<Class>` or requiring `context(ResourceScope)`.- If suspend `Resource` cannot be used, use `arrow-autoclose`/`AutoCloseable` with the same no-leak discipline.- Read `references/resource.md` before writing examples, reviews, or new APIs.## Workflow1. Identify every owned disposable dependency and its release action.2. Move acquisition into a `Resource` recipe or `context(ResourceScope)` builder.3. Compose resources into higher-level resources with `.bind()` or context-parameter builders.4. Keep resource handles private to the scoped object; expose operations, not the raw handle.5. Execute at lifecycle boundaries with `resourceScope`/`.use`, and keep finalizers idempotent.## Usage guidance- Prefer `Resource` over `use`/`try/finally` for suspend finalizers, cancellation awareness, composition, or multiplatform code.- Use context parameters for scoped capabilities: `context(_: ResourceScope) suspend fun acquire...`.- Use `ExitCase` when release behavior depends on success, failure, or cancellation.- `Resource` is FP-style ownership: acquisition and finalization are values/effects that compose; hidden side-effectful constructors are a design smell.- When changing examples, update and run the bundled `scripts/verify-examples.kt` check.## References- Load `references/resource.md` for rules, source links, and typechecked examples.

Frequently asked questions