Agent skill

Write Code

Rust code style and conventions for Syncpack. An agent skill from JamieMason/syncpack.

MITAuto-check passedDevelopment

Install Write Code

skills CLI

$ npx skills add JamieMason/syncpack --skill write-code -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install JamieMason/syncpack write-code --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/JamieMason/syncpack.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/write-code .claude/skills/write-code && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "write-code" agent skill from https://github.com/JamieMason/syncpack/tree/main/.claude/skills/write-code into .claude/skills/write-code/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-code", 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

$skill-installer install https://github.com/JamieMason/syncpack/tree/main/.claude/skills/write-code

Type 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.

skills CLI

$ npx skills add JamieMason/syncpack --skill write-code -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install JamieMason/syncpack write-code --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/JamieMason/syncpack.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/write-code .agents/skills/write-code && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "write-code" agent skill from https://github.com/JamieMason/syncpack/tree/main/.claude/skills/write-code into .agents/skills/write-code/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-code", 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.

skills CLI

$ npx skills add JamieMason/syncpack --skill write-code -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install JamieMason/syncpack write-code --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/JamieMason/syncpack.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/write-code .cursor/skills/write-code && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "write-code" agent skill from https://github.com/JamieMason/syncpack/tree/main/.claude/skills/write-code into .cursor/skills/write-code/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-code", 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

$ gemini skills install https://github.com/JamieMason/syncpack.git --path .claude/skills/write-code

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add JamieMason/syncpack --skill write-code -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install JamieMason/syncpack write-code --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/JamieMason/syncpack.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/write-code .gemini/skills/write-code && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "write-code" agent skill from https://github.com/JamieMason/syncpack/tree/main/.claude/skills/write-code into .gemini/skills/write-code/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-code", 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.

GitHub CLI

$ gh skill install JamieMason/syncpack write-code

Installs 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).

skills CLI

$ npx skills add JamieMason/syncpack --skill write-code -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/JamieMason/syncpack.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/write-code .github/skills/write-code && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "write-code" agent skill from https://github.com/JamieMason/syncpack/tree/main/.claude/skills/write-code into .github/skills/write-code/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-code", 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.

skills CLI

$ npx skills add JamieMason/syncpack --skill write-code -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install JamieMason/syncpack write-code --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/JamieMason/syncpack.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/write-code .opencode/skills/write-code && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "write-code" agent skill from https://github.com/JamieMason/syncpack/tree/main/.claude/skills/write-code into .opencode/skills/write-code/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-code", 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: write-code
GitHub stars: 2.1k
Token cost: ~944 tokens
SKILL.md length: 302 words
Files: 1
Skills in repo: 11
Repo updated: Sep 26, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Rust code style and conventions for Syncpack. An agent skill from JamieMason/syncpack.

Modifying Rust code
SKILL.md covers Style, Imports, File Organisation and Quality, plus 2 more sections
Calls just

What it does

Write Code is an agent skill from JamieMason/syncpack. Rust code style and conventions for Syncpack. Use when writing or modifying Rust code. Covers functional patterns, imports, naming, and quality standards.

Its SKILL.md is about 940 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. It works with Rust. The repository describes itself as: Consistent dependency versions in large JavaScript Monorepos. The licence is MIT.

When your agent uses it

Modifying Rust code

Example prompts

“/write-code”

What it can do on your machine

Read from SKILL.md and the folder at commit 958d306. 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
Shell commands in SKILL.md call:
- just
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

Write Code loads about 944 tokens when it runs. Until then it costs about 41 tokens; SKILL.md has 302 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~41
When it runs · the whole SKILL.md, loaded when a task matches: ~944

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

The full file from JamieMason/syncpack at commit 958d306, republished under its MIT licence (© JamieMason). 302 words, ~944 tokens.

