Skip to content
Skills Library
Sales & customer service · Writing

report-problem

/report-problem

Report a wrong result (a false alarm, a missed problem, or a confusing message) so it gets fixed and added to the test suite. Use when someone says "that's wrong", "false positive", "it missed this", "report a bug" or "send feedback" about crm-lifecycle-ops.

Licence
MIT
Last repository change
09.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
2
Deprecation

No signals detected. Repository changed on 09.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 wrong result (a false alarm, a missed problem, or a confusing message) so it gets fixed and added to the test suite. Use when someone says "that's wrong", "false positive", "it missed this", "report a bug" or "send feedback" about crm-lifecycle-ops.

Triggers from the description

thatfalse positiveit missed thisreport a bugsend feedback

Arguments

/report-problem [what was wrong]
Original author description

Report a wrong result (a false alarm, a missed problem, or a confusing message) so it gets fixed and added to the test suite. Use when someone says "that's wrong", "false positive", "it missed this", "report a bug" or "send feedback" about crm-lifecycle-ops.

How it works

  1. 1. Pin down what happened
  2. 2. Strip anything private (do this yourself, then show the person)
  3. 3. Show the draft and ask
  4. 4. Post it
Original SKILL.md headings · 49 lines, 326 words
SKILL.md preview
---
name: report-problem
description: Report a wrong result (a false alarm, a missed problem, or a confusing message) so it gets fixed and added to the test suite. Use when someone says "that's wrong", "false positive", "it missed this", "report a bug" or "send feedback" about crm-lifecycle-ops.
argument-hint: "[what was wrong]"
---

# Report a problem

Turn "that result was wrong" into a GitHub issue the maintainers can reproduce. Every confirmed
report becomes a regression test, so the same mistake can't come back.

## 1. Pin down what happened
Work it out from the conversation where you can; ask only for what's missing:
- **Type:** false alarm (flagged something fine) · missed problem (didn't flag something wrong) ·
  confusing message · crash/error · something else
- **Check id** if it's about a finding (e.g. `links.utm-inconsistent`). The `list_checks` tool has them all.
- **Expected vs. actual**, in one sentence each
- **Platform:** braze / klaviyo / iterable
- **The smallest snippet that shows it**: a few lines of template, not the whole email

## 2. Strip anything private (do this yourself, then show the person)
Replace real names, emails, phone numbers, customer or account IDs, API keys, internal URLs and real
company domains with placeholders (`Ana`, `ana@example.com`, `https://brand.example/...`). Keep the
template *syntax* exactly as it was; that's what reproduces the bug.

## 3. Show the draft and ask
Show the exact title and body that would be posted, then ask: **"Post this as a public GitHub issue?"**
Do not post without a clear yes. The repository is public.

Title format: `[wrong-result] <check id or area>: <one-line summary>`

Body:
```
**Type:** …
**Check id:** …
**Platform:** …
**Plugin version:** <version from the list_checks tool>
**Expected:** …
**Actual:** …

**Snippet (private details removed):**
<snippet in a code block>
```

## 4. Post it
- If `gh` is installed and signed in (`gh auth status`): write the body to a temp file and run
  `gh issue create --repo har5h98/crm-lifecycle-ops --title "<title>" --body-file <file> --label wrong-result`.
  If the label is rejected, retry without `--label`.
- Otherwise give them this link and the body to paste:
  https://github.com/har5h98/crm-lifecycle-ops/issues/new?template=wrong-result.yml
  (Don't put the body in the URL.)

Reply with the issue link and one line on what happens next: it becomes a test case, then gets fixed.

Versions

RepositoryScoreLicence
This page · har5h98/crm-lifecycle-ops100MIT
easeit-cz/vornik100AGPL-3.0
easeit-cz/vornik100AGPL-3.0

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

  • 90feedback
    Report a PandaWard false positive or a missed issue (false negative) to the PandaWard project, so its rules can be fixed. Use when the user says a finding is wrong, noisy or that PandaWard missed something.
  • 86start-here
    Overview of crm-lifecycle-ops. What each command does, what works today, and the best first step. Use when someone asks what crm-lifecycle-ops can do, how to use it, or which of its commands to run.
  • 100made-it-wrong-retro
    Retro on a `make-it-right` run: finds where it missed a problem, kept a false alarm, made a bad fix, or skipped a step, proves each lesson with a failing replay at the lowest level that shows it, and proposes the edit to make-it-right. Also prunes rules that never fire. Use when…
  • 86ops-report
    Report on how the crm-lifecycle-ops QA tools are being used and what they caught, for one operator or the whole team. Messages checked, blocking problems caught, most common issues, weekly trend and estimated hours saved. Use when someone asks "what has this caught", "how much…
  • 90fp-check
    Systematically verifies suspected security bugs to eliminate false positives, producing a TRUE POSITIVE or FALSE POSITIVE verdict with documented evidence for each. Use when asked whether a specific finding is real, exploitable, or a false positive, or to verify or validate a…
  • 90broadcasts
    This skill should be used when the user asks to send a message, announcement or reminder to members, a segment, a plan's members, pass holders or people whose access is expiring, to preview who a broadcast reaches, to read a broadcast's history or who it missed, or to retry or resend one.

Feedback and reports

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