all publishers

korchasa

@korchasa source repo

58 published skills

  1. ▌
    Session History Analyzer 2 · korchasa bundle
    Analyzes past AI IDE sessions (Claude Code, OpenAI Codex, OpenCode) for LLM behavior errors: hallucinated diagnostics, context decay, format loss, language leakage, and excessive reading. Use when the user asks to inspect session history, find agent errors, or build a session error index.
    3 repo stars
  2. ▌
    Acceptance Tests All 2 · korchasa
    Run all framework acceptance tests. Default is sequential (single `deno task acceptance-tests`). Use `--parallel` for 5-subagent parallel mode. Triggers on "run all acceptance tests", "acceptance-tests all", "/acceptance-tests-all".
    3 repo stars
  3. ▌
    Orchestrate Work 2 · korchasa
    Split independent work items and run them in parallel through subagents. Use when a request names several areas that do not share files.
    3 repo stars
  4. ▌
    Root Cause And Fix 2 · korchasa
    Autonomous investigate → root-cause → fix → verify loop for this repo's own defects. Decides first whether the product or the measuring instrument is broken, fixes that layer, proves it with the test that would have caught it, and writes what it learned back into itself. Use when a scenario, check or benchmark fails and the cause is not known.
    3 repo stars
  5. ▌
    Improve Primitive From Benchmark 2 · korchasa bundle
    Fully autonomous improvement loop for flowai primitives — run the flowai SWE-bench arm, root-cause failures, generalize fixes beyond code, implement via Acceptance-Test TDD; gated by a critic subagent instead of the user. Use when asked to improve primitives from benchmark results or diagnose benchmark failures.
    3 repo stars
  6. ▌
    CLI · korchasa bundle
    Run Deno from the command line with the right flags — permissions for run/test, `deno task` over raw commands, unstable-feature opt-ins, and dependencies via `deno add`/`outdated`/`remove`. Use when wiring or running any Deno command — these flags are not guessable. Not for Deno Deploy (use deploy) or npm/package.json projects.
    3 repo stars
  7. ▌
    Epic · korchasa bundle
    Use when the user asks to plan a LARGE feature that spans multiple sessions or phases — produces an epic under the `tasks` role from AGENTS.md with dependency-ordered phases, atomic tasks, and per-phase status tracking. Use plan for single-session tasks. Do NOT trigger on generic planning, roadmap, or brainstorming requests.
    3 repo stars
  8. ▌
    Ask · korchasa bundle
    Use when the user asks a question to be answered from the project's memex (long-term knowledge bank for AI agents) rather than training data or the live web. Reads the index, opens relevant pages, follows one SALP-REF hop, synthesises a cited answer, files it back. Do NOT trigger on source-code or live-session questions.
    3 repo stars
  9. ▌
    Save · korchasa bundle
    Use when the user provides a source (URL, file path, or free text) to save into the project's memex — a long-term knowledge bank for AI agents. Stores the raw source, extracts entities into cross-linked pages, runs a backlink audit, and updates the index and activity log. Do NOT trigger on casual reads; only when the intent is to persist a source into the memex.
    3 repo stars
  10. ▌
    Init · korchasa bundle
    Initialize project with AGENTS.md and rules, handling both Greenfield (new) and Brownfield (existing) projects.
    3 repo stars
  11. ▌
    Deploy · korchasa bundle
    Manage Deno Deploy cloud services using both `deno deploy` and `deployctl`. Use this skill for deploying projects, managing cloud environments (Build/Dev/Prod contexts), monitoring logs, and troubleshooting deployment issues (like private npm dependencies).
    3 repo stars
  12. ▌
    Audit · korchasa bundle
    Use when the user asks to audit a memex (long-term knowledge bank for AI agents) for orphans, dead SALP REFs, missing sections, contradictions, or index drift. Runs a deterministic structural check, layers LLM-judgement findings, optionally auto-fixes trivial issues with `--fix`. Do NOT trigger on general code linting.
    3 repo stars
  13. ▌
    Adapt · korchasa bundle
    Adapt project-local flowai primitives (skills, agents, AGENTS.md artifacts, hooks) to project specifics. Standalone adaptation — independent of update.
    3 repo stars
  14. ▌
    Reflect · korchasa bundle
    Use when the user asks to reflect on the CURRENT session, analyze the agent's own process, audit context usage in this conversation, or extract lessons from how the current task was executed. Do NOT trigger for historical multi-session analysis — use reflect-by-history for that. Do NOT trigger on plain "what did you do?" style recaps.
    3 repo stars
  15. ▌
    Update · korchasa bundle
    Reconcile project-owned AGENTS.md, CLAUDE.md, and scaffolded artifacts with the current flowai framework templates.
    3 repo stars
  16. ▌
    Root Cause And Fix · korchasa
    Autonomous investigate → root-cause → fix → verify loop for this repo's own defects. Decides first whether the product or the measuring instrument is broken, fixes that layer, proves it with the test that would have caught it, and writes what it learned back into itself. Use when a scenario, check or benchmark fails and the cause is not known.
    3 repo stars
  17. ▌
    Investigate · korchasa bundle
    Use when the user asks to diagnose a bug, find the root cause of a failing behavior, or run a controlled hypothesis-by-hypothesis investigation with experiments and evidence. Produces a diagnostic report with a recommended fix (but does not apply the fix). Do NOT trigger on "fix this bug" when the cause is obvious, or on simple error-message lookups.
    3 repo stars
  18. ▌
    Maintenance · korchasa bundle
    Use when the user asks for a project health audit, maintenance sweep, or multi-category lead-engineer scan followed by interactive issue-by-issue resolution with user approval. Do NOT trigger on routine lint/test runs, single-file cleanups, or standard "check project" requests.
    3 repo stars
  19. ▌
    Acceptance Tests All · korchasa
    Run all framework acceptance tests. Default is sequential (single `deno task acceptance-tests`). Use `--parallel` for 5-subagent parallel mode. Triggers on "run all acceptance tests", "acceptance-tests all", "/acceptance-tests-all".
    3 repo stars
  20. ▌
    AI Ide Runner · korchasa bundle
    Run prompts in Claude Code, OpenCode, Cursor, or Codex CLIs from the current session — pick one IDE, fan out across several, or compare models. You are a courier that relays the other runtime's stdout verbatim, do not synthesise your own answer. Use on "run in <ide>", "compare <ide> vs <ide>", "try on <model>", "which IDE handles X better", "run across models".
    3 repo stars
  21. ▌
    Tasks Overview · korchasa bundle
    Show the current state of the project's tasks, hiding archived ones, by deriving the project's own task layout from AGENTS.md and generating a small project-local status script. Use when the user asks which tasks are open, in progress, or how far along the work is.
    3 repo stars
  22. ▌
    Delegate To Ide · korchasa bundle
    Delegate a task to another AI IDE's CLI (codex / claude / opencode / cursor-agent) through an isolated-context subagent. Use when the user says "delegate to <ide>", "have <ide> do <task>", "execute <task> in <ide>", "offload to <ide>" — running that CLI from a shell yourself is the wrong path, the isolated context is the point. For one-shot relay or fan-out use `ai-ide-runner`.
    3 repo stars
  23. ▌
    Select LLM Model · korchasa bundle
    Recommend which LLM model to use for a task. Use when asked "which model / best LLM for X", "pick a model for this task", or for a model shortlist ranked by live leaderboard evidence (coding, reasoning, agentic, tool-use, price, speed). Live-fetches public leaderboards and ranks models with per-axis rationale and citations.
    3 repo stars
  24. ▌
    Write Gods Tasks · korchasa bundle
    Supplies the accepted task format — GODS, meaning Goal, Overview, Definition of Done, Solution — and its file template. Use when the user asks what that format is, or to write up an already-decided piece of work in it. NOT for planning work before coding — weighing variants and critiquing a plan belong to the planning skill, which writes the file itself.
    3 repo stars
  25. ▌
    Write Dep · korchasa bundle
    Write a Development Enhancement Proposal (DEP) for a technical improvement. Use when the user wants to propose, document, or formalize a technical change for review.
    3 repo stars
  26. ▌
    Write Prd · korchasa bundle
    Produce a comprehensive Product Requirements Document (PRD) for a product feature. Use when the user asks to write a PRD or formalize a product feature's scope, goals, user value, and success metrics. Not for internal technical/engineering change proposals (those argue for a code/architecture change, not a product feature).
    3 repo stars
  27. ▌
    Session History Analyzer · korchasa bundle
    Analyzes past AI IDE sessions (Claude Code, OpenAI Codex, OpenCode) for LLM behavior errors: hallucinated diagnostics, context decay, format loss, language leakage, and excessive reading. Use when the user asks to inspect session history, find agent errors, or build a session error index.
    3 repo stars
  28. ▌
    Engineer Hook · korchasa bundle
    Creation and configuration of event hooks/plugins to manage agent behavior, command filtering, auditing, and automation. Works across IDEs (Cursor, Claude Code, OpenCode). Use when you need to: (1) Create a new hook (e.g., for formatting or security checks), (2) Configure hooks/plugins, (3) Implement logic for blocking or modifying agent actions via scripts.
    3 repo stars
  29. ▌
    Engineer Rule · korchasa bundle
    Guide for creating persistent AI rules (coding standards, project conventions, file-specific patterns). Use when users want to create a rule, add coding standards, set up project conventions, configure file-specific patterns, or ask about rules placement. Works across IDEs (Cursor, Claude Code, OpenCode).
    3 repo stars
  30. ▌
    Reflect By History · korchasa bundle
    Use when the user asks to review PAST sessions (not the current one), find recurring patterns across multiple sessions, or improve project primitives (rules, skills, hooks, docs) based on historical IDE transcripts. Do NOT trigger on current-session self-review — use reflect instead.
    3 repo stars
  31. ▌
    Engineer Skill · korchasa bundle
    Guide for creating agent-invocable Agent Skills (SKILL.md packages auto-discovered by description). Use when users want to create or author a skill (SKILL.md), or ask about skill structure or format. Not for user-invoked slash commands (a separate command-authoring concern). Works across IDEs.
    3 repo stars
  32. ▌
    Extract Codex Prompt · korchasa bundle
    Extract Codex system prompt from its compiled binary or JS bundle into a structured template file. Produces a document mirroring the real API request with exact prompt text, ant-only variants, feature-gated sections, and minified-variable mappings. Use when extracting, documenting, or comparing Codex prompt versions.
    3 repo stars
  33. ▌
    Engineer Command · korchasa bundle
    Guide for creating effective flowai commands. This skill should be used when users want to create a new command (or update an existing command) that extends flowai's capabilities with specialized knowledge, workflows, or tool integrations. Works across IDEs (Cursor, Claude Code, OpenCode).
    3 repo stars
  34. ▌
    Deep Research · korchasa bundle
    Multi-directional deep research with sub-agents, scoring, source verification, and cited synthesis. Use for comprehensive research, deep analysis, or evidence-backed answers. Produces executive summary + markdown report. Supports search tools, playwright-cli, and MCP.
    3 repo stars
  35. ▌
    Engineer Subagent · korchasa bundle
    Guide for creating effective Subagents (custom agent definitions). Use when users want to create a new subagent, set up task-specific agents, configure code reviewers, debuggers, or domain-specific assistants. Works across IDEs (Cursor, OpenCode).
    3 repo stars
  36. ▌
    Analyze Context · korchasa bundle
    Estimate total token usage and cost across conversation history, system prompts, and active rules. Use when the user asks how much context or how many tokens are in use, to audit context size, or to estimate session cost.
    3 repo stars
  37. ▌
    Configure Deno Commands · korchasa bundle
    Configure and maintain Deno development commands (check, test, dev, prod). Use when the user wants to set up or update the standard command interface in deno.json and scripts/ directory.
    3 repo stars
  38. ▌
    Improve Primitive From Benchmark · korchasa bundle
    Fully autonomous improvement loop for flowai primitives — run the flowai SWE-bench arm, root-cause failures, generalize fixes beyond code, implement via Acceptance-Test TDD; gated by a critic subagent instead of the user. Use when asked to improve primitives from benchmark results or diagnose benchmark failures.
    3 repo stars
  39. ▌
    Setup AI Ide Devcontainer · korchasa bundle
    Generate a .devcontainer (devcontainer.json plus optional Dockerfile) for AI-IDE development with AI CLI integration, skill mounting, and security hardening. Use when the user wants to set up or containerize a local dev environment for Claude Code, OpenCode, or flowai. Not for cloud deployment (e.g. Deno Deploy).
    3 repo stars
  40. ▌
    Browser Automation · korchasa bundle
    Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
    3 repo stars
  41. ▌
    Write Agent Benchmarks · korchasa bundle
    Build and run benchmarks that measure an AI AGENT's behaviour — scenarios, checklists, judged runs. Use when authoring or evaluating agent benchmark scenarios. Not for performance benchmarks of code (deno bench, criterion) or ordinary test suites — those measure a program, not an agent.
    3 repo stars
  42. ▌
    Engineer Plugin MCP · korchasa bundle
    Build AI-IDE plugin MCP elements - stdio JSON-RPC servers, tool schemas, host wiring for Claude Code/Codex, event-name mapping, and validation. Use when building or adding an MCP server to a plugin. Not for plugin manifests or packaging when the MCP server already exists (that is a separate packaging concern).
    3 repo stars
  43. ▌
    Draw Mermaid Diagrams · korchasa bundle
    Draw and edit Mermaid diagrams in Markdown. Use when the user wants to visualize processes, flows, sequences, or asks for diagrams. Load it before writing any Mermaid block, including when you already know the syntax — knowing how is the usual reason it gets skipped.
    3 repo stars
  44. ▌
    Engineer Plugin Hooks · korchasa bundle
    Build AI-IDE plugin hook elements - shared policies plus Claude Code/Codex/OpenCode/Cursor adapters for lifecycle events, blocking, audit, and context injection. Use when adding or configuring plugin hooks.
    3 repo stars
  45. ▌
    Engineer AI Ide Plugin · korchasa bundle
    Design and build complete AI-IDE plugins that bundle multiple components (skills, MCP tools, hooks) with packaging, manifests, marketplaces, and per-IDE validation. Use when the user wants to create, design, or package a multi-component AI-IDE plugin. Not for authoring a single standalone skill (use the skill-authoring skill instead).
    3 repo stars
  46. ▌
    Diagnose Benchmark Failure · korchasa bundle
    Use when a flowai benchmark fails and you need the cause from run artifacts before editing. Reads judge-evidence.md, the raw agent transcript, the sandbox SKILL.md, and scenario mod.ts; classifies the failure against a known taxonomy; produces an evidence-grounded report (no fixes). Do NOT trigger for passing benchmarks or generic skill iteration.
    3 repo stars
  47. ▌
    Setup Agent Code Style Deno · korchasa bundle
    Use when the user asks to add Deno/TypeScript code-style rules to AGENTS.md, or during initial Deno project setup when code-style guidelines need to be established. Do NOT trigger for non-Deno TypeScript projects (use setup-agent-code-style-strict), or for runtime-agnostic style advice.
    3 repo stars
  48. ▌
    Engineer Plugin Marketplace · korchasa bundle
    Design AI-IDE plugin marketplaces - requirements, host-specific payloads, local dogfood, release sync, and validation. Use when the user wants to create or publish a plugin marketplace.
    3 repo stars
  49. ▌
    Engineer Prompts For Instant · korchasa bundle
    Write or fix a prompt for a fast/cheap model (Gemini Flash, GPT-4o Mini, Haiku) so its output is stable and parseable. Use for any request to draft, tune or debug such a prompt — producing it IS the work, even when you could write one unaided. Not for reasoning models (use engineer-prompts-for-reasoning), model choice, or prompting a person.
    3 repo stars
  50. ▌
    Write In Informational Style · korchasa bundle
    Rewrite text in a dense, factual informational style with no fluff or marketing. Use when the user asks to write or rewrite docs or notes concisely or to apply a neutral informational tone.
    3 repo stars
  51. ▌
    Setup Agent Code Style Strict · korchasa bundle
    Add TypeScript strict-mode code-style rules to AGENTS.md. The rule text ships inside this skill, so write it from here, not from memory. Use when the user asks for strict-mode style rules in a TypeScript project. Not for Deno projects (use setup-agent-code-style-deno), non-strict configs, or explaining what `strict` turns on.
    3 repo stars
  52. ▌
    Engineer Prompts For Reasoning · korchasa bundle
    Write, structure or fix a prompt for a reasoning/smart model (Gemini Pro, GPT-4o, Claude Sonnet) so it holds context across a multi-step task. Use for any request to draft, structure, tune or debug such a prompt — producing it IS the work, even when you could write one unaided. Not for fast models (use engineer-prompts-for-instant).
    3 repo stars
  53. ▌
    Interactive Teaching Materials · korchasa bundle
    Creates interactive HTML teaching materials with clickable state diagrams. Use when the user asks to produce an explorable tutorial artifact, not to answer a question.
    3 repo stars
  54. ▌
    AI Skel TS Usage · korchasa bundle
    Scaffold a complete AI agent application skeleton with LLM integration, tool calling, observability, cost tracking, session management, and content fetching using @korchasa/ai-skel-ts. Use when the user asks to create an AI agent, add LLM integration, scaffold an AI application, or mentions "ai-skel", "agent skeleton", or "AI scaffold". Works with any programming language.
    3 repo stars
  55. ▌
    Django Migrations · korchasa
    Manage Django database migrations (makemigrations, migrate, squash).
    3 repo stars
  56. ▌
    Orchestrate Work · korchasa bundle
    Split independent work items and run them in parallel through subagents. Use when a request names several areas that do not share files.
    3 repo stars
  57. ▌
    Conduct QA Session · korchasa bundle
    How to conduct a Q&A session with the user. Canonical reference for FR-UNIVERSAL.QA-FORMAT.
    3 repo stars
  58. ▌
    Flowai Conduct QA Session · korchasa
    How to conduct a Q&A session with the user
    3 repo stars