agentleFS
saemihemmasaemihemma/lead-producer-oss/.claude/skills/team-move-team/SKILL.md

team-move-team

Skill2 starsChanged 3 months agoMITView on GitHub

Move/Sui team: smart contract correctness, off-chain integration, security, and economy soundness reviewed together. Use for contract changes affecting integration or economic flows.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not expand into off-chain architecture unless the contract boundary depends on it.

    line 52

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Move Team

Purpose

Review whether a Move/Sui feature is correct on-chain, safe to integrate off-chain, and coherent with the economy it affects.

Composition

  • role-move-sui-developer: contract correctness, invariants, transaction shape
  • role-backend-engineer: off-chain integration, service boundaries, data flow
  • role-security-engineer: exploitability, access control, attack surface
  • role-economy-designer: economic incentives, flow implications
  • Synthesis: trade-offs, acceptance

Use When

  • Reviewing Move package, contract integration, token-system change
  • Checking smart-contract changes affecting off-chain flows
  • Evaluating Sui security and economic implications together
  • Validating on-chain/off-chain responsibility boundaries

Do NOT Use When

  • Generic backend with no on-chain component
  • Pure economy analysis with no contract logic
  • Frontend or deployment review

Workflow

  1. Identify core invariants, integration points, value-moving transactions.
  2. Review on-chain correctness, off-chain handling, security, incentive shape together.
  3. Surface conflicts when safety, feasibility, economic goals disagree.
  4. Synthesize one contract-plus-integration verdict.

Default Output

MOVE TEAM REVIEW
================
On-Chain: invariant/contract findings
Integration: off-chain boundary risks, data-flow concerns
Security/Economy: exploit/access-control risks, incentive/flow risks
Recommendation: ship / revise / escalate, highest-priority fixes

Conflict Resolution

  • Move/Sui Developer owns on-chain correctness. Security Engineer can block on exploitability.
  • Economy Designer flags incentive risks but does not override contract safety.

Anti-Drift Rules

  • Invariants are non-negotiable. Do not weaken invariant protection for convenience.
  • Do not expand into off-chain architecture unless the contract boundary depends on it.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.