Install
$ agentstack add skill-codephobiia-claude-roblox-game-studio-datastore-review ✓ 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 No
- ✓ 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.
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
/datastore-review — DataStore Audit
Delegate to: datastore-architect
Steps:
- Search for all DataStore usage:
grep -rn "DataStoreService" src/ - Search for all MemoryStore usage:
grep -rn "MemoryStoreService" src/ - Search for all BindToClose handlers:
grep -rn "BindToClose" src/ - Search for PlayerAdded / PlayerRemoving:
grep -rn "PlayerAdded\|PlayerRemoving" src/
Check each DataStore operation for:
Critical (must fix):
- [ ] All GetAsync/SetAsync/UpdateAsync wrapped in pcall
- [ ] Session locking implemented (acquire lock on join, release on leave)
- [ ] BindToClose handler saves all player data with timeout
- [ ] Player data keyed by UserId (not Name)
- [ ] Schema includes version number
- [ ] No synchronous DataStore calls in PlayerAdded without yielding protection
Important (should fix):
- [ ] Auto-save interval implemented (recommended: every 5 minutes)
- [ ] Save debouncing with dirty flag
- [ ] Retry logic for failed operations (with exponential backoff)
- [ ] Data migration functions for schema version upgrades
- [ ] OrderedDataStore used appropriately (leaderboards, rankings)
- [ ] Budget monitoring (not exceeding request limits)
Nice to have:
- [ ] Data backup system (periodic full save to backup key)
- [ ] Analytics on save failures
- [ ] Admin tools for data inspection/correction
Output:
Generate a report with findings organized by severity:
# DataStore Review
## Scope
Files analyzed: X
DataStore references found: Y
MemoryStore references found: Z
## Critical Findings
1. **[filepath:line]**: [issue]
- Impact: [data loss / duplication / exploit]
- Fix: [specific code change]
## Important Findings
...
## Anti-Patterns Detected
...
## Recommended Architecture
[If no DataStore code exists yet, suggest the recommended architecture pattern:]
- ServerStorage/PlayerData/PlayerDataService.lua (main API)
- ServerStorage/PlayerData/SessionLock.lua (lock mechanism)
- ServerStorage/PlayerData/Schema.lua (current schema + migrations)
- ServerStorage/PlayerData/Serializer.lua (compress/decompress)
If no DataStore code exists yet, suggest the recommended architecture pattern and offer to scaffold it via datastore-architect.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: CodePhobiia
- Source: CodePhobiia/claude-roblox-game-studio
- 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.