Skip to content
Skills Library
Other · Tool integration

feedback

/feedback

Report a problem with 10x Agent or ask it for something — draft a bug report or feature request for minanyang/10x-agent in its own issue forms, from any project, without that project's name or paths, and file it, or a comment on a matching issue, on approval. Use when the user runs /10x:feedback, reports that 10x does not work, or asks 10x for a feature.

Repository
10x-agent ↗
Licence
MIT
Last repository change
13.11.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
1
Deprecation

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

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Report a problem with 10x Agent or ask it for something — draft a bug report or feature request for minanyang/10x-agent in its own issue forms, from any project, without that project's name or paths, and file it, or a comment on a matching issue, on approval. Use when the user runs /10x:feedback, reports that 10x does not work, or asks 10x for a feature.

Original author description

Report a problem with 10x Agent or ask it for something — draft a bug report or feature request for minanyang/10x-agent in its own issue forms, from any project, without that project's name or paths, and file it, or a comment on a matching issue, on approval. Use when the user runs /10x:feedback, reports that 10x does not work, or asks 10x for a feature.

How it works

  1. Step 1 — Classify
  2. Step 2 — Look for an existing issue
  3. Step 3 — Draft, check and stop
  4. Step 4 — File it
  5. Replies
  6. Never
Original SKILL.md headings · 85 lines, 1,025 words
SKILL.md preview
---
name: feedback
description: Report a problem with 10x Agent or ask it for something — draft a bug report or feature request for minanyang/10x-agent in its own issue forms, from any project, without that project's name or paths, and file it, or a comment on a matching issue, on approval. Use when the user runs /10x:feedback, reports that 10x does not work, or asks 10x for a feature.
disable-model-invocation: true
allowed-tools:
  - Bash(10x-feedback init)
  - Bash(10x-feedback check *)
  - Bash(gh issue list --repo minanyang/10x-agent *)
  - Bash(gh issue view *)
---

# Report a 10x problem

`/10x:feedback <what>` turns a problem with 10x Agent, or a request for it, into an issue on `minanyang/10x-agent` — whatever project you run it in — or a comment on an issue there that already covers it. The report is public, so it never carries the current project's name, paths or code, and it **shows the draft and waits for the user's go** before anything is filed.

Run one command per Bash call — no `&&`, `;` or `|`. Before anything else:

```bash
10x-feedback init
```

A non-zero exit stops the skill: relay its message. Its lines are what the rest of this skill works from: `gh: ok`, `gh: missing` or `gh: logged-out`; `drafts: <path>`; one `form: <file> name: … labels: … title: … required: … fields: …` line per form of the 10x repository; `banned: […]`; the `new issue:`, `search:` and `security:` URLs; and, after `environment:`, seven lines that go into every draft verbatim.

## Step 1 — Classify

A bug — 10x does something other than its docs say — takes `bug.yml`; anything else takes `feature.yml`. It is a vulnerability when the user says so, or when the report describes a way to cross a security boundary: a worker escaping its sandbox, a grant allowing more than it names, a script writing outside the paths it is given, a secret reaching a public place.

Ask the user only for what the report needs and does not say — for a bug: what was run, what happened, what was expected. Ask in general terms; do not read the current project's files to fill it in.

## Step 2 — Look for an existing issue

Skipped for a vulnerability, so its key words are never sent as a search. Skipped when `gh:` is not `ok`: say so, and give the `search:` URL for the user to look themselves. Otherwise:

```bash
gh issue list --repo minanyang/10x-agent --state all --search "<key words>" --limit 10
```

The key words are general terms for the problem — a command, a skill, an error message — never the project's name or anything else from it. When an issue covers it, open or closed, show it (`gh issue view <n> --repo minanyang/10x-agent`) and ask whether to comment on it instead of opening a new one.

## Step 3 — Draft, check and stop

Write `<drafts>/<slug>.md`, `<drafts>` being `init`'s `drafts:` path (slug: lowercase letters, digits and `-`). Line 1 is `# <title>`; header lines follow directly, then a blank line and the body.

- A new issue: `Form: <file>` in the header and one `### <label>` section per entry of the form's `fields:`, in that order, every `required:` one filled. `Acceptance criteria` holds `- [ ] AC<n> — …` lines, one per line, with no phrase of the `banned:` line. `bug.yml`'s `Version / commit` is the `10x:` version of the environment lines.
- A comment: `Comment: <n>` in the header, and the comment's text as the body.
- A vulnerability: `Vulnerability: yes` as a header line too.

