Mina ecosystem research scout

Skill mysteryon88/skills/mina-protocol/skills/mina-ecosystem-research-scout

My Web3 skills & experiments

Install

npx -y skills add mysteryon88/skills --skill mina-ecosystem-research-scout

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when finding or evaluating current Mina and o1js resources, examples, grants, audit reports, repositories, issues, tooling, standards, or ecosystem projects.

SKILL.md

2.7 KB, as published. Nobody here has run it

Mina Ecosystem Research Scout Skill

Use when

Use this skill when the user asks to find or evaluate current Mina/o1js resources, examples, grants, audit reports, repositories, issues, tooling, standards or ecosystem projects.

Always use current web search for this skill unless the user explicitly says not to browse.

Shared references

If installed from the full package, shared resources live in ../mina-protocol-agent/references/. Load ../mina-protocol-agent/references/INDEX.md only when task cards, examples, templates, source links or deeper checklists are needed.

Research priority

Prefer primary sources:

Official Mina docs.
Current o1Labs docs.
o1-labs/o1js repo.
o1-labs/zkapp-cli repo.
Mina Foundation repos and project lists.
Published audit reports.
Maintained project repos with recent commits.

Then use secondary sources:

community tutorials;
blog posts;
course materials;
Discord/Telegram content only if user provides it;
AI agent wrappers and existing skill packs.

Evaluation criteria

For every resource, assess:

Official or community:
Last updated:
Targets SnarkyJS or current o1js:
Uses current API:
Has tests:
Has security notes:
Has deployment instructions:
Production/audited/demo:
Best use case:
Risk/caveat:

Search queries to use

Use combinations like:

site:docs.minaprotocol.com Mina o1js <topic>
site:docs.o1labs.org/o1js <topic>
site:github.com/o1-labs/o1js <topic>
site:github.com Mina o1js SmartContract <topic>
Mina o1js audit report <project>
Mina zkApp <topic> repository

For old examples, search both SnarkyJS and o1js, then explain whether migration is needed.

Red flags

old SnarkyJS examples presented as current o1js;
no tests;
no permission discussion;
no state preconditions;
no negative tests;
private keys in frontend examples;
deprecated APIs;
token examples without supply invariants;
privacy claims without leakage map;
examples that rely on a trusted backend but market themselves as trustless.

Output format

Return a ranked table:

Rank | Resource | Type | Link | Usefulness | Current? | Risk/Caveat | Best use

Then give a practical recommendation:

Start here:
Use this for coding:
Use this for security:
Avoid or treat as legacy:
Missing resource I would create:

Special instruction for learning support

When the user is learning Mina, do not dump 30 links. Give 3 to 7 resources, in order, with one sentence on how to use each.