Files
Chris Tate 7c2ff0a2a6 Move specialized skills to skill-data/ so npx skills add only finds one (#1227)
The skills CLI metadata.internal flag was never implemented (PRs #587
and #652 were both closed). All 6 skills were showing in the installer.

Move the 5 specialized skills (dogfood, electron, slack, vercel-sandbox,
agentcore) from skills/ to skill-data/, which the skills CLI does not
search. The bootstrap skill stays in skills/ for discovery. The Rust CLI
searches both directories so agent-browser skills list/get still serves
all 6.
2026-04-12 13:13:04 -05:00

54 lines
1.4 KiB
Markdown

# Dogfood Report: {APP_NAME}
| Field | Value |
|-------|-------|
| **Date** | {DATE} |
| **App URL** | {URL} |
| **Session** | {SESSION_NAME} |
| **Scope** | {SCOPE} |
## Summary
| Severity | Count |
|----------|-------|
| Critical | 0 |
| High | 0 |
| Medium | 0 |
| Low | 0 |
| **Total** | **0** |
## Issues
<!-- Copy this block for each issue found. Interactive issues need video + step-by-step screenshots. Static issues (typos, visual glitches) only need a single screenshot -- set Repro Video to N/A. -->
### ISSUE-001: {Short title}
| Field | Value |
|-------|-------|
| **Severity** | critical / high / medium / low |
| **Category** | visual / functional / ux / content / performance / console / accessibility |
| **URL** | {page URL where issue was found} |
| **Repro Video** | {path to video, or N/A for static issues} |
**Description**
{What is wrong, what was expected, and what actually happened.}
**Repro Steps**
<!-- Each step has a screenshot. A reader should be able to follow along visually. -->
1. Navigate to {URL}
![Step 1](screenshots/issue-001-step-1.png)
2. {Action -- e.g., click "Settings" in the sidebar}
![Step 2](screenshots/issue-001-step-2.png)
3. {Action -- e.g., type "test" in the search field and press Enter}
![Step 3](screenshots/issue-001-step-3.png)
4. **Observe:** {what goes wrong -- e.g., the page shows a blank white screen instead of search results}
![Result](screenshots/issue-001-result.png)
---