Javascript Game Tools
Use when building JavaScript or TypeScript tooling around a game project, including Firebase web apps, admin dashboards, build tools, data editors, content pipelines, Node scripts, Cloud Functions, React/Vite/Next frontends, package setup, linting, tests, and browser tooling.
Install
$ agentstack add skill-furkantokkan-agent-foundry-javascript-game-tools ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ● Environment & secrets Used
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-furkantokkan-agent-foundry-javascript-game-tools) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
JavaScript Game Tools
Use this skill for web tooling, dashboards, Firebase web clients, Node scripts, Cloud Functions, editor utilities, and TypeScript refactors around the game.
First Read
Inspect:
package.json- lockfile (
package-lock.json,pnpm-lock.yaml,yarn.lock, orbun.lockb) tsconfig.jsonvite.config.*,next.config.*, or other build configsrc/functions/if Firebase Functions are involved.env.exampleand config docs, but never print secrets
Core Rules
- Prefer TypeScript for production tooling.
- Use the existing package manager and module style.
- Use Firebase modular Web SDK in browser code.
- Use Firebase Admin SDK only in trusted server code.
- For Firebase Functions game APIs in this workspace, prefer JavaScript Gen2
Functions with Express.js route registration unless the target project already uses another explicit pattern.
- Keep environment-specific config outside source.
- Validate input at boundaries with the project's existing schema library if
present; otherwise choose a small, explicit validator only when needed.
- Do not introduce a framework or state library for a small script.
- Add tests for data transforms, rules-sensitive code, and Cloud Functions.
Workflow
- Identify whether the target is browser, Node, Cloud Functions, or static tooling.
- Read existing scripts and package conventions.
- Make the smallest compatible change.
- Run available checks: typecheck, lint, unit tests, build.
- If checks cannot run, explain the missing dependency or command.
Reference Loading
- JavaScript/TypeScript patterns:
references/javascript-patterns.md - Firebase web/client boundaries: use
firebase-game-backend
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: furkantokkan
- Source: furkantokkan/agent-foundry
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.