KS
Killer-Skills

s_catann — how to use s_catann how to use s_catann, what is s_catann, s_catann setup guide, s_catann alternative, s_catann vs other AI skills, s_catann install, s_catann tutorial, s_catann documentation, s_catann for AI agents

v1.0.0
GitHub

About this Skill

Perfect for Development Agents needing standardized output formats with codex objects and visual debugging through screenshots. s_catann is a technical skill that automates the process of formatting AI agent responses, including the removal of ANSI color codes and the inclusion of visual elements.

Features

Prepends { codex: { ... } } object to final responses
Renders human-readable output by removing ANSI color codes
Includes screenshots as the first visual part of the final response
Supports inclusion of full test_catann.sh output in final responses
Starts the dev server for testing and development purposes
Handles test output and screenshots even in cases of test failure

# Core Topics

dcep93 dcep93
[0]
[0]
Updated: 2/28/2026

Quality Score

Top 5%
42
Excellent
Based on code quality & docs
Installation
SYS Universal Install (Auto-Detect)
Cursor IDE Windsurf IDE VS Code IDE
> npx killer-skills add dcep93/firegame/s_catann

Agent Capability Analysis

The s_catann MCP Server by dcep93 is an open-source Categories.community integration for Claude and other AI agents, enabling seamless task automation and capability expansion. Optimized for how to use s_catann, what is s_catann, s_catann setup guide.

Ideal Agent Persona

Perfect for Development Agents needing standardized output formats with codex objects and visual debugging through screenshots.

Core Value

Empowers agents to prepend codex objects and include screenshots in their responses, providing a human-readable output with ANSI color codes removed, and supporting protocols like file inclusion for 'screenshot.png' and command execution for 'test_catann.sh'.

Capabilities Granted for s_catann MCP Server

Prepending codex objects for standardized responses
Including screenshots for visual debugging and testing
Rendering human-readable test outputs with ANSI color codes removed

! Prerequisites & Limits

  • Requires 'screenshot.png' to exist for visual inclusion
  • Dependent on 'test_catann.sh' output for final response generation
  • May require additional setup for ANSI color code removal
Project
SKILL.md
4.2 KB
.cursorrules
1.2 KB
package.json
240 B
Ready
UTF-8

# Tags

[No tags]
SKILL.md
Readonly

Skill: catann

Always prepend the { codex: { ... } } object from the test output (if it appears) to the final response, and then include the screenshot (if screenshot.png exists) as the first visual part of the final response, even when the test fails. Always include the full test_catann.sh output in the final response. The output can include ANSI color codes; when presenting it, render a human-readable version with ANSI removed (plain text).

Summary flow

  1. Start the dev server (keep it running).
  2. Run tests and capture output.
  3. Collect screenshot.png (if present).
  4. Host the image locally and attach it.
  5. Report results + full logs.

Pre-commit validation

Before committing changes, validate TypeScript by running:

bash
1cd firegame/app/firegame 2yarn lint 3yarn tsc --noEmit

Then validate the regression catann suite specifically:

bash
1cd firegame/app 2CATANN_REGRESSION=1 timeout 300s bash ./test_catann.sh --codex

Regression mode is enabled via CATANN_REGRESSION=1; only regression-mode choreos execute when this env var is set.

If either command fails (including duplicate/overwritten property diagnostics such as TS2783), fix the issue and rerun until both pass. Treat this as the authoritative typecheck gate before continuing with test runs or commits.

Anti-slop change validation (required)

Before committing any non-trivial Catann change:

  1. Stage the intended patch and inspect the full diff.
  2. Identify suspicious additions (extra helpers, hardcoded branches, test-only magic values, broad refactors) and explicitly test whether each is necessary.
  3. Prefer the simplest implementation with the smallest diff that preserves behavior.
  4. Re-run the workflow and compare the resulting { codex: ... } printout to confirm no regression.

If removing a new abstraction/helper yields the same behavior, do not keep it.

Timestamp format (NYC time)

At the start of each numbered step, record a timestamp in America/New_York using:

bash
1TZ=America/New_York date "+%Y-%m-%d %H:%M:%S %Z"

Include the raw command output in your notes/output for that step.

1) Start the dev server (keep running for hot reloads)

bash
1cd firegame/app/firegame 2yarn start

Keep this command running.

2) Run tests and capture output

In another shell:

bash
1cd firegame/app 2timeout 300s bash ./test_catann.sh --codex

If the timeout is hit, report it as a failure and proceed to collect the screenshot (if available).

If CODEX_HOME is not set, omit --codex so test_catann.sh can start the server for you.

Fix mode (only if explicitly requested)

If the prompt explicitly requests, fix the failing test and rerun the Catann workflow until it passes. For a solution, are only allowed to change files in firegame/app/firegame/src/routes/catann/app/gameLogic. Do not stop after a single failing attempt or timeout; keep re-running the test command after each fix until you get a clean pass. Once it passes, continue with the screenshot steps. Follow AGENTS.md in the same folder as this skill doc. Do not introduce global variables, global state, or manipulate the DOM or window objects.

Game-logic purity guard

When editing app/gameLogic, keep logic explicitly game-behavior driven. Avoid hardcoded test fixtures, magic IDs, lookup tables for recorded runs, or special-case branches that exist only to satisfy a single capture.

If test data is required, consume values that the harness already provides via existing override paths rather than encoding constants in game logic.

3) Locate output image (if present)

bash
1cd firegame/app/firegame/test-results 2ls 3# pick the folder just created, then: 4cd <test-results-subfolder> 5ls 6# expect: screenshot.png

4) Host image locally (for browser pickup)

bash
1python -m http.server -b 0.0.0.0 8001

5) Screenshot capture (browser tool / Playwright)

If a browser tool is available, open http://localhost:8001/screenshot.png and include it in the response. If no browser tool is available, still mention whether screenshot.png was found and hosted. Ensure the screenshot capture waits for network idle (e.g., use a browser tool's equivalent of Playwright's wait_until='networkidle') before attaching the image.

Related Skills

Looking for an alternative to s_catann or building a Categories.community AI Agent? Explore these related open-source MCP Servers.

View All

widget-generator

Logo of f
f

widget-generator is an open-source AI agent skill for creating widget plugins that are injected into prompt feeds on prompts.chat. It supports two rendering modes: standard prompt widgets using default PromptCard styling and custom render widgets built as full React components.

149.6k
0
Design

chat-sdk

Logo of lobehub
lobehub

chat-sdk is a unified TypeScript SDK for building chat bots across multiple platforms, providing a single interface for deploying bot logic.

73.0k
0
Communication

zustand

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

72.8k
0
Communication

data-fetching

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

72.8k
0
Communication