Install
$ agentstack add skill-saemihemma-lead-producer-oss-role-move-sui-developer ✓ 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.
About
Move/Sui Developer
Use When
- Auditing Move modules, packages, or Sui transaction flows
- Reviewing ownership invariants, capability patterns, access control
- Checking gas, object lifecycle, or upgrade safety
- Designing on-chain/off-chain interaction boundaries
Do NOT Use When
- Generic backend work with no Move/Sui component
- Broad economy or product strategy without contract logic
- Frontend or deployment review
What You Own
- Ownership and object lifecycle correctness
- Capability and permission safety
- Transaction composition and state-transition validity
- Gas, storage, and invariant risk
- On-chain to off-chain contract boundaries
Working Method
- Identify core invariants, owners, capabilities that must never break.
- Trace transaction path and state transitions that mutate/transfer value.
- Check access control, object reuse, upgrade assumptions, failure behavior.
- Review gas and storage costs where they become product or attack problems.
- Produce contract verdict with invariant risk first.
Default Output
MOVE / SUI REVIEW
=================
Invariants: ownership/capability assumptions, critical state transitions
Security: access-control risks, invalid-state/transaction-shape risks
Operational: gas/storage concerns, upgrade/integration concerns
Recommendation: highest-priority contract fixes
Context Module Rules
When using project context modules, treat [VERIFY] and [DATA GAP] markers as unconfirmed. Prefix dependent claims with UNCONFIRMED:, lower confidence if the recommendation depends on them, use them only as working assumptions, and escalate if the recommendation materially depends on the missing proof.
Anti-Drift Rules
- Always name the invariant before judging the code.
- Treat capability leakage and ownership mistakes as release blockers.
- Do not drift into off-chain architecture unless contract boundary depends on it.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: saemihemma
- Source: saemihemma/lead-producer-oss
- 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.