Seed skill
Turn source material into a usable packet.
Capability guide
MiroFish skill means the capabilities behind a scenario run.
Searchers often use skill to mean capability. This page maps the phrase to the real MiroFish workflow: source grounding, graph construction, agents, simulation, reports, and follow-up review.
Short answer for mirofish skill
Use this page to route the search phrase to a real MiroFish action without creating a misleading product claim.
Graph skill
Keep entities, claims, relationships, and assumptions visible.
Agent skill
Create role-based perspectives that can disagree.
Report skill
Summarize branches, weak assumptions, and next checks.
Capability map
A useful MiroFish run is not one magic skill. It is a chain of smaller capabilities that must stay reviewable. If one step is weak, the report becomes harder to trust.
How to evaluate it
Read the output by asking whether the source packet was clear, the graph stayed inspectable, the personas covered the right actors, and the report produced a concrete next check.
How to use this mirofish skill page
A search result is useful only when it leaves the visitor with a safe next action and a clear reason for that action.
mirofish skill intent
A mirofish skill search usually comes from someone who already recognizes the MiroFish name but does not yet know which official route answers the question. The right response is a narrow guide, not a broad marketing page. This page keeps the phrase mirofish skill tied to the real MiroFish workflow, the official domain, the source links that can be checked, and the next internal page that should carry the visitor forward.
Before opening a workspace, read the short answer, compare the listed facts, and decide whether your task is discovery, account access, source review, plan selection, safety checking, or scenario research. That small classification prevents a searcher from treating one MiroFish page as proof of a claim that belongs somewhere else.
What to verify before acting
Use the visible facts on this page as a checklist rather than as decorative copy. For mirofish skill, the current decision points are seed skill, graph skill, agent skill, report skill. The underlying details are intentionally concrete: Seed skill: Turn source material into a usable packet. Graph skill: Keep entities, claims, relationships, and assumptions visible. Agent skill: Create role-based perspectives that can disagree. Report skill: Summarize branches, weak assumptions, and next checks. If any of those details becomes important to your decision, follow the linked official page or source reference and verify the current version before sharing, installing, paying, citing, or uploading sensitive material.
This matters because brand searches often mix official pages, old snippets, unrelated domains, and recycled descriptions. MiroFish pages should keep the reader close to verifiable routes: the homepage for product identity, the console for real work, pricing for capacity, resources for learning, and GitHub for source or release checks.
Useful first step
The safest first step after a mirofish skill query is to write down what you are trying to decide in one sentence. Then choose the page section that matches that decision. If the task is capability map and how to evaluate it, continue to the relevant internal guide before using the console. If the task depends on source code, releases, setup, downloads, or self-hosting, use the external repository link and release link on this page before trusting a third-party summary.
For scenario work, prepare a short source packet, one question, one time horizon, and one assumption you may want to change later. For account, cost, app, regional, language, or package searches, make the verification step first and the simulation step second. That order keeps the result practical and reduces the chance of treating a brand keyword as a product promise.
mirofish skill checklist
Use this checklist when comparing search snippets, official pages, source links, and your next MiroFish action.
Confirm the official route
Stay on mirofish.work for product pages and account or console routes. If a page uses the MiroFish name but does not connect back to the official site, repository, resources, or pricing path, treat it as unverified until proven otherwise.
Match the page to the job
Do not use a mirofish skill page for every MiroFish task. Use it for this exact search intent, then move to the internal guide that handles the real work: pricing, login, chat, creator planning, capabilities, regional checks, package safety, or BTC scenario research.
Keep limits visible
MiroFish reports are scenario analysis, not certainty. Higher capacity, a cleaner login path, a source link, or a safer app route can improve workflow quality, but source quality, review, and follow-up checks still decide whether the output is useful.
Record the next check
After reading the page, choose one follow-up action: open the official console, compare plans, inspect GitHub releases, read the tutorial, or prepare source material. A good mirofish skill search ends with a concrete next check, not another vague search loop.
Handoff note for mirofish skill
When you share this page with a teammate, summarize the handoff in plain language: "I checked the official mirofish skill route, the page points back to mirofish.work, and the next action is to use the linked MiroFish guide or source reference." That note is short, but it prevents the common mistake of sending someone from a brand search into a random download page, stale profile, or broad AI description that does not answer the actual task.
When not to continue
Pause before continuing if the page you found asks for account details on another domain, promises certainty, presents an unofficial install package, hides the source of a price or product claim, or turns a scenario report into advice. A careful mirofish skill workflow should keep official links, source links, limits, and the reader's next check visible all the way through.
Official and source links
If you need implementation details, inspect the open-source project and then use the tutorial for the practical user path.
Official homepage
Canonical MiroFish product entry, pricing, resources, and console route.
Open homeMiroFish tutorial
Step-by-step guide for preparing seed material, running scenarios, and reading reports.
Open tutorialExternal source references
Use these when the page mentions source code, releases, setup, or installation decisions.
Open-source repository GitHub releasesContinue from here
These internal links keep the searcher on the official product path.
Resources
Best next step for a mirofish skill search after this page answers the basic intent.
Continue hereGraph construction
Inspect how entities, claims, assumptions, and relationships become reviewable graph context.
Read guideAgent personas
Read how role-based perspectives are created, constrained, and checked for disagreement.
Read guideSimulation report
Read how MiroFish turns simulation rounds into a structured report and next checks.
Read guideMiroFish Skill and Capability Guide FAQ
Fast answers before opening a workspace, reading source, or choosing a plan.
Does MiroFish have one skill?
No. The value is a workflow of source, graph, persona, simulation, report, and follow-up capabilities.
Which guide should I read first?
Start with resources, then graph construction, agent personas, and simulation report.
Is this a Codex skill?
No. This page explains MiroFish product capabilities, not a Codex skill package.