Results for “ode”

Link Figma design components with their code counterparts through Code Connect, helping design-system updates flow into the codebase. This catalogue entry points agents toward the full upstream workflow.

• Linking Figma components to code components
• Reflecting design-system updates in code
• Introducing a Code Connect workflow

Get guidance on Codex, OpenAI APIs, and ChatGPT Work using official documentation with citations. Use it to investigate settings and errors, compare models, plan migrations, or work on prompts and API integrations.

• Check Codex settings and troubleshoot errors
• Compare models for a particular task
• Plan a model migration and prompt changes

Delegates repository analysis or coding tasks to MiniMax Code without opening its interactive interface. It runs one task in the specified project with a time limit, then uses the final response as the result.

• Delegating repository analysis to MiniMax Code
• Investigating a failing test without editing files
• Requesting explicitly authorized code changes

Reproduce a Codex or Claude Code feature in Qwen Code or another command-line agent. Capture requests, terminal output, and state changes, then use that evidence to implement focused behavior and add a verification path.

• Reproduce an existing agent's slash command
• Inspect request formats and tool definitions
• Compare terminal output and saved state

Compare a feature implemented in Qwen Code with Codex or Claude Code under the same scenario. Capture communication and terminal records, inspect tool definitions and outputs, and guide fixes toward matching observable behavior.

• Checking a reproduced feature against its reference agent
• Comparing tool definitions and required arguments
• Investigating differences in terminal output

Deploy Model Garden models to Agent Platform endpoints, the addresses used for model requests. Check supported hardware and estimated hourly costs, inspect deployment progress, test predictions, and remove deployed resources after use.

• Choose a deployable model and supported hardware
• Estimate hourly deployment costs before approval
• Check deployment progress and test predictions

Delegate coding, analysis, planning, and reviews from Codex to Claude Code through its command-line interface. Capture responses, resume sessions, or run independent tasks in parallel, then verify changed files and test results independently.

• Delegating implementation or refactoring from Codex
• Getting another model's review of code changes
• Continuing delegated work across multiple sessions

Evaluate code generation models with HumanEval, MBPP, and multilingual benchmarks. The skill guides test execution and model comparisons using pass@k, an estimate of whether at least one of k generated solutions passes the tests.

• Compare code generation models on shared benchmarks
• Measure code generation performance across languages
• Evaluate instruction-tuned coding models

Review estimated spending, token usage, and cache hit ratios across Claude Code, Codex, and Grok using local logs. Filter by time, project, or provider, while keeping currencies separate and identifying models without pricing.

• Reviewing estimated spending for the past seven days
• Comparing usage across providers and models
• Checking costs for a specific project or time range

Investigate LazyCodex and Codex bugs using reproduction results and source code. Identify the responsible repository, then prepare or submit an English GitHub report with evidence, likely causes, fix guidance, and a verification plan.

• Report a reproducible LazyCodex or Codex bug
• Identify which project owns a defect
• Add new evidence to an existing issue

Run OpenCode without an interactive interface to analyze a repository or perform requested coding work. Collect its structured output, summarize results and tool errors, or use its response to compare coding agents.

• Investigating a failing test without edits
• Delegating project analysis to OpenCode
• Requesting explicitly authorized code changes

Set up CodeQL security scanning in GitHub Actions or with the local CLI. Get guidance on language settings, build steps, analysis rules, result uploads, and troubleshooting so you can configure scans and interpret their findings.

• Adding security scans to GitHub Actions
• Running local scans with the CodeQL CLI
• Investigating failed builds or result uploads

Delegate research, coding, and testing from Claude Code to opencode workers. Run independent tasks in parallel with separate Git working directories, combine findings, track token use, and compare solo execution with coordinated workers.

• Delegate a small task to one opencode worker
• Implement independent changes in parallel
• Review a diff from four perspectives

Generate a PUA KPI and performance report card from Codex CLI. This command alias loads pua-pro and provides a Codex equivalent of the Claude Code /pua:kpi command through $pua-kpi.

• Generate a PUA performance report card in Codex
• Use the equivalent of /pua:kpi from Codex CLI
• Load pua-pro to produce a KPI report

