Mail Time
veliovgroup/mail-time
A skill your agent uses when building, wiring, reviewing, or debugging MailTime and ostrio:mailer email queues for horizontally scaled Node.js, Bun, or Meteor apps.
Locking patterns for Glommio's single-threaded async executors.
$ npx skills add celeriant/celeriant-db --skill glommio-locking-patterns -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install celeriant/celeriant-db glommio-locking-patterns --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/celeriant/celeriant-db.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/glommio-locking-patterns .claude/skills/glommio-locking-patterns && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "glommio-locking-patterns" agent skill from https://github.com/celeriant/celeriant-db/tree/main/.claude/skills/glommio-locking-patterns into .claude/skills/glommio-locking-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "glommio-locking-patterns", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/celeriant/celeriant-db/tree/main/.claude/skills/glommio-locking-patternsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add celeriant/celeriant-db --skill glommio-locking-patterns -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install celeriant/celeriant-db glommio-locking-patterns --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/celeriant/celeriant-db.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/glommio-locking-patterns .agents/skills/glommio-locking-patterns && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "glommio-locking-patterns" agent skill from https://github.com/celeriant/celeriant-db/tree/main/.claude/skills/glommio-locking-patterns into .agents/skills/glommio-locking-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "glommio-locking-patterns", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add celeriant/celeriant-db --skill glommio-locking-patterns -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install celeriant/celeriant-db glommio-locking-patterns --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/celeriant/celeriant-db.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/glommio-locking-patterns .cursor/skills/glommio-locking-patterns && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "glommio-locking-patterns" agent skill from https://github.com/celeriant/celeriant-db/tree/main/.claude/skills/glommio-locking-patterns into .cursor/skills/glommio-locking-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "glommio-locking-patterns", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/celeriant/celeriant-db.git --path .claude/skills/glommio-locking-patterns--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add celeriant/celeriant-db --skill glommio-locking-patterns -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install celeriant/celeriant-db glommio-locking-patterns --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/celeriant/celeriant-db.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/glommio-locking-patterns .gemini/skills/glommio-locking-patterns && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "glommio-locking-patterns" agent skill from https://github.com/celeriant/celeriant-db/tree/main/.claude/skills/glommio-locking-patterns into .gemini/skills/glommio-locking-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "glommio-locking-patterns", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install celeriant/celeriant-db glommio-locking-patternsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add celeriant/celeriant-db --skill glommio-locking-patterns -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/celeriant/celeriant-db.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/glommio-locking-patterns .github/skills/glommio-locking-patterns && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "glommio-locking-patterns" agent skill from https://github.com/celeriant/celeriant-db/tree/main/.claude/skills/glommio-locking-patterns into .github/skills/glommio-locking-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "glommio-locking-patterns", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add celeriant/celeriant-db --skill glommio-locking-patterns -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install celeriant/celeriant-db glommio-locking-patterns --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/celeriant/celeriant-db.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/glommio-locking-patterns .opencode/skills/glommio-locking-patterns && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "glommio-locking-patterns" agent skill from https://github.com/celeriant/celeriant-db/tree/main/.claude/skills/glommio-locking-patterns into .opencode/skills/glommio-locking-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "glommio-locking-patterns", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
glommio-locking-patternsLocking patterns for Glommio's single-threaded async executors.
Glommio Locking Patterns is an agent skill from celeriant/celeriant-db. Locking patterns for Glommio's single-threaded async executors. Use when working with shard read/write paths, replication, or any async code needing synchronization. Critical for avoiding deadlocks.
Its SKILL.md is about 880 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Databases. The repository describes itself as: Fast, distributed per-aggregate event log with strict ordering and optimistic concurrency control. The licence is Apache-2.0.
3 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit d071a6d. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Glommio Locking Patterns loads about 876 tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 435 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from celeriant/celeriant-db at commit d071a6d, republished under its Apache-2.0 licence (© celeriant). 435 words, ~876 tokens.
.claude/skills/glommio-locking-patterns/SKILL.md (or your agent's skills folder).Glommio is single-threaded per executor. No thread contention, but async tasks interleave at .await points. The one rule that matters:
Never hold a RefCell borrow across an .await boundary. Another task will try to borrow while you're suspended. Deadlock under load.
RefCell when all operations on the data are synchronous. No .await while borrowed.
Glommio RwLock when you need to hold across async operations (file I/O, network). More overhead, but safe across .await.
If you're unsure, ask: will I .await while holding this? Yes = RwLock. No = RefCell.
The core pattern for working with RefCell-wrapped state:
This is how the fsync path works. take_sync_positions_snapshot() clones queue positions and swaps out the pending queue, then the borrow drops. Async disk I/O happens with no borrow held. Then commit or rollback re-borrows briefly.
All RwLock acquisitions use read_with_timeout / write_with_timeout wrappers with a 1-second deadline. Timeout returns PotentialDeadlock error with a location string instead of blocking forever. This catches bugs during development and prevents stuck tasks under high load.
Always use these wrappers. Always pass a descriptive location string.
See celeriant_rotating_log/src/rwlock_timeout.rs.
When multiple async tasks want the same cold aggregate from disk, only one does the I/O. Others wait on a per-key RwLock, then double-check the cache. Without the double-check after acquiring the lock, you get duplicate I/O.
See celeriant_shard/src/loading_coordinator.rs.
Multiple concurrent writers coalesce into one fsync. First caller becomes leader (sleeps for configurable delay to accumulate followers), then performs the sync and broadcasts the result via LocalEvent. Followers never call the sync function. At most one sync executes at a time.
Key subtlety: the snapshot is captured before the queue is cleared. Reversing this loses writes that arrive between clear and snapshot.
See celeriant_shard/src/amortisation/coordinator.rs.
Glommio Semaphore limits how many async tasks can do expensive work concurrently:
list_semaphore: bounds concurrent list operations. Lists allocate unbudgeted per-request memory, so unlimited concurrency can exhaust RAM.cache_load_semaphore: bounds concurrent cache-miss disk scans. Without this, cold start read amplification saturates NVMe reads and starves the fsync write path.Both configured via list_max_concurrent and read_max_concurrent in shard config.
The sync_gate: RwLock<()> in the amortisation coordinator serialises fsync execution and supports rollback. Normal fsyncs acquire a read lock (concurrent reads OK, one-at-a-time via the coordinator). Rollback acquires the write lock, which drains all in-flight fsyncs and blocks new ones until rollback completes.
© celeriant, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .claude/skills/glommio-locking-patterns of celeriant/celeriant-db.
Open the folder on GitHubat commit d071a6d
Glommio Locking Patterns next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Glommio Locking Patterns this skillceleriant/celeriant-db | 114 | — | ~876 | Automated safety check: Pass | Apache-2.0 | |
| Mail Timeveliovgroup/mail-time | 143 | — | ~1k | Automated safety check: Pass | BSD-3-Clause | |
| Tgf Server Devthkhxm/tgf | 128 | — | ~1.3k | Automated safety check: Notes | MIT | |
| Azure Storagemicrosoft/GitHub-Copilot-for-Azure | 255 | 2 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Configure REST Cachestrapi-community/plugin-rest-cache | 155 | — | ~1.1k | Automated safety check: Pass | MIT | |
| ArchitectYougLin-dev/Aha-Loop | 181 | — | ~2.2k | Automated safety check: Pass | MIT |
veliovgroup/mail-time
A skill your agent uses when building, wiring, reviewing, or debugging MailTime and ostrio:mailer email queues for horizontally scaled Node.js, Bun, or Meteor apps.
thkhxm/tgf
基于 tgf v2(github.com/thkhxm/tgf/v2)用确定性的 tgfctl 工作流创建、验证和维护 Go 游戏服务器项目。
microsoft/GitHub-Copilot-for-Azure
Azure Storage Services including Blob Storage, File Shares, Queue Storage, Table Storage, and Data Lake.
strapi-community/plugin-rest-cache
Choose and write a Strapi REST Cache configuration for a specific use case.
YougLin-dev/Aha-Loop
Designs system architecture and selects technology stack based on vision analysis.
pockethost/pockethost
Models PocketBase backends: collections, relations, auth, API rules, migrations, and architecture.
celeriant/celeriant-db
Error handling patterns in Celeriant. An agent skill from celeriant/celeriant-db.
celeriant/celeriant-db
How to write and run tests in Celeriant. An agent skill from celeriant/celeriant-db.
celeriant/celeriant-db
Celeriant codebase architecture, crate responsibilities, and how they fit together.
celeriant/celeriant-db
Refactor a named Rust type or its surrounding code with an agreed scope.
celeriant/celeriant-db
Celeriant's client-server protocol invariants, network behavior, failure modes, and shard routing.
celeriant/celeriant-db
Core architecture invariants for Celeriant. An agent skill from celeriant/celeriant-db.
Categories
Locking patterns for Glommio's single-threaded async executors. Glommio Locking Patterns is an agent skill from celeriant/celeriant-db. Locking patterns for Glommio's single-threaded async executors.
Glommio Locking Patterns fits situations like: working with shard read/write paths; any async code needing synchronization.
Run `npx skills add celeriant/celeriant-db --skill glommio-locking-patterns -a claude-code`. Or copy the skill folder (.claude/skills/glommio-locking-patterns in celeriant/celeriant-db) into .claude/skills/glommio-locking-patterns in your project. Claude Code loads it when a task matches its description.
Run `npx skills add celeriant/celeriant-db --skill glommio-locking-patterns -a codex`. Or copy the skill folder (.claude/skills/glommio-locking-patterns in celeriant/celeriant-db) into .agents/skills/glommio-locking-patterns in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add celeriant/celeriant-db --skill glommio-locking-patterns -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/glommio-locking-patterns, .gemini/skills/glommio-locking-patterns, .github/skills/glommio-locking-patterns and .opencode/skills/glommio-locking-patterns in your project.
SKILL.md names no scripts, command-line tools or credentials: Glommio Locking Patterns is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Glommio Locking Patterns is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 876 tokens (SKILL.md is roughly 3.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Glommio Locking Patterns: Mail Time (veliovgroup/mail-time, 143 stars), Tgf Server Dev (thkhxm/tgf, 128 stars), Azure Storage (microsoft/GitHub-Copilot-for-Azure, 255 stars) and Configure REST Cache (strapi-community/plugin-rest-cache, 155 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
celeriant (a GitHub organization) maintains it in celeriant/celeriant-db, which has 114 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on September 28, 2026.
Source: celeriant/celeriant-db on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.