Javascript SDK
aiskillstore/marketplace
JavaScript/TypeScript SDK for inference.sh - run AI apps, build agents, integrate with all models.
A skill your agent uses when adding, extending, or troubleshooting EdgeStore file uploads, upload UI, or bucket access policies in a TypeScript/React application.
Install Edgestore Setup
$ npx skills add edgestorejs/edgestore --skill edgestore-setup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install edgestorejs/edgestore edgestore-setup --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/edgestorejs/edgestore.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/edgestore-setup .claude/skills/edgestore-setup && 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 "edgestore-setup" agent skill from https://github.com/edgestorejs/edgestore/tree/main/skills/edgestore-setup into .claude/skills/edgestore-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edgestore-setup", 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/edgestorejs/edgestore/tree/main/skills/edgestore-setupType 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 edgestorejs/edgestore --skill edgestore-setup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install edgestorejs/edgestore edgestore-setup --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/edgestorejs/edgestore.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/edgestore-setup .agents/skills/edgestore-setup && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "edgestore-setup" agent skill from https://github.com/edgestorejs/edgestore/tree/main/skills/edgestore-setup into .agents/skills/edgestore-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edgestore-setup", 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 edgestorejs/edgestore --skill edgestore-setup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install edgestorejs/edgestore edgestore-setup --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/edgestorejs/edgestore.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/edgestore-setup .cursor/skills/edgestore-setup && 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 "edgestore-setup" agent skill from https://github.com/edgestorejs/edgestore/tree/main/skills/edgestore-setup into .cursor/skills/edgestore-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edgestore-setup", 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/edgestorejs/edgestore.git --path skills/edgestore-setup--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 edgestorejs/edgestore --skill edgestore-setup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install edgestorejs/edgestore edgestore-setup --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/edgestorejs/edgestore.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/edgestore-setup .gemini/skills/edgestore-setup && 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 "edgestore-setup" agent skill from https://github.com/edgestorejs/edgestore/tree/main/skills/edgestore-setup into .gemini/skills/edgestore-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edgestore-setup", 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 edgestorejs/edgestore edgestore-setupInstalls 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 edgestorejs/edgestore --skill edgestore-setup -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/edgestorejs/edgestore.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/edgestore-setup .github/skills/edgestore-setup && 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 "edgestore-setup" agent skill from https://github.com/edgestorejs/edgestore/tree/main/skills/edgestore-setup into .github/skills/edgestore-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edgestore-setup", 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 edgestorejs/edgestore --skill edgestore-setup -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install edgestorejs/edgestore edgestore-setup --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/edgestorejs/edgestore.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/edgestore-setup .opencode/skills/edgestore-setup && 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 "edgestore-setup" agent skill from https://github.com/edgestorejs/edgestore/tree/main/skills/edgestore-setup into .opencode/skills/edgestore-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "edgestore-setup", 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
edgestore-setup- GitHub stars
- 454
- Token cost
- ~1.8k tokens
- SKILL.md length
- 926 words
- Files
- 3 (incl. references)
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when adding, extending, or troubleshooting EdgeStore file uploads, upload UI, or bucket access policies in a TypeScript/React application.
- Troubleshooting EdgeStore file uploads
- SKILL.md covers Establish the application and…, Choose the integration, Use MCP and the CLI and Implement and verify
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Bucket access policies in a TypeScript/React application
What it does
Edgestore Setup is an agent skill from edgestorejs/edgestore. Use when adding, extending, or troubleshooting EdgeStore file uploads, upload UI, or bucket access policies in a TypeScript/React application. Not for unrelated storage migrations or account administration.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `agents/openai.yaml` and `references/hosted-setup.md`).
It sits in Backend & APIs, covering File uploads and storage. It works with React and TypeScript. The licence is MIT.
When your agent uses it
- Troubleshooting EdgeStore file uploads
- Bucket access policies in a TypeScript/React application
Example prompts
- “/edgestore-setup”
What it can do on your machine
Read from SKILL.md and the folder at commit e84aeae. 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
Links to these hosts (documentation or services it may open):
edgestore.dev
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
Edgestore Setup loads about 1.8k tokens when it runs, and up to ~2.2k if it reads all its reference files. Until then it costs about 56 tokens; SKILL.md has 926 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
The full file from edgestorejs/edgestore at commit e84aeae, republished under its MIT licence (© edgestorejs). 926 words, ~1,792 tokens.
Download SKILL.mdSave it as
.claude/skills/edgestore-setup/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- edgestore-setup
- description
- Use when adding, extending, or troubleshooting EdgeStore file uploads, upload UI, or bucket access policies in a TypeScript/React application. Not for unrelated storage migrations or account administration.
- license
- MIT
EdgeStore setup
Implement uploads through the application's UI and server route. Verify the upload and retrieval there; if runtime access is unavailable, report what remains untested.
Establish the application and API version
Use edgestore --cwd <app> agent context --json when the CLI is available. Otherwise
inspect the selected workspace's manifests, installed EdgeStore package metadata,
existing routes/provider, and backend env-file convention. In a monorepo identify
the frontend and backend separately. Use the app's package versions, not the CLI's.
Read the relevant installed @edgestore/server, @edgestore/react, or
@edgestore/sdk agent-docs/README.md and follow its local references. These
belong to the installed package version; the skill and CLI can be newer. If the
reference is absent, use installed types/source and version-matched documentation,
and mention the fallback. Read the references again after installing packages.
For an existing 0.x integration, resolve maintenance versus migration with the user before changing APIs. Preserve installed versions unless an upgrade is authorized. For missing packages choose a compatible, explicit version. Use a prerelease only when requested or required by the application.
Choose the integration
Reuse the app's architecture, existing buckets, and configured storage provider.
Read the matching installed server reference: next.md (App or Pages Router),
tanstack-start.md, remix.md (Remix or React Router framework mode), astro.md,
hono.md, express.md, or fastify.md. Check the app's routing convention and
framework version before adapting examples. A React Router client-side app still
needs a backend. Reuse the existing backend or ask which one to add. Preserve S3,
Azure, and custom providers rather than provisioning hosted EdgeStore resources.
Infer a bucket name from the application's feature (for example avatars or
attachments); fall back to publicFiles when context is insufficient. Infer public
versus protected access from the application. Ask when the access policy is
ambiguous or the files may be sensitive. Configure the application's authorization
rules for protected files.
Before changing configuration or provisioning, summarize the proposed setup for approval: app/backend, provider, account/project to create or reuse, bucket name, who can access files, upload limits, and env destination. Proceed once approved; ask again only if the plan materially changes. Reuse an existing env file when the backend already loads it; otherwise use the framework's convention. Preserve existing env values.
Use MCP and the CLI
Prefer an available MCP for an action it supports; otherwise use the CLI.
For hosted setup, complete authentication, project linking, and credential
delivery as part of the task. When the CLI is needed but missing, install or
invoke @edgestore/cli with the application's package manager using the version
guidance above. Start with read-only discovery.
When sign-in is needed, initiate it with the available tooling, ask the user to
complete the browser step, then resume setup and verification.
Creating resources requires authorization for that setup. A project already created through MCP should be linked locally, not created again through CLI. After an uncertain mutation result, inspect for the resource before retrying or switching tools. Do not delete/empty buckets, revoke keys, enable billable overage, or change unrelated resources as an implicit setup step.
For hosted provisioning or credential delivery, read references/hosted-setup.md.
Show full SKILL.md (425 more words)Show less
Implement and verify
Configure the backend router/provider and the matching client endpoint using
installed references. Keep server keys in a loaded, gitignored backend env file,
not frontend variables (VITE_*, NEXT_PUBLIC_*).
Treat credentials as required configuration. Do not add conditional providers,
upload-enable flags, or disabled setup placeholders merely because authentication
is pending. Finish setup instead; preserve optional-storage behavior only when
the application requires it.
In split workspaces, export the real backend router type and import it with
import type on the frontend. For cross-origin calls, configure CORS for the
intended frontend origin. Wrap the upload UI with the React provider.
Implement upload UI as a reusable component, reusing the app's components or
adapting the React package's component references. For attachments, provide
drag-and-drop and file selection with a file list. For profiles or compact forms,
choose an avatar picker, file field, or upload button as appropriate.
If the installed references are absent, see the
Dropzone,
Multi-file uploader,
Avatar,
File field,
Upload button, and
Uploader provider guides.
Use the docs origin recorded in the installed references for these online guides.
Adapt the examples to the installed APIs and app styling; do not introduce a new
styling system just to use them. For custom dropzones, prefer react-dropzone
with accessible file selection, progress, and error feedback.
For uploads in unsaved forms, use temporary files when supported: upload, save
the record, then confirm. A failed database save must leave the files temporary.
Persist the upload result's ID/key and URL directly. Do not add a backend get()
just to recheck the uploaded URL or size: it can return 404 while processing is
pending. Validate input and authorize attachments in the app; fetch authoritative
metadata only when the feature needs it. Wait for processing only when processed
details are needed immediately, using the installed API's opt-in support.
For a failing integration, read the installed server's troubleshooting.md and
the React package's errors.md. Diagnose the failing app request before changing
remote resources or credentials.
Run edgestore --cwd <app> doctor --offline when available, plus the app's own
typecheck/build/tests. Investigate doctor warnings and skipped checks. Start the
app, upload a small test file through its UI and server route, and independently
retrieve and check the bytes.
For protected access, verify unauthenticated retrieval is denied and authorized
retrieval works.
Use the account and project authorized for testing. Keep credentials and signed URLs out of agent output; retrieve protected files in a local process that returns only the result. Clean up only this task's test resources. Summarize the integration choices, checks performed, blockers, and any test resources left behind.
© edgestorejs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references) in skills/edgestore-setup of edgestorejs/edgestore.
- SKILL.md
- agents/openai.yaml
- references/hosted-setup.md
Open the folder on GitHubat commit e84aeae
Compare with similar skills
Edgestore Setup 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 |
|---|---|---|---|---|---|---|
| Edgestore Setup this skilledgestorejs/edgestore | 454 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Javascript SDKaiskillstore/marketplace | 430 | 1 repos | ~3.3k | Automated safety check: Pass | None | |
| Edit PDFSimplePDF/simplepdf-embed | 407 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Implementing Drag Dropancoleman/ai-design-components | 526 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Trigger.dev Realtimepapermark/papermark | 9.2k | — | ~1.7k | Automated safety check: Pass | Custom licence | |
| React Emailviclafouch/meme-studio | 110 | 2 repos | ~3.6k | Automated safety check: Pass | MIT |
Similar skills
Edit PDF
SimplePDF/simplepdf-embed
Edit and fill PDF documents. An agent skill from SimplePDF/simplepdf-embed.
Implementing Drag Drop
ancoleman/ai-design-components
Implements drag-and-drop and sortable interfaces with React/TypeScript including kanban boards, sortable lists, file uploads, and reorderable grids.
Trigger.dev Realtime
papermark/papermark
Shows how to subscribe to Trigger.dev task runs from the backend and from React for progress indicators, live dashboards, AI response streams and approval waits.
React Email
viclafouch/meme-studio
A skill your agent uses when creating HTML email templates with React components - welcome emails, password resets, notifications, order confirmations, newsletters, or transactional emails.
Wayfinder Development
slimani-dev/muraqib
A skill your agent uses for Laravel Wayfinder which auto-generates typed functions for Laravel controllers and routes.
Related
Works with
Categories
Questions about Edgestore Setup
What does Edgestore Setup do?
A skill your agent uses when adding, extending, or troubleshooting EdgeStore file uploads, upload UI, or bucket access policies in a TypeScript/React application. Edgestore Setup is an agent skill from edgestorejs/edgestore. Use when adding, extending, or troubleshooting EdgeStore file uploads, upload UI, or bucket access policies in a TypeScript/React application.
When should I use Edgestore Setup?
Edgestore Setup fits situations like: troubleshooting EdgeStore file uploads; bucket access policies in a TypeScript/React application.
How do I install Edgestore Setup in Claude Code?
Run `npx skills add edgestorejs/edgestore --skill edgestore-setup -a claude-code`. Or copy the skill folder (skills/edgestore-setup in edgestorejs/edgestore) into .claude/skills/edgestore-setup in your project. Claude Code loads it when a task matches its description.
How do I install Edgestore Setup in Codex?
Run `npx skills add edgestorejs/edgestore --skill edgestore-setup -a codex`. Or copy the skill folder (skills/edgestore-setup in edgestorejs/edgestore) into .agents/skills/edgestore-setup in your project. Codex loads it when a task matches its description.
Can I use Edgestore Setup 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 edgestorejs/edgestore --skill edgestore-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/edgestore-setup, .gemini/skills/edgestore-setup, .github/skills/edgestore-setup and .opencode/skills/edgestore-setup in your project.
What does Edgestore Setup need to run?
SKILL.md names no scripts, command-line tools or credentials: Edgestore Setup is instructions for the agent only.
Does Edgestore Setup access the network?
SKILL.md names 1 domain. As links in the text: edgestore.dev. This is read from the text; nothing was executed.
Is Edgestore Setup 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 Edgestore Setup use?
Edgestore Setup is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Edgestore Setup use?
About 1.8k tokens (SKILL.md is roughly 7.2k 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 437 tokens, read only when the agent opens those files.
What are the alternatives to Edgestore Setup?
Skills that share tags, products or a category with Edgestore Setup: Javascript SDK (aiskillstore/marketplace, 430 stars), Edit PDF (SimplePDF/simplepdf-embed, 407 stars), Implementing Drag Drop (ancoleman/ai-design-components, 526 stars) and Trigger.dev Realtime (papermark/papermark, 9.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Edgestore Setup?
edgestorejs (a GitHub organization) maintains it in edgestorejs/edgestore, which has 454 GitHub stars. The repository was last updated on October 6, 2026.
Source: edgestorejs/edgestore on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.