Results for “systems-paper”

Generate, continue, revise, polish, and stress-test game theory research papers. Use when the user provides a game theory topic, phenomenon, draft, outline, model idea, literature anchor, reviewer comments, or asks for 博弈论论文生成, 选题建模, 文献迁移, 模型修正, 均衡分析, 数值模拟, 论文润色, 改稿打磨, or R&R response work.

Search scientific papers via the BGPT MCP server and retrieve structured experimental data — methods, results, conclusions, quality scores, and 25+ metadata fields per paper.

Manage design systems in Stitch using MCP tools. Includes retrieval of assets, creating/updating design systems in Stitch, and applying them to screens.

Publish and manage research papers on Hugging Face Hub, including creating paper pages, linking papers to models and datasets, claiming authorship, and generating professional markdown-based research articles.

Manage design systems in Stitch using MCP tools, including retrieval of assets, creating or updating design systems, and applying them to screens.

Provides nine skills for Nature-journal-family academic publishing, covering figure creation, prose polishing, manuscript writing, citation formatting, data availability statements, paper reading, reviewer responses, paper-to-PPT conversion, and academic search via an MCP server.

Map control, influence, and concern after systems analysis. Use when students need wise agency without being made responsible for everything.

Search scientific papers and retrieve structured experimental data extracted from full-text studies via the BGPT MCP server, returning 25+ fields per paper including methods, results, sample sizes, quality scores, and conclusions.

Map a current event below the surface into patterns, structures, and mental models. Use when a class or team needs systemic understanding before action.

Plan a chunk of work too big for one agent session by putting it on a shared whiteboard — a map of investigation tickets on GitHub Issues — working them until nothing is left to decide, then snapshotting the board into a handoff artifact. Tickets needing nobody are worked back-to-back; the session stops when the human is the blocker. Use only when the user explicitly invokes whiteboard or asks to draw, work, run, or snapshot a whiteboard/map — not for ordinary planning requests.