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

Sanity Dual Studio

skill-aiengkenn-agent-skills-sanity-dual-studio · by AIEngKenn

>-

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

Install

$ agentstack add skill-aiengkenn-agent-skills-sanity-dual-studio

✓ 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-aiengkenn-agent-skills-sanity-dual-studio)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
2mo 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 Sanity Dual Studio? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Sanity Dual Studio Config

Many repos have two entrypoints:

| Entry | Config file | Used by | |-------|-------------|---------| | Embedded | root sanity.config.ts | Next /studio | | Standalone | sanity/sanity.config.ts | sanity dev historically |

They must stay aligned — same desk, schema, locale, badges.

Symptoms this skill fixes

  • /studio has default desk; studio:dev has custom structure
  • TS: StructureResolver from sanity/node_modules ≠ root node_modules
  • Locale plugin works in one entry only

Recommended end state

  1. One Sanity install at repo root
  2. Root sanity.config.ts is canonical
  3. npm run studio:devsanity dev from root (not cd sanity && npm run dev)
  4. sanity/schemas (or src/sanity) shared by import
  5. Nested sanity/package.json uses peerDependencies / echo scripts — do not reinstall full sanity under sanity/node_modules
  6. Root sanity.cli.ts for CLI projectId/dataset

tsconfig tips

Force resolution to root if needed:

"paths": {
  "sanity": ["./node_modules/sanity"],
  "sanity/*": ["./node_modules/sanity/*"]
}

Exclude sanity/node_modules, starter examples.

Anti-patterns

  • Two divergent desk structures
  • npm install inside sanity/ recreating nested copies
  • Different projectIds between configs

Deliverable

Canonical config path · scripts updated · dual-desk eliminated · tsc clean for studio files.

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.