Cross-Language Coding Standards
zereight/gitlab-mcp
Shared reference for naming, function size, complexity and error handling rules that reviewer agents apply across TypeScript, Python, Go, Rust, Java, C# and Swift.
Configuring semantic retry policies for a TypeScript Golem agent.
Install Golem Retry Policies TS
$ npx skills add golemcloud/golem --skill golem-retry-policies-ts -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install golemcloud/golem golem-retry-policies-ts --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/golemcloud/golem.git skills-src && mkdir -p .claude/skills && cp -r skills-src/golem-skills/skills/ts/golem-retry-policies-ts .claude/skills/golem-retry-policies-ts && 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 "golem-retry-policies-ts" agent skill from https://github.com/golemcloud/golem/tree/main/golem-skills/skills/ts/golem-retry-policies-ts into .claude/skills/golem-retry-policies-ts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "golem-retry-policies-ts", 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/golemcloud/golem/tree/main/golem-skills/skills/ts/golem-retry-policies-tsType 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 golemcloud/golem --skill golem-retry-policies-ts -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install golemcloud/golem golem-retry-policies-ts --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/golemcloud/golem.git skills-src && mkdir -p .agents/skills && cp -r skills-src/golem-skills/skills/ts/golem-retry-policies-ts .agents/skills/golem-retry-policies-ts && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "golem-retry-policies-ts" agent skill from https://github.com/golemcloud/golem/tree/main/golem-skills/skills/ts/golem-retry-policies-ts into .agents/skills/golem-retry-policies-ts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "golem-retry-policies-ts", 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 golemcloud/golem --skill golem-retry-policies-ts -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install golemcloud/golem golem-retry-policies-ts --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/golemcloud/golem.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/golem-skills/skills/ts/golem-retry-policies-ts .cursor/skills/golem-retry-policies-ts && 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 "golem-retry-policies-ts" agent skill from https://github.com/golemcloud/golem/tree/main/golem-skills/skills/ts/golem-retry-policies-ts into .cursor/skills/golem-retry-policies-ts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "golem-retry-policies-ts", 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/golemcloud/golem.git --path golem-skills/skills/ts/golem-retry-policies-ts--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 golemcloud/golem --skill golem-retry-policies-ts -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install golemcloud/golem golem-retry-policies-ts --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/golemcloud/golem.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/golem-skills/skills/ts/golem-retry-policies-ts .gemini/skills/golem-retry-policies-ts && 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 "golem-retry-policies-ts" agent skill from https://github.com/golemcloud/golem/tree/main/golem-skills/skills/ts/golem-retry-policies-ts into .gemini/skills/golem-retry-policies-ts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "golem-retry-policies-ts", 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 golemcloud/golem golem-retry-policies-tsInstalls 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 golemcloud/golem --skill golem-retry-policies-ts -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/golemcloud/golem.git skills-src && mkdir -p .github/skills && cp -r skills-src/golem-skills/skills/ts/golem-retry-policies-ts .github/skills/golem-retry-policies-ts && 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 "golem-retry-policies-ts" agent skill from https://github.com/golemcloud/golem/tree/main/golem-skills/skills/ts/golem-retry-policies-ts into .github/skills/golem-retry-policies-ts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "golem-retry-policies-ts", 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 golemcloud/golem --skill golem-retry-policies-ts -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install golemcloud/golem golem-retry-policies-ts --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/golemcloud/golem.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/golem-skills/skills/ts/golem-retry-policies-ts .opencode/skills/golem-retry-policies-ts && 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 "golem-retry-policies-ts" agent skill from https://github.com/golemcloud/golem/tree/main/golem-skills/skills/ts/golem-retry-policies-ts into .opencode/skills/golem-retry-policies-ts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "golem-retry-policies-ts", 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.
Facts
- Skill name
golem-retry-policies-ts- GitHub stars
- 1.5k
- Token cost
- ~3.2k tokens
- SKILL.md length
- 998 words
- Files
- 1
- Skills in repo
- 289
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Configuring semantic retry policies for a TypeScript Golem agent.
- Works in 5 steps: Define Retry Policies in the Application… → SDK: Build and Apply Retry Policies at… → Querying Retry Policies at Runtime → …
- The user asks about retry policies
- SKILL.md covers 1. Define Retry Policies in…, 2. SDK: Build and Apply Retry…, 3. Querying Retry Policies at… and 4. Live-Editing Policies via CLI, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Golem Retry Policies TS is an agent skill from golemcloud/golem. Configuring semantic retry policies for a TypeScript Golem agent. Use when the user asks about retry policies, retry strategies, exponential backoff, error handling retries, transient error recovery, retry predicates, withRetryPolicy, NamedPolicy, Policy composition, jitter, countBox, timeBox, andThen, or customizing how failures are retried.
Its SKILL.md is about 3.2k 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 Development, covering Error handling. It works with TypeScript. The repository describes itself as: Golem Cloud is the agent-native platform for building AI agents and distributed applications that never lose state, never duplicate work, and never require you to build…
When your agent uses it
- The user asks about retry policies
- Retry strategies
- Exponential backoff
- Error handling retries
Example prompts
- “/golem-retry-policies-ts”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
- Define Retry Policies in the Application Manifest
- SDK: Build and Apply Retry Policies at Runtime
- Querying Retry Policies at Runtime
- Live-Editing Policies via CLI
- Default Retry Policy
What it can do on your machine
Read from SKILL.md and the folder at commit 8bed66c. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript, yaml and bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Golem Retry Policies TS loads about 3.2k tokens when it runs. Until then it costs about 92 tokens; SKILL.md has 998 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.
Safety
Auto-check passed
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.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 998 words (~3,225 tokens).
“Golem provides a composable, per-environment retry policy system. Policies are evaluated against error context properties and can be defined in the application manifest, managed via CLI, or created/overridden at runtime from agent code using the SDK.”
- name
- golem-retry-policies-ts
Files
Just SKILL.md in golem-skills/skills/ts/golem-retry-policies-ts of golemcloud/golem.
Open the folder on GitHubat commit 8bed66c
Compare with similar skills
Golem Retry Policies TS 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 |
|---|---|---|---|---|---|---|
| Golem Retry Policies TS this skillgolemcloud/golem | 1.5k | — | ~3.2k | Automated safety check: Pass | Custom licence | |
| Cross-Language Coding Standardszereight/gitlab-mcp | 2k | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| evlog Map Rule Creatorevloghq/evlog | 1.9k | — | ~2.9k | Automated safety check: Pass | MIT | |
| Strict Programming Practicescode-yeongyu/oh-my-openagent | 70k | — | ~9.5k | Automated safety check: Pass | Custom licence | |
| Error Causes Handlingparalleldrive/aidd | 384 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Convex Best Practicesjulianromli/ai-skills | 191 | — | ~2.4k | Automated safety check: Pass | None |
Similar skills
evlog Map Rule Creator
evloghq/evlog
Walks through adding a new rule or framework adapter to `evlog map` in @evlog/cli, from the rule source and registry to types, tests, docs and the published skill.
Strict Programming Practices
code-yeongyu/oh-my-openagent
Applies strict, type-first coding rules for Python, Rust, TypeScript and Go, loading the matching language reference before the agent writes or edits any code.
Error Causes Handling
paralleldrive/aidd
Has your agent throw and catch JavaScript and TypeScript errors with the error-causes library, using named causes, preserved originals and routed handlers.
Convex Best Practices
julianromli/ai-skills
Guidelines for building production-ready Convex apps covering function organization, query patterns, validation, TypeScript usage, error handling, and the Zen of Convex design philosophy
Typescript Rules
shinpr/ai-coding-project-boilerplate
Applies type safety and error handling rules. An agent skill from shinpr/ai-coding-project-boilerplate.
More from golemcloud/golem
All 289 skills in this repoMoonbit C Binding
golemcloud/golem
Guide for writing MoonBit bindings to C libraries using native FFI.
Adding Dependencies
golemcloud/golem
Adding or updating crate dependencies in the Golem workspace.
Analysing CI Failures
golemcloud/golem
Analysing GitHub Actions CI failures from a run URL. An agent skill from golemcloud/golem.
Creating New Builtin Plugins
golemcloud/golem
Adds a built-in WASM plugin that is externally released and provisioned by the registry service.
DB Migration Scripts
golemcloud/golem
Writing database migration SQL scripts. An agent skill from golemcloud/golem.
Debugging Hanging Tests
golemcloud/golem
Diagnosing and fixing hanging worker executor or integration tests.
Related
Works with
Categories
Questions about Golem Retry Policies TS
What does Golem Retry Policies TS do?
Configuring semantic retry policies for a TypeScript Golem agent. Golem Retry Policies TS is an agent skill from golemcloud/golem. Configuring semantic retry policies for a TypeScript Golem agent.
When should I use Golem Retry Policies TS?
Golem Retry Policies TS fits situations like: the user asks about retry policies; retry strategies; exponential backoff; error handling retries.
How do I install Golem Retry Policies TS in Claude Code?
Run `npx skills add golemcloud/golem --skill golem-retry-policies-ts -a claude-code`. Or copy the skill folder (golem-skills/skills/ts/golem-retry-policies-ts in golemcloud/golem) into .claude/skills/golem-retry-policies-ts in your project. Claude Code loads it when a task matches its description.
How do I install Golem Retry Policies TS in Codex?
Run `npx skills add golemcloud/golem --skill golem-retry-policies-ts -a codex`. Or copy the skill folder (golem-skills/skills/ts/golem-retry-policies-ts in golemcloud/golem) into .agents/skills/golem-retry-policies-ts in your project. Codex loads it when a task matches its description.
Can I use Golem Retry Policies TS in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add golemcloud/golem --skill golem-retry-policies-ts -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/golem-retry-policies-ts, .gemini/skills/golem-retry-policies-ts, .github/skills/golem-retry-policies-ts and .opencode/skills/golem-retry-policies-ts in your project.
What does Golem Retry Policies TS need to run?
SKILL.md names no scripts, command-line tools or credentials: Golem Retry Policies TS is instructions for the agent only.
Does Golem Retry Policies TS access the network?
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.
Is Golem Retry Policies TS safe to install?
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.
What licence does Golem Retry Policies TS use?
Golem Retry Policies TS has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Golem Retry Policies TS use?
About 3.2k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Golem Retry Policies TS?
Skills that share tags, products or a category with Golem Retry Policies TS: Cross-Language Coding Standards (zereight/gitlab-mcp, 2k stars), evlog Map Rule Creator (evloghq/evlog, 1.9k stars), Strict Programming Practices (code-yeongyu/oh-my-openagent, 70k stars) and Error Causes Handling (paralleldrive/aidd, 384 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Golem Retry Policies TS?
golemcloud (a GitHub organization) maintains it in golemcloud/golem, which has 1,508 GitHub stars. The repository holds 289 skills in this directory. The repository was last updated on October 10, 2026.
Source: golemcloud/golem on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.