Agent skill

Freighter Best Practices

Comprehensive best practices for the Freighter browser extension.

Apache-2.0Auto-check passedDevelopment

Install Freighter Best Practices

skills CLI

$ npx skills add stellar/freighter --skill freighter-best-practices -a claude-code

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

GitHub CLI

$ gh skill install stellar/freighter freighter-best-practices --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/stellar/freighter.git skills-src && mkdir -p .claude/skills && cp -r skills-src/docs/skills/freighter-best-practices .claude/skills/freighter-best-practices && 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 "freighter-best-practices" agent skill from https://github.com/stellar/freighter/tree/master/docs/skills/freighter-best-practices into .claude/skills/freighter-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "freighter-best-practices", 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/stellar/freighter/tree/master/docs/skills/freighter-best-practices

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 stellar/freighter --skill freighter-best-practices -a codex

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

GitHub CLI

$ gh skill install stellar/freighter freighter-best-practices --agent codex

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

Manual copy

$ git clone --depth 1 https://github.com/stellar/freighter.git skills-src && mkdir -p .agents/skills && cp -r skills-src/docs/skills/freighter-best-practices .agents/skills/freighter-best-practices && 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 "freighter-best-practices" agent skill from https://github.com/stellar/freighter/tree/master/docs/skills/freighter-best-practices into .agents/skills/freighter-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "freighter-best-practices", 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 stellar/freighter --skill freighter-best-practices -a cursor

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

GitHub CLI

$ gh skill install stellar/freighter freighter-best-practices --agent cursor

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

Manual copy

$ git clone --depth 1 https://github.com/stellar/freighter.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/docs/skills/freighter-best-practices .cursor/skills/freighter-best-practices && 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 "freighter-best-practices" agent skill from https://github.com/stellar/freighter/tree/master/docs/skills/freighter-best-practices into .cursor/skills/freighter-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "freighter-best-practices", 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/stellar/freighter.git --path docs/skills/freighter-best-practices

--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 stellar/freighter --skill freighter-best-practices -a gemini-cli

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

GitHub CLI

$ gh skill install stellar/freighter freighter-best-practices --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/stellar/freighter.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/docs/skills/freighter-best-practices .gemini/skills/freighter-best-practices && 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 "freighter-best-practices" agent skill from https://github.com/stellar/freighter/tree/master/docs/skills/freighter-best-practices into .gemini/skills/freighter-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "freighter-best-practices", 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 stellar/freighter freighter-best-practices

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 stellar/freighter --skill freighter-best-practices -a github-copilot

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

Manual copy

$ git clone --depth 1 https://github.com/stellar/freighter.git skills-src && mkdir -p .github/skills && cp -r skills-src/docs/skills/freighter-best-practices .github/skills/freighter-best-practices && 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 "freighter-best-practices" agent skill from https://github.com/stellar/freighter/tree/master/docs/skills/freighter-best-practices into .github/skills/freighter-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "freighter-best-practices", 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 stellar/freighter --skill freighter-best-practices -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 stellar/freighter freighter-best-practices --agent opencode

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

Manual copy

$ git clone --depth 1 https://github.com/stellar/freighter.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/docs/skills/freighter-best-practices .opencode/skills/freighter-best-practices && 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 "freighter-best-practices" agent skill from https://github.com/stellar/freighter/tree/master/docs/skills/freighter-best-practices into .opencode/skills/freighter-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "freighter-best-practices", 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: freighter-best-practices
GitHub stars: 118
Token cost: ~706 tokens
SKILL.md length: 174 words
Files: 12 (incl. references)
Skills in repo: 1
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Comprehensive best practices for the Freighter browser extension.

