Skip to content
Skills Library
AI & agents · Writing

feedback

/feedback

Guide the user to open a feedback issue for the simple-output-styles plugin. Use when the user wants to report feedback on an output style, the evals, the documentation, the installation, licensing, or wants to request a new style. Gathers the Claude Code version and the active style, then prepares a prefilled GitHub issue link.

Licence
ISC
Last repository change
23.08.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
3
Deprecation

No signals detected. Repository changed on 23.08.2026, without references to retired models or APIs.

Licence

ISC, otwarta.

What it does and when to use it

Guide the user to open a feedback issue for the simple-output-styles plugin. Use when the user wants to report feedback on an output style, the evals, the documentation, the installation, licensing, or wants to request a new style. Gathers the Claude Code version and the active style, then prepares a prefilled GitHub issue link.

Original author description

Guide the user to open a feedback issue for the simple-output-styles plugin. Use when the user wants to report feedback on an output style, the evals, the documentation, the installation, licensing, or wants to request a new style. Gathers the Claude Code version and the active style, then prepares a prefilled GitHub issue link.

How it works

  1. Step 1: pick the form
  2. Step 2a: style feedback
  3. Step 2b: general feedback
  4. Step 3: hand over the link
Original SKILL.md headings · 59 lines, 349 words
SKILL.md preview
---
name: feedback
description: Guide the user to open a feedback issue for the simple-output-styles plugin. Use when the user wants to report feedback on an output style, the evals, the documentation, the installation, licensing, or wants to request a new style. Gathers the Claude Code version and the active style, then prepares a prefilled GitHub issue link.
disable-model-invocation: true
---

# Provide feedback on simple-output-styles

Help the user open the right issue on the
[simple-output-styles repository](https://github.com/stefanobaghino/simple-output-styles)
with as little typing as possible. You gather the facts; the user reviews a
prefilled form and submits it.

Do not open the issue for the user with `gh` or the API. The repository closes
issues that bypass the forms. Always hand the user a prefilled form link.

## Step 1: pick the form

Ask the user one question: is the feedback about an existing style
(actionable-clarity, clarity-flow, classic-concise, developer-docs,
plain-language, technical-simplified), or about something else (evals and
methodology, documentation, installation, licensing and attribution, a new
style request, or anything else)? Skip the question if the request already
makes the answer clear.

## Step 2a: style feedback

Gather each field, asking the user only for what you cannot find yourself:

1. **Version**: run `claude --version` and use the output.
2. **Styles**: find the active output style: check `outputStyle` in
   `.claude/settings.local.json` and `.claude/settings.json` in the project,
   then `~/.claude/settings.json`. Confirm it with the user, since the
   feedback may be about a style other than the active one. If you find
   nothing and the user does not know, use `I don't know`.
3. **Sentiment**: ask whether the feedback is overall positive, mixed, or
   negative, unless the conversation already makes it obvious.
4. **Feedback**: ask for a short description if the user has not given one.
   If the feedback is about output produced in this conversation, offer to
   include the relevant excerpt.

Build the link (URL-encode every value; join multiple styles with commas):

```
https://github.com/stefanobaghino/simple-output-styles/issues/new?template=style-feedback.yml&styles=<styles>&version=<version>&sentiment=<Positive|Mixed|Negative>&feedback=<text>
```

## Step 2b: general feedback

Ask for the area if it is not clear — one of `Evals and methodology`,
`Documentation`, `Installation`, `New style request`,
`Licensing and attribution`, `Other` — plus the sentiment and a short
description, then build the link (URL-encode every value):

```
https://github.com/stefanobaghino/simple-output-styles/issues/new?template=general-feedback.yml&area=<area>&sentiment=<Positive|Mixed|Negative>&feedback=<text>
```

## Step 3: hand over the link

Show the link and tell the user to open it, review the prefilled fields, and
submit. Mention that dropdowns GitHub fails to prefill (this can happen with
multi-select) must be set by hand before the form submits.

Versions

RepositoryScoreLicence
This page · stefanobaghino/simple-output-styles100ISC
shaunjones-gh/lilystack100MIT
superset-sh/superset100MIT
Embassy-of-the-Free-Mind/sourcelibrary-v2100AGPL-3.0
minanyang/10x-agent100MIT
Insilico-org/plsi100MIT
blackbeard-tech/pair100Apache-2.0
optimiziramsi/skills100MIT
AMDResearch/omniprobe100MIT

Database snapshot: 13.11.2026 · package version a434fb20ef00 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100claude-output-styles
    Guide for creating Claude Code output styles and reusable response-format contracts. Use when creating, shipping, or customizing an output style for a session; defining the response shape an agent, command, or team worker must produce; standardizing worker reports so a team lead…
  • 100submit-feedback
    Turn a title and markdown body you write into a prefilled GitHub new-issue link, which the user clicks to file feedback about the skills under their own account. Nothing is sent by the skill. Use when the user asks to report a bug, a suggestion, or other feedback about a skill.
  • 100scenario-report
    Use when a Scenario user wants to report a bug or request a change, on the public tracker at github.com/scenario-labs/skills or by email to support@scenario.com: turning a failed generation, MCP tool error, or unclear skill into a reproducible report, collecting trace ids with…
  • 100style
    Pick, switch, clear, or create a Claude Code output style. Use when the user invokes /lej-output-fixer:style, asks to change how Claude writes (tone, verbosity, readability, formatting), or mentions output styles.
  • 100env-setup
    Claude Code 环境一键同步工具。从 GitHub 仓库同步所有配置到本地:output-styles 风格、CLAUDE.md 全局提示词、MCP 服务器配置、Agent 配置、Plugin 配置。适用于多设备统一环境、换电脑恢复、团队共享配置等场景。当用户需要从 GitHub 仓库同步 Claude Code/OpenClaw 环境配置时使用此 skill。
  • 100output-styles
    Use when the user asks to "change the output style", "make the agent explain its choices", "switch to learning mode" or "write a custom output style". Explains the builtin and custom styles and how to select them.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.