Pencil CLI（`pencil`コマンド）だけを使って、.penファイル（Pencilで作成されたデザインファイル）の中のNodeのデザインデータ（属性・構造）とスクリーンショット画像を読み取り専用で取得するスキル。Node IDが分かっているケースだけでなく、名前の正規表現（例: 「ヘッダー」「.*Button」）、Nodeタイプ（frame / text / image など）、再利用可能コンポーネント、特定フレーム配下、ドキュメント全体のトップレベルなど、**ID以外の指定方法**にも対応する。ユーザーが「.penのこのNodeの中身を見せて」「特定コンポーネントのデザインデータを取り出して」「Nodeのスクリーンショットだけ欲しい」「ヘッダーの構造を確認したい」「ボタンのスタイルをコピーしたい」「再利用可能コンポーネント一覧を見せて」「ドキュメント全体の構造を覗きたい」「全てのテキストNodeを取得して」のように.pen内の要素の調査・参照・確認・抜き出しを依頼した場合に必ずこのスキルを使う。インタラクティブモード（`pencil interactive`）で `batch_get` の `nodeIds` / `patterns` / `parentId` を使い分けてNode属性をJSONで取得し、`get_screenshot` / `export_nodes` で画像を`.pen`と同階層の`snapshots/`にPNG出力する。編集はしない（`save()`を呼ばない）ため、対象ファイルは絶対に書き換わらない。Pencil MCPには依存せず`pencil`コマンドのみで完結。

The English summary is being prepared. Showing the original description.

Resume unfinished Claude Code work in Muse Code using a local session log. After the user selects a session, the skill recovers recent requests, decisions, and tool results, checks current files, and continues the task.

• Continuing unfinished Claude Code work in Muse Code
• Recovering task context from a session ID or log path
• Checking saved progress before resuming a task

Add OpenCode as an agent runtime in NanoClaw to use models from OpenAI, Google, OpenRouter, DeepSeek, and other supported services. The skill covers installation, authentication, group selection, and default model changes.

• Adding OpenCode to an existing NanoClaw installation
• Switching an agent group to OpenCode
• Changing the default model without signing in again

Turn 3D models into printer instructions called G-code with OrcaSlicer. The skill selects existing printer and material presets, slices the model, and checks dimensions and output settings before handing over the files.

• Prepare an STL model for a specific printer
• Slice models using existing material presets
• Check model size and print settings

Complete the PUA survey through a guided flow in Codex CLI and save responses to a local JSON file. This alias provides the equivalent of Claude Code’s /pua:survey command without sending answers anywhere.

• Complete the PUA survey in Codex CLI
• Save survey answers to a local JSON file
• Use the equivalent of /pua:survey from Codex

Disables PUA's always-on mode from Codex CLI and sets feedback frequency to zero. The alias updates the local configuration while preserving unknown fields, then reports completion with evidence from the executed command.

• Disabling PUA's always-on mode in Codex CLI
• Setting PUA feedback frequency to zero
• Using a Codex equivalent of Claude Code's /pua:off

Keep chat-ui model settings aligned with the HuggingFace router. Add descriptions for newly available models, check reasoning support, enable artifact panels based on model size, and remove settings for models no longer served.

• Add newly released models to chat-ui settings
• Remove settings for models no longer served
• Check reasoning support and artifact eligibility

Build a threat model that identifies valuable assets, attack entry points, potential threats, and mitigation priorities. Use source code and past vulnerabilities, an interview with the application owner, or a combination of both.

• Reviewing security risks during system design
• Assessing an inherited codebase without its owner
• Refining a code-based draft with the application owner

Turn a Figma design into code that fits an existing project. Reuse its components and shared style values, follow designer notes and component mappings, and adapt Figma's reference output to the project's framework and conventions.

• Implementing a screen from a Figma design
• Reusing existing project components in a design implementation
• Applying designer notes and shared style values

Write and improve documentation for ComfyUI nodes in per-node JSON files. Use when asked to document nodes, write node descriptions, add tips to nodes, improve node docs, enrich node content, fill in empty node descriptions, or batch-write documentation for new/updated nodes. Also triggers on "write docs for nodes", "document the new nodes", "improve node tips", "fill in node descriptions", "enrich nodes", "node content pass", "update nodes", "sync comfyui nodes", "new comfyui version", or "node enrichment".

The English summary is being prepared. Showing the original description.