Skip to main content
skill CX Codex

corezoid-feedback — Claude Code skill: features and setup

corezoid-feedback is a Claude Code skill that gathers bug reports and improvement requests about the Corezoid plugin. It offers to submit feedback after a complaint or a platform-level mistake.

MIT ★ 74 updated 2026-10-29

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add corezoid/corezoid-ai-plugin
/plugin install corezoid@corezoid
Open on GitHub

What corezoid-feedback does

corezoid-feedback detects complaints about the Corezoid plugin and offers to pass them to the Corezoid team. It also reacts when the agent picks the wrong node type, API, process structure, or MCP tool, or misses a required platform field. Changes to business logic, such as editing values or conditions, do not trigger feedback collection.

With the user's consent, the skill gathers the problem and expected result from the conversation, then asks for missing details. Before calling send-feedback, it shows the prepared report, says that tokens, API keys, and secrets are masked, and waits for explicit approval. Submission requires access to the send-feedback MCP tool.

What it helps with

  • report a Corezoid plugin failure to its team
  • send a request to improve the plugin
  • flag an incorrect node or API choice
  • prepare a problem report from the conversation

Example prompts for the agent

  • The plugin did something I didn't ask for. Offer to report it to the Corezoid team.
  • I'd like to suggest an improvement to the Corezoid plugin.
  • The plugin chose the wrong node type. Offer to send feedback.

How to install corezoid-feedback

1Plugin marketplace

/plugin marketplace add corezoid/corezoid-ai-plugin
/plugin install corezoid@corezoid

This installs the whole corezoid plugin with all its skills

2Skills CLI (Vercel)

npx skills add corezoid/corezoid-ai-plugin --skill corezoid-feedback -a claude-code

3Manually: put the files in place

~/.claude/skills/corezoid-feedback/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/corezoid-feedback/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about corezoid-feedback

How do I install corezoid-feedback in Claude Code?

Add the marketplace with /plugin marketplace add corezoid/corezoid-ai-plugin, then install the plugin with /plugin install corezoid@corezoid.

What does corezoid-feedback do?

It detects plugin complaints and improvement requests, gathers relevant details from the conversation, and submits feedback to the Corezoid team after explicit user approval.

What does corezoid-feedback need to work?

Submitting feedback requires access to the send-feedback MCP tool. The skill displays the report and waits for approval before calling it.

Source text

SKILL.md · MIT
---
name: corezoid-feedback
description: >
  Collects and submits bug reports, improvement requests, and quality signals
  about the Corezoid plugin to the Corezoid team. Activate in two cases:

  1. The user signals dissatisfaction, reports a bug, or requests an
  improvement — phrases like "this is not what I asked", "it did the wrong
  thing", "that's broken", "можно было бы лучше", "хотелось бы чтобы",
  "было бы здорово если", "сработало не так", "это не то", "оно сломало
  мой процесс", "не то что я хотел", or explicitly asks to report something.

  2. The user message reveals a platform-level mistake — wrong node type,
  wrong API choice (Corezoid vs Simulator), wrong process structure, wrong
  MCP tool, missing required platform field — even without explicit phrases.
  In this case add one offer line to whatever response you are giving; do
  not open a separate flow unless the user agrees.

  Do NOT activate for business-logic iterations: changing values, adding
  fields, renaming things, adjusting conditions. These are normal user-driven
  changes, not platform issues.
---

# Corezoid Feedback Skill

You help users report bugs, suggest improvements, and flag unexpected behavior
in the Corezoid plugin to the Corezoid team.

## When to offer and how to phrase it

**Case 1 — bug or broken behavior.** The user reports something that stopped
working, produced wrong output, or broke their process. Offer once, adapting
to the context:

> "Хотите сообщить о баге команде Corezoid?"

**Case 2 — improvement request.** The user hints that something could work
better ("хотелось бы", "было бы здорово", "можно улучшить"):

> "Хотите отправить пожелание команде Corezoid?"

**Case 3 — platform-level mistake by the plugin.** The message reveals that
the plugin chose the wrong node type, wrong API, wrong structure, or wrong
MCP tool. Add one line to the normal response without interrupting it:

> "Хотите сообщить об этом команде Corezoid?"

In all cases: offer once per problem context, do not repeat if the user declines.
Do not offer when the user is iterating on business logic.

## What to collect

If the user agrees, **derive as much as possible from context** and ask only for what is missing:

| Field | Meaning |
|-------|---------|
| `problem` *(required)* | What went wrong, in the user's words |
| `expected` | What the user expected to happen |
| `proposed_solution` | How the user thinks it should work |
| `tool` | Which tool or skill was involved (derive from context) |
| `transcript_excerpt` | Short relevant excerpt of the dialog |
| `contact` | Optional email or handle for follow-up |

## Mandatory confirmation step

**Before calling `send-feedback`, always show the user exactly what will be sent:**

```
Планирую отправить следующее:
• Проблема: <problem text>
• Ожидалось: <expected text>
• Предложение: <proposed_solution text>
• Инструмент: <tool>
• Выдержка из диалога: <transcript_excerpt>
• Контакт: <contact or "не указан">
```

Explicitly note that any tokens, API keys, and secrets have been masked. Ask the user to confirm, edit, or cancel before proceeding.

**Never call `send-feedback` without an explicit "yes" / "да" / "отправляй" from the user.**

## Calling the tool

After confirmation, call the MCP tool:

```
send-feedback(
  problem: "<user's description>",
  expected: "<optional>",
  proposed_solution: "<optional>",
  tool: "<optional>",
  transcript_excerpt: "<optional, keep short>",
  contact: "<optional>"
)
```

The tool performs its own secret redaction automatically. Pass the raw user text — do not pre-redact in your message to the tool.

## After the tool responds

On success the tool returns a ticket id, for example:
`Feedback submitted. Ticket id: 6a3b8b6ab677ac777074794f`

Tell the user:
> "Спасибо! Заявка отправлена, номер: `6a3b8b6ab677ac777074794f`. По нему можно ссылаться при дальнейшем обсуждении с командой Corezoid."

On error, respond gently:
> "Не удалось отправить фидбек прямо сейчас. Попробуйте позже или напишите на [email protected]."

Do not show the technical endpoint URL or error details to the user.

© Corezoid · MIT · corezoid/corezoid-ai-plugin

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set30

The whole set →
corezoid-logout The corezoid-logout skill removes saved Corezoid credentials from ~/.corezoid/config.json for the current working directory. Use it to end your Corezoid session or switch to another account. CX Codex +1 ★ 74repo stars commit Automates commits in the corezoid-ai-plugin repository: calculates semver version bumps, updates manifest files, and edits CHANGELOG.md. CX Codex +1 ★ 74repo stars corezoid-api-connector corezoid-api-connector — a skill for automating Corezoid operations through the public API. Builds processes that call /api/2/json/, work with nodes, processes, and tasks on the platform. CX Codex +1 ★ 74repo stars corezoid-describe corezoid-describe is a Claude Code skill that creates and updates descriptions for Corezoid processes, folders, and projects without changing node logic. CX Codex +1 ★ 74repo stars corezoid-lifecycle The corezoid-lifecycle skill for Claude Code pauses, resumes, or relocates Corezoid processes and folders only on explicit user instruction. CX Codex +1 ★ 74repo stars corezoid-retro corezoid-retro — a skill that analyzes a completed Corezoid work session, extracts actionable insights, and stores them as workspace CLAUDE.md updates, team feedback, and permission rules. Every session teaches the next one. CX Codex +1 ★ 74repo stars corezoid-dashboard-manager corezoid-dashboard-manager is a Claude Code skill that builds Corezoid dashboards via cz-dashboards, mapping process node task counters to charts and setting grid layouts. CX Codex +1 ★ 74repo stars corezoid-git-context The corezoid-git-context skill records meaningful Corezoid session changes in stage documentation and syncs the git mirror. Use it after real process work. CX Codex +1 ★ 74repo stars

Project sponsors

Companies that keep this analytics open