AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Datastore Review

skill-codephobiia-claude-roblox-game-studio-datastore-review · by CodePhobiia

Audit all DataStore usage in the project for correctness, security, and best practices. Checks for session locking, pcall usage, schema versioning, budget management, and common anti-patterns.

No reviews yet
0 installs
35 views
0.0% view→install

Install

$ agentstack add skill-codephobiia-claude-roblox-game-studio-datastore-review

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

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

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-codephobiia-claude-roblox-game-studio-datastore-review)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
5mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

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 →
Are you the author of Datastore Review? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

/datastore-review — DataStore Audit

Delegate to: datastore-architect

Steps:

  1. Search for all DataStore usage: grep -rn "DataStoreService" src/
  2. Search for all MemoryStore usage: grep -rn "MemoryStoreService" src/
  3. Search for all BindToClose handlers: grep -rn "BindToClose" src/
  4. 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.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.