Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
runtime--atomic-effects - Skill - OpenSmartRoute
Skillv1.0.0
runtime--atomic-effects
Validate the complete change before mutation, stage on the destination filesystem, and expose it through one atomic commit point. Partial success fails.
Instruction file imported from flext-sh/flext-db-oracle (.github/instructions/runtime--atomic-effects.instructions.md). Copyright stays with the author.
Effects publish atomically
Validate the complete change before mutation, stage on the destination
filesystem, and expose it through one atomic commit point. Partial success fails.
For mass retirement, hold serialization through postcondition and atomically
isolate each root before internal reclamation. The rename is the commit point;
sequential unlinks are cleanup, not an atomic batch. Cleanup failure remains red,
preserves its manifest, and requires causal correction plus fresh preflight.
Rollback may remove or restore only effects attributable to the current
invocation and only from already validated recovery data. Rollback failure is
attached to the original exception, which remains the exception re-raised.
Never delete unknown, foreign, live, dirty, or ownership-ambiguous state.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
yaml
targets:
- https://api.opensmartroute.ai/api/v1/registry/flext-sh-flext-db-oracle-runtime-atomic-effects-instructions/manifest # or paste the manifest below
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
{
"ocm": "1",
"id": "flext-sh-flext-db-oracle-runtime-atomic-effects-instructions",
"kind": "skill",
"name": "runtime--atomic-effects",
"description": "Validate the complete change before mutation, stage on the destination filesystem, and expose it through one atomic commit point. Partial success fails.",
"publisher": "flext-sh",
"version": "1.0.0",
"capabilities": {
"domains": [
"general"
],
"tags": [
"skill-md",
"github-instructions"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Validate the complete change before mutation, stage on the destination filesystem, and expose it through one atomic commit point. Partial success fails."
],
"primary": false,
"metadata": {
"source": {
"provider": "github-instructions",
"repository": "https://github.com/flext-sh/flext-db-oracle",
"path": ".github/instructions/runtime--atomic-effects.instructions.md",
"ref": "040ad48d2515bae968986236fc1d0f821a6d2dbf",
"url": "https://github.com/flext-sh/flext-db-oracle/blob/040ad48d2515bae968986236fc1d0f821a6d2dbf/.github/instructions/runtime--atomic-effects.instructions.md",
"key": "flext-sh/flext-db-oracle/.github/instructions/runtime--atomic-effects.instructions.md"
},
"applies_to": "**"
},
"instructions": "# Effects publish atomically\n\nValidate the complete change before mutation, stage on the destination\nfilesystem, and expose it through one atomic commit point. Partial success fails.\n\nFor mass retirement, hold serialization through postcondition and atomically\nisolate each root before internal reclamation. The rename is the commit point;\nsequential unlinks are cleanup, not an atomic batch. Cleanup failure remains red,\npreserves its manifest, and requires causal correction plus fresh preflight.\n\nRollback may remove or restore only effects attributable to the current\ninvocation and only from alr",
"cost": {
"context_tokens": 199
}
}
Fetch it by URL: GET /api/v1/registry/flext-sh-flext-db-oracle-runtime-atomic-effects-instructions/manifest?version=1.0.0
Reviews
Star ratings from people who tried it. One review per account; edit yours any time.
No reviews yet. Install it, try it, and be the first to rate it.