825 skills · sorted by relevance
Explore development ideas and problems through conversation, code investigation, diagrams, and comparisons. The skill helps clarify requirements, weigh approaches, and surface risks before or during a change, with optional documentation of decisions when requested.
Add a blockchain explorer transaction to the TRES Finance ledger. Use when the user provides a blockchain explorer URL (Etherscan, Polygonscan, Arbiscan, Basescan, Snowtrace, BscScan, etc.) or a raw transaction hash and wants to record it in the platform ledger. Trigger phrases include "add this transaction", "import tx from etherscan", "record this on-chain tx", "add to ledger".
The English summary is being prepared. Showing the original description.
Expert knowledge for Azure Data Explorer development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when securing ADX (RBAC/MI), automating cluster/schema deploys, tuning ingestion/queries, or integrating via ODBC/JDBC/Power BI, and other Azure Data Explorer related development tasks. Not for Azure Synapse Analytics (use azure-synapse-analytics), Azure HDInsight (use azure-hdinsight), Azure Databricks (use azure-databricks), Azure Stream Analytics (use azure-stream-analytics).
The English summary is being prepared. Showing the original description.
Scaffolds a structured investigation in scratch/ for empirical research and documentation. Use when the user says "start an investigation" or wants to: trace code paths or data flow ("trace from X to Y", "what touches X", "follow the wiring"), document system architecture comprehensively ("document how the system works", "archeology"), investigate bugs ("figure out why X happens"), explore technical feasibility ("can we do X?"), or explore design options ("explore the API", "gather context", "design alternatives"). Creates dated folder with README. NOT for simple code questions or single-file searches.
The English summary is being prepared. Showing the original description.
Deep web research skill using parallel subagents + chromux browser-explorer + Gemini. Spawns multiple WebSearch research agents AND browser-explorer agents (via chromux for JS-heavy/dynamic sites), plus a Gemini CLI deep research source, then synthesizes everything into a cited report. Uses WebSearch, WebFetch, chromux browser-explorer, and Gemini CLI. Invoke with /deep-research <topic>.
The English summary is being prepared. Showing the original description.
Explore a feature or CLI, reproduce defects and record bounded findings. Use for "explore X", "find issues with X", or the exploration stage of feature- pipeline; standalone runs return findings without automatically expanding scope.
The English summary is being prepared. Showing the original description.
Scaffolds a structured investigation in scratch/ for empirical research and documentation. Use when the user says "start an investigation" or wants to: trace code paths or data flow ("trace from X to Y", "what touches X", "follow the wiring"), document system architecture comprehensively ("document how the system works", "archeology"), investigate bugs ("figure out why X happens"), explore technical feasibility ("can we do X?"), or explore design options ("explore the API", "gather context", "design alternatives"). Creates dated folder with README. NOT for simple code questions or single-file searches.
The English summary is being prepared. Showing the original description.
Ideate a brand-new game concept with the user, from a blank page or a one-line hint to a finished CONCEPT card. Use it whenever the user wants to come up with a new game — whether the project has no design document yet, or already has one and they're exploring a fresh idea. Through a structured divergence/convergence dialogue it explores ideas, frames the hook, generates and scores concepts (market validation delegated to /unikit-gd-explore), and settles pillars, loops, motivation, and a pre-mortem. Trigger whenever the user wants to make or invent a game, doesn't know where to start, or gives a genre/theme hint, e.g. "let's come up with a game", "I don't know what game to make", "I want to make a roguelike", "a game about zombies", "a farming game", "help me come up with a concept". For researching or dissecting existing games use /unikit-gd-explore; to write an already-chosen concept as the master GDD use /unikit-gd-spec.
The English summary is being prepared. Showing the original description.
Mandatory 3-phase explore-reason-act workflow before code modification. Enforces read-before-write, root cause hypothesis formulation, minimal change application. Triggered by "explore" ("탐색"), "reason" ("추론"), "read before write", "root cause" ("근본 원인") keywords.
The English summary is being prepared. Showing the original description.
Manages your own skill landscape: surveys and compares existing skills (Audit mode), researches the web for new skills/plugins (Explore mode), and is at the same time the installer that generates lean subskills (Skill-Finder, family umbrella, maintenance skills) instead of loading a monolith. Use this skill for "compare/audit skills", "which skills are duplicated", "form skill families", "clean up/consolidate skills", "maintain the skill register", "find skills/plugins for topic X", "install new skills", "browse the skill marketplace", or for `/skill-explorer`. Delivers a sub-report per family and a globally numbered decision list; installs/uninstalls only after a security check and explicit approval.
The English summary is being prepared. Showing the original description.
Review a codebase for structural problems that make understanding and testing difficult. Compare refactoring candidates in an HTML report with before-and-after diagrams, then explore the chosen option through questions about constraints, design, and tests.
Build a disposable prototype to answer a design question. Explore logic and changing states through a shareable HTML demo, or compare distinct interface variations, then record the findings and carry validated decisions into real code.
Explore a writing topic through probing questions and collect promising sentences, anecdotes, metaphors, and unfinished thoughts. It saves these fragments in a single Markdown file, giving you raw material to develop before deciding on an outline.
Design and generate simple, cute mascot images for products, brands, or communities, aiming for recognition at 32 × 32 pixels. Explore distinct concepts and color choices through separately generated square candidates with labeled design details.
Search arXiv papers by topic, author, category, or ID, then inspect abstracts and full texts or create citation entries. Use Semantic Scholar alongside arXiv to explore related research, references, and citation counts.
Explore a web app in the browser to find functional, visual, and usability issues. The skill organizes screenshots, console errors, and reproduction steps into a Markdown bug report, with findings grouped by severity and category.
Generate several AI design options, view them on a comparison board, and collect organized feedback. Use the results to explore visual directions and refine designs when a feature’s appearance is undecided or an existing interface needs improvement.
Delegate code lookup, small edits, and diff reviews to three specialized subagents. Their compact, structured results help conserve the main agent's context, with guidance on when to delegate and when to keep work in the main conversation.
Add a live adjustment panel to an HTML page so viewers can explore colors, text sizes, spacing, themes, and motion. Changes appear immediately and are saved in the browser for the next visit.
Connect RuView sensing data to AI agents through tools for presence, breathing, and heart rate. Explore agent coordination and prototype storing agent state and decisions alongside sensing data in a shared RVF container.
Turn a structured LLM wiki into an interactive knowledge graph. It maps articles, topics, and sources, then adds entities and inferred relationships to help readers explore connections beyond the wiki’s explicit links.
Analyze a Figma file and turn its pages, screens, components, instances, and design tokens—shared design values—into an interactive graph. Open the dashboard to explore the file's structure and relationships.
Launch the Understand Anything web dashboard to explore an existing codebase knowledge graph, a map of its structure and relationships. Open the current project or a specified directory and receive the local access URL.
Explore design ideas with three to five distinct rough options using wireframes, simple screen layouts, and storyboards. Compare structure and flow, then develop selected options while keeping earlier rounds available for reference.