Either way the body ends with a last `### Environment` section holding the `environment:` lines verbatim. Describe the problem in general terms: no project name, file path, code, URL or data of the current project — say "a TypeScript project with two worktrees", not its name.

Then:

```bash
10x-feedback check <slug>
```

It refuses a draft whose header, form sections or Environment section are wrong, and lists every line that names the project's directory, its origin's owner or repo, or its absolute path. On a refusal, reword the draft and run it again — never show a draft `10x-feedback check <slug>` refused. Once it passes, show the draft once: its path on one line, then the file verbatim. **Stop** until the user approves or edits it.

## Step 4 — File it

On the user's go:

- A vulnerability files nothing. Give the `security:` URL — GitHub's private vulnerability reporting — and the draft's path, so the user can paste it there, and leave the draft where it is.
- `gh:` not `ok`: print the draft and the `new issue:` URL with `<form>` replaced by the form's file name (no other query parameter added), or for a comment the issue's URL, for the user to paste; run nothing. Name the fix: install `gh` (https://cli.github.com) or run `gh auth login`.
- Otherwise, a new issue:

  ```bash
  10x-feedback issue <slug>
  ```

  or a comment:

  ```bash
  10x-feedback comment <slug>
  ```

`10x-feedback issue <slug>` and `10x-feedback comment <slug>` are not in this skill's `allowed-tools` on purpose: they always ask for permission, so filing a public report never rests on the model stopping. They file on `minanyang/10x-agent` only, with the form's own labels, and delete the draft once `gh` succeeds; when `gh` fails the draft stays. Report the issue or comment URL `gh` prints.

## Replies

- Lead with the result. No first sentence that announces what comes next, and no closing recap or offer.
- Between routine tool calls, at most one line per phase change — a phase is one of this skill's numbered steps.
- Say each fact once: what the reply has already shown is not summarised again.

Some things are exempt from these rules and are written in full: a security warning; an irreversible action, both its warning and the statement made before acting on it; a question to the user; and anything persisted — issue bodies, comments and the files under `.10x/`.

The final reply is Step 4's: the URL, or for a vulnerability the `security:` URL and the draft's path.

## Never

- Never file an issue or a comment before the user has seen and approved the draft.
- Never put the current project's name, paths, code, URLs, secrets or data in a draft — the report is public.
- Never attach logs, transcripts or `.10x/` files.
- Never file to another repository than `minanyang/10x-agent`, and never open a public issue for a vulnerability.
- Never reply that something is unverified, unchecked or not yet confirmed: check it first. Only when a check is impossible, say so, naming what was tried and why it cannot be checked.

Versions

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

Database snapshot: 13.11.2026 · package version 26d4b442d55f (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

  • 90studio-feedback
    Prepare a user-reviewed Arch Studio bug report or feature request for GitHub. Use when the user runs /as:studio-feedback, says \"report a bug\", \"this skill broke\", \"send feedback\", or requests a feature. Do not use for Claude Code's native /feedback command.
  • 100create-github-issue
    Create GitHub issues using the gh CLI. Use when the user wants to create a new issue, report a bug, request a feature, or create a task in GitHub. Trigger keywords - create issue, new issue, file bug, report bug, feature request, github issue.
  • 84github-issue
    Use when opening a GitHub issue, bug report, feature request, or discussion in any repository, including one the user has no local checkout of.
  • 90feedback-intake
    Help the user file a bug report or feature request for Nimbalyst. Activates when the user opens the in-app feedback flow or runs /feedback:bug-report or /feedback:feature-request. Coordinates evidence gathering, anonymization, and posting to GitHub Issues.
  • 100prisma-next-feedback
    Hand a Prisma Next question or report off to the team — file a GitHub issue (bug or feature request), or route Q&A / design discussion / direct-team-contact to the Prisma Discord at pris.ly/discord. Use for bug, bug report, file an issue, report a bug, feature request, missing…
  • 96writing-issues
    Draft or revise an issue, bug report, or feature request with concrete impact, evidence, and observable acceptance criteria; use when preparing an issue for a tracker.

Feedback and reports

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