check-feedback SKILL.md skillA
check-feedback from aitit-inc/leadace is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add aitit-inc/leadace/check-feedback@git:20260831.9e3776bPins git:20260831.9e3776b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- aitit-inc/leadace
- Path
plugin/skills/check-feedback/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260831.9e3776b, committed Aug 31, 2026
- First version recorded
- May 28, 2026
- Size
- 4,730 bytes
- Repository stars
- 3
- License
- a license file GitHub does not identify
Surface PMF signals from rejection feedback: feature_gap notes and competitor presence (already_have_solution / competitor_locked). Read-only product reflection, not sales tactics. Triggers: "check feedback", "PMF signals".
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Check Feedback - PMF Signals from Rejection Feedback
A read-only skill that surfaces **product/pricing/business-model** signals from rejection feedback recorded by `/check-responses`. Use this for PMF reflection — questions like "is there a missing feature people keep asking for?" or "are we losing to a specific competitor?".
This skill is **not** for sales tactics. Tactical signals from rejections (when to recontact, who to redirect to, which industries to deprioritize) are consumed automatically by `/evaluate` in the daily cycle. Do not use `/check-feedback` to drive operational decisions.
**Before starting:** `Read` `${CLAUDE_PLUGIN_ROOT}/references/workspace-conventions.md` and follow the cross-cutting conventions there (data storage, MCP error handling, document writes, output discipline).
## Steps
### 1. Verify Arguments
- Project ID: `$0` (required)
Return an error if `$0` is empty.
### 2. Fetch Two Windows in Parallel
Call `get_rejection_feedback_summary` twice in parallel, both with `scope: "pmf"`:
1. `projectId: "$0"`, `windowDays: 30`, `scope: "pmf"` -> recent
2. `projectId: "$0"`, `scope: "pmf"` (no `windowDays`) -> all-time
…Read the whole file at its exact version.
How to install
mdr add aitit-inc/leadace/check-feedback@sha256:0fb67c6bd0ec1fcaThe line at the top of this page pins the label git:20260831.9e3776b, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_bukaywntvfdpqrhd)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between May 28, 2026 and Aug 31, 2026, about one every 24 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260831.9e3776b latest | 2026-08-31 | 9e3776b | 4,730 B | A | view · diff |
| git:20260829.ab41dc3 | 2026-08-29 | ab41dc3 | 4,759 B | A | view · diff |
| git:20260604.2716545 | 2026-06-04 | 2716545 | 4,751 B | A | view · diff |
| git:20260531.a951898 | 2026-05-31 | a951898 | 4,749 B | A | view · diff |
| git:20260528.1af8f71 | 2026-05-28 | 1af8f71 | 4,701 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4730 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
aitit-inc/leadace · 3 stars · license a license file GitHub does not identify · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_bukaywntvfdpqrhd GET https://markdownregistry.com/api/v1/resolve?ref=aitit-inc/leadace/check-feedback GET https://markdownregistry.com/api/v1/blob/0fb67c6bd0ec1fca90d7fb006614576c964b86c17348a826661b3bddaa7cbcf5
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.