Generate kinetic typography animations for expressive agent-to-human communication. Use when you want to communicate with visual flair - animated text for announcements, alerts,…
IBM ContextForge — MCP Gateway + registry: federate MCP servers + A2A + REST/gRPC qua 1 endpoint. OTel tracing, JWT auth, RBAC, 7000+ tests. Production-ready.
IBM API Connect integration. Manage data, records, and automate workflows. Use when the user wants to interact with IBM API Connect data.
Comprehensive operational skill specification for Anthropic Claude to automate, script, troubleshoot, and optimize IBM Maximo, Maximo Application Suite (MAS), MBO Jython — from…
IBM X-Force Exchange integration. Manage data, records, and automate workflows. Use when the user wants to interact with IBM X-Force Exchange data.
Curate external IC10 resources without generating code. Use when user wants to find existing scripts, tutorials, or community solutions for Stationeers automation.
Debug and fix IC10 code issues. Use when user has IC10 code that isn't working, has errors, or behaves unexpectedly in Stationeers.
Find example IC10 code for common patterns. Use when user asks for examples, templates, or sample code for Stationeers automation like airlocks, pressure control, solar tracking,…
Explain IC10 code behavior in plain English. Use when user pastes IC10 code and asks what it does, how it works, or wants to understand existing Stationeers scripts.
Generate IC10 code from natural language descriptions. Use when user wants to create new IC10 code, asks for automation scripts, or needs IC10 implementation for devices like…
Look up Stationeers device properties and IC10 instruction syntax. Use when user asks about logic values, device pins, prefab hashes, or IC10 command syntax.
Draft a structured investment committee memo for PE deal approval. Synthesizes due diligence findings, financial analysis, and deal terms into a professional IC-ready document.
Erstellt IC-Memo mit Deal-These, Struktur, Risiken, Schutzmechanismen, offenen Punkten und Beschlussvorschlag im Private Equity Praxis.
Migrate old IC10 code to work with current Stationeers version. Use when user has legacy IC10 scripts that don't work due to game updates or breaking changes.
Generate hardware setup and wiring instructions for IC10 code. Use when user wants to know how to physically connect devices to use their IC10 scripts.
Simulates a realistic VC Investment Committee with three partner archetypes debating a startup's merits, concerns, and deal terms, scored across 28 dimensions.
Test IC10 code for correctness and logic bugs. Use when user wants to verify IC10 code works through test cases or simulation analysis.
Validate IC10 code for correctness. Use when user wants to check IC10 code for errors, constraint violations, or best practice issues before using it in Stationeers.
Parse .ics / iCalendar files or URLs, expand recurring events (RRULE), filter by date range / keywords, and return clean list of events.
Use to understand why ICALP (EATCS) has no artifact-evaluation track or badge scheme, and what plays the equivalent role for a pure-theory paper — the full version with complete…
Use when preparing an accepted ICALP (EATCS) paper for the LIPIcs open-access camera-ready — converting to the lipics-v2021 document class, de-anonymizing (restoring authors,…
Use when making an ICALP (EATCS) theory result independently checkable — writing complete, self-contained proofs in the appendix and a full version (arXiv/ECCC/HAL), pinning any…
Use when reasoning about how an ICALP (EATCS) submission is evaluated, covering lightweight double-blind review, the separate Track A and Track B program committees, the…
Use when auditing an ICALP (EATCS) Track A or Track B submission for HotCRP readiness, covering the correct-track submission server, abstract registration before the full-paper…
Use when splitting an ICALP (EATCS) theory paper between the 15-page main body and the clearly labelled appendix / full version — deciding what a referee must see in the body…
Use when deciding whether a theoretical computer science result belongs at ICALP (EATCS) and, if so, whether it is a Track A (algorithms, complexity, games) or Track B (automata,…
Use when planning an ICALP (EATCS) campaign backward from its single annual February deadline, through abstract registration, the anonymous submission, the Track B rebuttal…
Use when shaping the exposition of an ICALP (EATCS) theory paper — stating the model before the theorem, putting a legible theorem statement and its improvement over prior bounds…
Use when packaging ICASSP code, data, audio or image samples, model checkpoints, scoring scripts, seeds, and logs, even though ICASSP has no formal artifact badge.
Use when drafting an ICASSP rebuttal or author response to reviews, covering the recently added and short author-response window, the single-blind setting where reviewers already…
Use when preparing an accepted ICASSP paper for IEEE Xplore publication, covering the final 4+1 PDF, IEEE PDF eXpress validation, the IEEE electronic copyright form, integrating…
Use when strengthening ICASSP reproducibility across signal-processing modalities — pinning the scoring ruler for the paper's metric, dataset versions and splits, front-end/DSP…
Use when reasoning about ICASSP peer review — the IEEE Signal Processing Society technical-committee pipeline, EDICS-based assignment, single-blind reviewing, the recently added…
Use when auditing an ICASSP submission before the CMS portal deadline — the IEEE 4+1 page format, the single-blind rule that the author list must appear, EDICS subject selection,…
Use when deciding what goes in the four ICASSP pages versus a public release, given that ICASSP has no reviewed appendix — managing the 4+1 budget, curating optional multimedia…
Use when deciding whether a project fits ICASSP, the IEEE Signal Processing Society flagship spanning all signal processing, and specifically for the ICASSP-versus-Interspeech…
Use when planning an ICASSP project timeline — the annual clock from venue fit through the September paper deadline, single-blind review, the short winter rebuttal, spring…
Tee an icc-pipes pipe. Copy what one side writes into a pipe onto the same lanes of other pipes, byte for byte, in order, until removed.
ICCE 2026 論文を XeLaTeX + biblatex で作成する。Notion からコピペしたテキストを ICCE フォーマット準拠の LaTeX ソースに変換し、ビルドコマンドまで提示する。
Use when packaging code, models, or data for an ICCV paper at review or release time, covering anonymous in-archive code under the do-not-cite-your-repo rule, the June-to-October…
Use when ICCV reviews arrive and the one-page rebuttal must be drafted inside the one-week May window, covering the official template's constraints, evidence selection when no…
Use when an ICCV paper is accepted and the final version, releases, and October conference must be delivered, covering de-anonymization edits, the summer camera-ready window…
Use when hardening the reproducibility story of an ICCV paper, covering full recipe disclosure without a mandated compute form, protocol pinning for foundation-model and zero-shot…
Use when deciding whether a computer-vision project should target ICCV, weighing the biennial odd-year cadence and its two-year option cost, what the Marr Prize lineage says about…
Use when project-managing an ICCV campaign across the odd-year cycle, covering the autumn fork between CVPR and ICCV, the early-March registration and single submission deadline,…
Use when drafting or revising the prose and figures of an ICCV paper, covering writing for an international generalist reviewer pool, the inclusive 8-page economy, mechanism-first…
Use when responding to IEEE ICDE reviews, whether drafting a rebuttal to reviewer concerns or preparing a revise-and-resubmit change document for an invited ICDE revision under…
Use when preparing an accepted IEEE ICDE paper for camera-ready and IEEE Xplore publication: IEEE eCopyright and PDF-eXpress validation, the IEEE double-column final format,…
Use when explaining or planning around IEEE ICDE peer review: the two-round-per-edition structure, area-chair-coordinated assignment with at least three reviewers, two-phase…
Assess ATO boundary impact and manage supply chain risk for requirements. Use when analyzing how a requirement change affects the ATO boundary or supply chain.
Query the ICDEV™ compliance database using natural language. Converts questions to safe SQL queries and returns formatted results. Use when invoking /icdev-query.
Use when preparing for the review phase of an ICDM (IEEE International Conference on Data Mining) submission - planning for a venue whose tradition is NO author rebuttal,…
Use when preparing the ICDM (IEEE International Conference on Data Mining) camera-ready after acceptance - IEEE final formatting and eCopyright, de-anonymizing a triple-blind…
Use when reasoning about the ICDM (IEEE International Conference on Data Mining) review machinery - the triple-blind mechanics, the Accept / Accept-as-Short / Reject outcome…
Use when organizing supplementary and appendix material for an ICDM (IEEE International Conference on Data Mining) paper - deciding what belongs in the body, in an appendix that…
Use when planning an ICDM (IEEE International Conference on Data Mining) project timeline from venue fit through the abstract and full-paper deadlines, the long summer wait to the…
Use when preparing the "artifact" of an ICDT (International Conference on Database Theory) paper, which at a pure-theory venue is the complete-proofs full version rather than a…
Use when responding to ICDT (International Conference on Database Theory) referees — principally the first-cycle Revise-and-resubmit round, where you return a corrected paper that…
Use when preparing the final LIPIcs camera-ready for an accepted ICDT (International Conference on Database Theory) paper — the lipics-v2021 final document, mandatory ACM CCS…
Use when strengthening the verifiability of an ICDT (International Conference on Database Theory) paper — the theory-venue analogue of reproducibility — covering complete and…