New in week 43

Analyzes git repositories and commit history

Per-case mocked MCP override smoke skill used by skill-up e2e tests.

MCP mocked marker smoke skill used by skill-up e2e tests.

MCP stdio marker smoke skill used by skill-up e2e tests.

SDD-RIPER workflow executor with phase gating

A skill with potentially flaky behavior for testing retry

Verify Sandbox MCP can be installed and called from skill-up.

Triggered when the user needs to convert data formats, such as CSV to JSON, JSON to YAML, or XML to JSON.

Triggered when the user submits code or requests a code review.

Triggered when the user expresses boredom, low mood, frustration, irritation, or a need to relax.

Analyzes code files and reports statistics including line counts, file counts by extension, and total size.

Decode the marker fixture used by the DeepSeek Harness integration example.

Ask for missing deployment settings and summarize the requested configuration without deploying it.

Capture and review Agent Skill observations, and create, run, diagnose, or iteratively improve Skill evaluations (evals) with the skill-up CLI.

Build, test, and deploy DeFi trading strategies using the Almanak SDK.

Interactively debug source code — set breakpoints, step through execution line by line, inspect live variable state, evaluate expressions against the running…

Generate web assets including favicons, app icons (PWA), and social media meta images (Open Graph) for Facebook, Twitter, WhatsApp, and LinkedIn.

Invoke when the user asks about accessibility, inclusive design, colorblind mode, remappable controls, screen reader support, EAA compliance, CVAA, difficulty…

Invoke when the user asks about art style, visual language, style guide, character design, environment art, UI art direction, asset pipeline, reference…

Invoke when the user asks about sound design, music direction, audio identity, adaptive audio, spatial audio, SFX, sonic palette, dialogue systems, audio…

Invoke when the user asks about creative vision, game pillars, core fantasy, design direction, art style decisions, scope arbitration, or creative conflicts.

Invoke when the user asks about game mechanics, core loop, balance, progression, economy design, reward systems, onboarding, game feel, systems design, or GDD…

Invoke when the user asks about game economy, currency design, monetization, virtual currency, inflation, sink/source balance, F2P economy, premium currency…

Invoke when the user asks about story structure, branching narrative, dialogue systems, world-building, character design, environmental storytelling…

Invoke when the user asks about sprint planning, milestone tracking, scope management, risk assessment, scheduling, resource allocation, team velocity, or…

Invoke when the user asks about testing strategy, bug tracking, playtest methodology, regression testing, release certification, QA automation, or bug triage.

Invoke when the user asks about game architecture, engine selection, performance budgets, technical debt, build pipeline, cross-platform, rendering pipeline…

Invoke when the user asks about game UI, onboarding, HUD design, controller navigation, player feedback, usability testing, colorblind modes, or game-specific…

Invoke when the user works with Godot Engine or asks about GDScript, scene composition, signals, resources, shaders, GDExtension, physics, or Godot UI.

Invoke when the user works with Unity or asks about C#, MonoBehaviour, DOTS/ECS, Shader Graph, Addressables, UI Toolkit, URP/HDRP, or ScriptableObjects.

Invoke when the user works with Unreal Engine 5 or asks about C++/Blueprints, GAS, replication, Nanite, Lumen, CommonUI, Enhanced Input, or World Partition.

Invoke when the user needs to set up analytics, define telemetry events, establish KPIs, build dashboards, configure A/B testing, or implement data-driven…

Invoke when the user needs to validate game balance, tune economy systems, analyze progression curves, evaluate difficulty scaling, or check reward pacing.

Invoke when the user wants to brainstorm game ideas, explore concepts, run structured ideation, or develop a new game concept from scratch.

Invoke to set up CI/CD pipelines for game builds -- automated testing, build pipelines, and deployment to Steam, itch.io, or Epic.

Invoke when the user wants a game-specific code review, architecture check, or technical analysis of game code.

Invoke when the user wants feedback on a game design document, GDD review, design evaluation, or consistency check on an existing design.

Invoke for guided game design document authoring -- section-by-section GDD creation with validation, pillar alignment, and scope tier marking.

Invoke for game jam participation -- 48-72 hour compressed development workflow.

Invoke when the user is preparing for game release, needs a launch checklist, store submission guidance, go/no-go decision framework, or day-one patch planning.

Invoke when the user asks about localization, translation, i18n, internationalization, string extraction, cultural adaptation, RTL support, CJK text, or EFIGS…

Conduct market research for a game concept -- competitive landscape, market sizing, audience analysis, trend detection, and positioning strategy.

Invoke when the user wants to plan, execute, or analyze a structured playtest session with behavioral observation.

Run a structured post-mortem analyzing what went well, what went wrong, and extractable lessons.

Invoke when the user wants to rapidly prototype a mechanic, test a proof of concept, run hypothesis-driven development, or validate a game idea before full…

Run a game development post-mortem rooted in the GDC tradition.

Generate documentation from existing code or prototypes.

Evaluate project scope against timeline and resources.

Invoke when the user needs to plan a development sprint, break down tasks, schedule game work, or organize a sprint with cross-discipline dependencies.

Invoke when the user wants to start a new game project, set up project scaffolding, onboard into an existing codebase, or initialize GameForge session state.