Download SKILL.mdSave it as .claude/skills/write-code/SKILL.md (or your agent's skills folder).

name: write-code
description: Rust code style and conventions for Syncpack. Use when writing or modifying Rust code. Covers functional patterns, imports, naming, and quality standards.

Write Code

Rust code conventions for Syncpack.

Style

Functional style: pipelines over loops
Avoid ? chains: use .and_then(), .map(), .or_else()
Descriptive names: clarity over brevity
Named placeholders: println!("{var}") not println!("{}", var)
British English: "behaviour" not "behavior", "organised" not "organized"

Imports

Single use statement with grouped braces:

rust

use {
  crate::{cli::Cli, config::Config},
  log::{debug, error},
  std::{process::exit, sync::Arc},
};

Rules:

Never use super:: — always crate:: for internal imports
Group: crate::, external crates, std::
Alphabetise within groups

File Organisation

Adding...	Location
New command	`src/commands/{name}.rs`
New test	Sibling `_test.rs` file (e.g., `src/foo.rs` → `src/foo_test.rs`)

NEVER use #[cfg(test)] modules inside implementation files.

Quality

Functions <50 lines, commands 100-300 lines
Zero warnings (except during TDD red phase)
Run just format before committing

Comments

Forbidden

//! module docs — collect implementation history and rot
Phase/F-N labels — // Phase v4-2, // F16:, banner headers like // ---------- Phase v4-3 RED ----------
History refs — Migrated from, carry-over, Mirrors v3, replaces the v3, previously inside X, reserved for future
Issue/PR refs — Reproduces issue #239, GitHub issue #206. Plans rot; the code is the truth
Banner separators — // ---------- Free functions: yaml ops ----------. Use module structure or let the file speak for itself
Test scenario labels — don't write // Windows-style backslashes above a test input. Use a descriptive variable binding (let windows_backslashes = [...]) instead
Name-restating field docs — /// A unique identifier for this instance, /// The dependency name, /// The instance id. The field name already says it
Step numbering inside functions — // 1. ..., // 2. .... Drop the numbers; keep the WHY if it's non-obvious

Allowed

@TODO markers — future plans worth tracking inline
/// doc comments for non-obvious detail: None/Err semantics, side effects, invariants, distinctions between similar fields (e.g. is_local_dependency vs is_local_instance)
// inline comments when WHY is non-obvious: hidden constraints, ordering invariants ("SnappedTo groups must be visited last"), workarounds for surprising library behaviour, "must not poison X" cautions

Default

No comments. Add one only when the WHY is non-obvious to a fresh reader.

Patterns

Iterating Instances

rust

ctx.version_groups.iter().for_each(|group| {
    group.get_sorted_dependencies(&ctx.config.cli.sort).for_each(|dependency| {
        dependency.get_sorted_instances()
            .filter(|instance| instance.is_invalid())
            .for_each(|instance| { /* process */ });
    });
});

Error Handling

Prefer combinators over ?:

rust

// Good
path.parent()
    .and_then(|p| p.to_str())
    .map(|s| s.to_string())
    .unwrap_or_default()

// Avoid
let parent = path.parent()?;
let str = parent.to_str()?;
Ok(str.to_string())

State Mutation

rust

let mut state = instance.state.borrow_mut();
if !state.is_invalid() {
    *state = InstanceState::fixable(SomeVariant);
}

Files

Just SKILL.md in .claude/skills/write-code of JamieMason/syncpack.

Open the folder on GitHubat commit 958d306

Compare with similar skills

Write Code 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.

Write Code compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Write Code this skillJamieMason/syncpack	2.1k	—	~944	Automated safety check: Pass	MIT	11 days ago
Migrate Core Code to Submodulestinyhumansai/openhuman	41k	—	~2.6k	Automated safety check: Pass	GPL-3.0	yesterday
Rust Best Practicesfarm-fe/farm	5.6k	3 repos	~1.1k	Automated safety check: Pass	MIT	15 days ago
OpenLogi macOS Permissions TriageAprilNEA/OpenLogi	23k	—	~2.5k	Automated safety check: Notes	Apache-2.0	4 days ago
RTK Rust Design Patternsrtk-ai/rtk	83k	—	~1.9k	Automated safety check: Pass	Apache-2.0	yesterday
Release Skillsnexmoe/eve	421	3 repos	~3.3k	Automated safety check: Pass	None	6 mo ago

Similar skills

Migrate Core Code to Submodules
tinyhumansai/openhuman
Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.
41k GitHub stars~2.6k tokensUpdated yesterday
DevelopmentAuto-check passed
Rust Best Practices
farm-fe/farm
Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook.
5.6k GitHub starsUsed in 3 repos~1.1k tokens
DevelopmentAuto-check passed
OpenLogi macOS Permissions Triage
AprilNEA/OpenLogi
Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.
23k GitHub stars~2.5k tokensUpdated 4 days ago
DevelopmentAuto-check: notes
RTK Rust Design Patterns
rtk-ai/rtk
Describes seven Rust design patterns for the RTK CLI filter modules, with when to use each, RTK examples, and notes on when a pattern is overkill.
83k GitHub stars~1.9k tokensUpdated yesterday
DevelopmentAuto-check passed
Release Skills
nexmoe/eve
Universal release workflow. An agent skill from nexmoe/eve.
421 GitHub starsUsed in 3 repos~3.3k tokens
DevelopmentAuto-check passed
Pnpm Engine
teambit/bit
Work on the pnpm Rust engine (@pnpm/napi, the pacquet crates) that bit install runs through.
18k GitHub stars~1.9k tokensUpdated yesterday
DevelopmentAuto-check passed

Questions about Write Code

What does Write Code do?

Rust code style and conventions for Syncpack. An agent skill from JamieMason/syncpack. Write Code is an agent skill from JamieMason/syncpack. Rust code style and conventions for Syncpack.

When should I use Write Code?

Write Code fits situations like: modifying Rust code.

How do I install Write Code in Claude Code?

Run `npx skills add JamieMason/syncpack --skill write-code -a claude-code`. Or copy the skill folder (.claude/skills/write-code in JamieMason/syncpack) into .claude/skills/write-code in your project. Claude Code loads it when a task matches its description.

How do I install Write Code in Codex?

Run `npx skills add JamieMason/syncpack --skill write-code -a codex`. Or copy the skill folder (.claude/skills/write-code in JamieMason/syncpack) into .agents/skills/write-code in your project. Codex loads it when a task matches its description.

Can I use Write Code 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 JamieMason/syncpack --skill write-code -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/write-code, .gemini/skills/write-code, .github/skills/write-code and .opencode/skills/write-code in your project.

What does Write Code need to run?

Going by SKILL.md and its folder, Write Code needs the command-line tools its instructions call (just).

Does Write Code 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 Write Code 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 Write Code use?

Write Code is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Write Code use?

About 944 tokens (SKILL.md is roughly 3.8k 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 Write Code?

Skills that share tags, products or a category with Write Code: Migrate Core Code to Submodules (tinyhumansai/openhuman, 41k stars), Rust Best Practices (farm-fe/farm, 5.6k stars), OpenLogi macOS Permissions Triage (AprilNEA/OpenLogi, 23k stars) and RTK Rust Design Patterns (rtk-ai/rtk, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Write Code?

JamieMason (a GitHub user) maintains it in JamieMason/syncpack, which has 2,099 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on September 26, 2026.

Source: JamieMason/syncpack on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Write Code

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Write Code

Style

Imports

File Organisation

Quality

Comments

Forbidden

Allowed

Default

Patterns

Iterating Instances

Error Handling

State Mutation

Files

Compare with similar skills

Similar skills

More from JamieMason/syncpack

Related

Questions about Write Code