Works in 4 steps: extension/ -- the browser extension… → @stellar/freighter-api/ -- the npm SDK… → @shared/ -- shared packages (api,… → …
Writing new features
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
Adding message handlers

What it does

Freighter Best Practices is an agent skill from stellar/freighter. Comprehensive best practices for the Freighter browser extension. Covers code style, architecture, security, testing, performance, error handling, i18n, messaging, git workflow, dependencies, and anti-patterns. Use when writing new features, reviewing PRs, adding message handlers, working with Redux, modifying content scripts, handling keys, building transactions, or any development work in the freighter extension repo. Triggers on any task touching the freighter codebase.

Its SKILL.md is about 710 tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including reference files (for example `references/anti-patterns.md`, `references/architecture.md` and `references/code-style.md`).

It sits in Development, covering Browser extensions, Internationalization and Git workflow. It works with Chrome Extensions and Redux. The repository describes itself as: Stellar browser extension. The licence is Apache-2.0.

When your agent uses it

Writing new features
Adding message handlers
Working with Redux
Modifying content scripts

Example prompts

“/freighter-best-practices”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

extension/ -- the browser extension itself (popup, background service
@stellar/freighter-api/ -- the npm SDK that dApps use to interact with
@shared/ -- shared packages (api, constants, helpers) consumed by
docs/ -- documentation and skills

What it can do on your machine

Read from SKILL.md and the folder at commit a701189. 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.
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

Freighter Best Practices loads about 706 tokens when it runs, and up to ~16k if it reads all its reference files. Until then it costs about 126 tokens; SKILL.md has 174 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~126
When it runs · the whole SKILL.md, loaded when a task matches: ~706
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~16k

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 stellar/freighter at commit a701189, republished under its Apache-2.0 licence (© stellar). 174 words, ~706 tokens.

Download SKILL.mdSave it as .claude/skills/freighter-best-practices/SKILL.md (or your agent's skills folder). This skill also uses 11 other files; get the full folder from GitHub.

name: freighter-best-practices
description: Comprehensive best practices for the Freighter browser extension. Covers code style, architecture, security, testing, performance, error handling, i18n, messaging, git workflow, dependencies, and anti-patterns. Use when writing new features, reviewing PRs, adding message handlers, working with Redux, modifying content scripts, handling keys, building transactions, or any development work in the freighter extension repo. Triggers on any task touching the freighter codebase.

Freighter Best Practices

Freighter is a non-custodial Stellar wallet shipped as a browser extension (Manifest V3) for Chrome and Firefox. The repository is a Yarn workspaces monorepo with four main workspaces:

extension/ -- the browser extension itself (popup, background service worker, content scripts)
@stellar/freighter-api/ -- the npm SDK that dApps use to interact with Freighter
@shared/ -- shared packages (api, constants, helpers) consumed by multiple workspaces
docs/ -- documentation and skills

Reference Guide

Concern	File	When to Read
Code Style	references/code-style.md	Writing or reviewing any code
Architecture	references/architecture.md	Adding features, understanding the codebase
Security	references/security.md	Touching keys, messages, storage, or dApp interactions
Testing	references/testing.md	Writing or fixing tests
Performance	references/performance.md	Optimizing renders, bundle size, or load times
Error Handling	references/error-handling.md	Adding error states, catch blocks, or user-facing errors
Internationalization	references/i18n.md	Adding or modifying user-facing strings
Messaging	references/messaging.md	Adding popup<>background<>content script communication
Git & PR Workflow	references/git-workflow.md	Branching, committing, opening PRs, CI
Dependencies	references/dependencies.md	Adding, updating, or auditing packages
Anti-Patterns	references/anti-patterns.md	Code review, avoiding common mistakes
Troubleshooting	../../docs/troubleshooting-guide.md	Build failures, setup issues, known bugs and gotchas

Files

SKILL.md and 11 other files (references) in docs/skills/freighter-best-practices of stellar/freighter.

SKILL.md
references/anti-patterns.md
references/architecture.md
references/code-style.md
references/dependencies.md
references/error-handling.md
references/git-workflow.md
references/i18n.md
references/messaging.md
references/performance.md
references/security.md
references/testing.md

Open the folder on GitHubat commit a701189

Compare with similar skills

Freighter Best Practices 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.

Freighter Best Practices compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Freighter Best Practices this skillstellar/freighter	118	—	~706	Automated safety check: Pass	Apache-2.0	today
Repomix Browser Extension Developeryamadashy/repomix	29k	1 repos	~288	Automated safety check: Pass	MIT	5 days ago
Workflows Management Jest Testingelastic/kibana	21k	—	~1.3k	Automated safety check: Pass	Custom licence	today
Develop ExtensionPostHog/posthog-js	628	—	~2.3k	Automated safety check: Pass	Custom licence	today
Claude Designkwakseongjae/oh-my-design	531	—	~4.8k	Automated safety check: Pass	MIT	8 days ago
JavaScript IO Effects With Sagasparalleldrive/aidd	384	—	~587	Automated safety check: Pass	MIT	3 mo ago

Similar skills

Repomix Browser Extension Developer
yamadashy/repomix
Use this skill when developing or maintaining browser extension code in the `browser/` directory, including Chrome/Firefox/Edge compatibility, content…
29k GitHub starsUsed in 1 repo~288 tokens
DevelopmentAuto-check passed
Workflows Management Jest Testing
elastic/kibana
Official
Use the shared TestProvider in workflowsmanagement Jest tests instead of hand-wiring KibanaContextProvider, QueryClientProvider, WorkflowsContextProvider, MemoryRouter, I18nProvider, and the Redux…
21k GitHub stars~1.3k tokensUpdated today
Testing & QAAuto-check passed
Develop Extension
PostHog/posthog-js
Official
Author a new PostHog browser extension, or port a posthog-js v1 extension, against the @posthog/browser-common Client/Extension contract.
628 GitHub stars~2.3k tokensUpdated today
DevelopmentAuto-check passed
Claude Design
kwakseongjae/oh-my-design
현재 코드베이스(또는 폴더)를 분석해 "디자인 컨텍스트 브리프"(스택/디자인 토큰/컴포넌트/ 라우트/실제 UI 카피/큐레이션된 에셋/레포 링크)를 합성하고, 그걸 Claude Design (claude.ai/design)에 자동으로 전달해 디자인을 생성한 뒤 결과 링크를 터미널에 클릭 가능한 형태로 돌려주는 스킬.
531 GitHub stars~4.8k tokensUpdated 8 days ago
DevelopmentAuto-check passed
JavaScript IO Effects With Sagas
paralleldrive/aidd
Teaches the saga pattern with call and put so network requests and side effects stay out of the logic and sagas can be tested without mocks.
384 GitHub stars~587 tokensUpdated 3 mo ago
DevelopmentAuto-check passed
Wxt Browser Extensions
vantezzen/skip-silence
WXT browser extension performance optimization guidelines. An agent skill from vantezzen/skip-silence.
469 GitHub starsUsed in 2 repos~1.9k tokens
DevelopmentAuto-check passed

Works with

Questions about Freighter Best Practices

What does Freighter Best Practices do?

Comprehensive best practices for the Freighter browser extension. Freighter Best Practices is an agent skill from stellar/freighter. Comprehensive best practices for the Freighter browser extension.

When should I use Freighter Best Practices?

Freighter Best Practices fits situations like: writing new features; adding message handlers; working with Redux; modifying content scripts.

How do I install Freighter Best Practices in Claude Code?

Run `npx skills add stellar/freighter --skill freighter-best-practices -a claude-code`. Or copy the skill folder (docs/skills/freighter-best-practices in stellar/freighter) into .claude/skills/freighter-best-practices in your project. Claude Code loads it when a task matches its description.

How do I install Freighter Best Practices in Codex?

Run `npx skills add stellar/freighter --skill freighter-best-practices -a codex`. Or copy the skill folder (docs/skills/freighter-best-practices in stellar/freighter) into .agents/skills/freighter-best-practices in your project. Codex loads it when a task matches its description.

Can I use Freighter Best Practices 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 stellar/freighter --skill freighter-best-practices -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/freighter-best-practices, .gemini/skills/freighter-best-practices, .github/skills/freighter-best-practices and .opencode/skills/freighter-best-practices in your project.

What does Freighter Best Practices need to run?

SKILL.md names no scripts, command-line tools or credentials: Freighter Best Practices is instructions for the agent only.

Does Freighter Best Practices 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 Freighter Best Practices 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 Freighter Best Practices use?

Freighter Best Practices 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.

How many tokens does Freighter Best Practices use?

About 706 tokens (SKILL.md is roughly 2.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 15k tokens, read only when the agent opens those files.

What are the alternatives to Freighter Best Practices?

Skills that share tags, products or a category with Freighter Best Practices: Repomix Browser Extension Developer (yamadashy/repomix, 29k stars), Workflows Management Jest Testing (elastic/kibana, 21k stars), Develop Extension (PostHog/posthog-js, 628 stars) and Claude Design (kwakseongjae/oh-my-design, 531 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Freighter Best Practices?

stellar (a GitHub organization) maintains it in stellar/freighter, which has 118 GitHub stars. The repository was last updated on October 8, 2026.

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

Install Freighter Best Practices

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Freighter Best Practices

Reference Guide

Files

Compare with similar skills

Similar skills

Repomix Browser Extension Developer

Workflows Management Jest Testing

Develop Extension

Claude Design

JavaScript IO Effects With Sagas

Wxt Browser Extensions

Related

Questions about Freighter Best Practices