How do I install the Pure Managed Closure skill?

Run npx skillmds@latest add devolutions/pure-managed-closure 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 Pure Managed Closure 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 Pure Managed Closure?

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 Pure Managed Closure free to use?

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

Who published Pure Managed Closure?

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

Pure Managed Closure by devolutions

Name: Pure Managed Closure
Author: devolutions

Pure Managed Closure

The enforced "no native/Rust/P-Invoke" invariant of the Ahtola build. Use this before adding any PackageReference, dependency, or interop to shipped library code, and whenever a build fails with a managed-closure error.

devolutions ef2b831 2.8 KB Updated Sep 17, 2026

File contents

Pure-managed closure

Ahtola ships no native companion, no Rust toolchain, no P/Invoke SDK. Two scripts police this automatically and run during normal build/pack/validate flows. Treat any violation as a hard error, not a warning.

What is scanned

build.ps1 → Assert-ManagedProjectClosure regex-scans Directory.Build.props/.targets, Ahtola.slnx, and every .csproj/ .props/.targets under src/Ahtola.* and samples/ManagedPackageConsumer against $NativeLeakPattern.

scripts/Validate-ManagedPackageClosure.ps1 validates built .nupkg entries, project.assets.json, and publish output against the same idea plus a native-archive-entry pattern (runtimes/, native/, Ahtola.Raw.dll, libAhtola_sdk_kit.*, etc.).

What the pattern rejects

$NativeLeakPattern matches, among others: Ahtola.Raw, Ahtola.Data.(Native|Sync), Ahtola.Data.Sqlite.(Native*|Sync), cargo, rustc, cargo-ndk, turso_sdk_kit, DirectPInvoke, NativeLibrary, DllImport, LibraryImport, TursoUseStaticNativeLibrary.

Rules

Do not add PackageReferences to Ahtola.Raw, Ahtola.Data.Native, Ahtola.Data.Sync, or any Turso.* companion in shipped projects.
Do not add DllImport/LibraryImport to shipped library code.
Do not add a dependency whose transitive graph brings a runtimes/<rid>/native/ asset into a shipped nupkg.
The only intentional OS P/Invoke is inside Ahtola.Core/Storage for page/WAL byte-range locks and shared-memory mapping. That is engine code, not an SDK binding, and stays — do not spread it elsewhere.

If the closure check fails

Read which file and which pattern matched (the error names both).
If it is a real leak (native ref, DllImport, Rust tooling), remove it — do not widen the pattern.
If it is the one allowed P/Invoke in Ahtola.Core/Storage, it is already exempt; the failure means you added a new one. Reconsider whether you actually need OS interop (you almost certainly don't).
Never silence the check with #pragma/UnconditionalSuppressMessage or by excluding a file from the scan to land a native dependency.

Intentional Turso companion strings (do not "clean up")

AhtolaNativeProvider/AhtolaReplicaProvider/SqliteNativeProvider load optional companion assemblies by name (Turso.Data.Native, Turso.Data.Sync) and fail closed when absent. Those companions are not shipped from this repo. The string match is intentional; renaming is a product decision, not a refactor.

---name: pure-managed-closuredescription: The enforced "no native/Rust/P-Invoke" invariant of the Ahtola build. Use this before adding any PackageReference, dependency, or interop to shipped library code, and whenever a build fails with a managed-closure error.---# Pure-managed closureAhtola ships **no native companion, no Rust toolchain, no P/Invoke SDK**. Twoscripts police this automatically and run during normal build/pack/validateflows. Treat any violation as a hard error, not a warning.## What is scanned`build.ps1` → `Assert-ManagedProjectClosure` regex-scans`Directory.Build.props`/`.targets`, `Ahtola.slnx`, and every `.csproj`/`.props`/`.targets` under `src/Ahtola.*` and `samples/ManagedPackageConsumer`against `$NativeLeakPattern`.`scripts/Validate-ManagedPackageClosure.ps1` validates built `.nupkg` entries,`project.assets.json`, and publish output against the same idea **plus** anative-archive-entry pattern (`runtimes/`, `native/`, `Ahtola.Raw.dll`,`libAhtola_sdk_kit.*`, etc.).## What the pattern rejects`$NativeLeakPattern` matches, among others: `Ahtola.Raw`,`Ahtola.Data.(Native|Sync)`, `Ahtola.Data.Sqlite.(Native*|Sync)`, `cargo`,`rustc`, `cargo-ndk`, `turso_sdk_kit`, `DirectPInvoke`, `NativeLibrary`,`DllImport`, `LibraryImport`, `TursoUseStaticNativeLibrary`.## Rules- Do **not** add `PackageReference`s to `Ahtola.Raw`, `Ahtola.Data.Native`, `Ahtola.Data.Sync`, or any `Turso.*` companion in shipped projects.- Do **not** add `DllImport`/`LibraryImport` to shipped library code.- Do **not** add a dependency whose transitive graph brings a `runtimes/<rid>/native/` asset into a shipped nupkg.- The **only** intentional OS P/Invoke is inside `Ahtola.Core/Storage` for page/WAL byte-range locks and shared-memory mapping. That is engine code, not an SDK binding, and stays — do not spread it elsewhere.## If the closure check fails1. Read which file and which pattern matched (the error names both).2. If it is a real leak (native ref, `DllImport`, Rust tooling), remove it — do not widen the pattern.3. If it is the one allowed P/Invoke in `Ahtola.Core/Storage`, it is already exempt; the failure means you added a *new* one. Reconsider whether you actually need OS interop (you almost certainly don't).4. Never silence the check with `#pragma`/`UnconditionalSuppressMessage` or by excluding a file from the scan to land a native dependency.## Intentional Turso companion strings (do not "clean up")`AhtolaNativeProvider`/`AhtolaReplicaProvider`/`SqliteNativeProvider` loadoptional companion assemblies *by name* (`Turso.Data.Native`,`Turso.Data.Sync`) and fail closed when absent. Those companions are **notshipped from this repo**. The string match is intentional; renaming is aproduct decision, not a refactor.

Frequently asked questions