Run any Skill in Manus with one click

team-shinchan-skill-feedback

Stars8

Forks2

UpdatedJune 19, 2026 at 23:43

Use when the user wants to review accumulated skill feedback, verdict trends, or improvement candidates collected during Stage 4 retrospectives. Trigger on "show skill feedback", "스킬 피드백 보여줘", or finding which skills need /writing-skills work.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

seokan-jeong

seokan-jeong/team-shinchan

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

SKILL.md

readonly

name	team-shinchan:skill-feedback
description	Use when the user wants to review accumulated skill feedback, verdict trends, or improvement candidates collected during Stage 4 retrospectives. Trigger on "show skill feedback", "스킬 피드백 보여줘", or finding which skills need /writing-skills work.
user-invocable	true

EXECUTE IMMEDIATELY

Steps

Read the global ledger ~/.shinchan/skill-feedback.jsonl — skill feedback is global because team-shinchan SKILLS are global plugin code, so it aggregates ACROSS every project. Also read the legacy per-project .shinchan-docs/skill-feedback.jsonl if it exists (pre-v4.50 data) and merge the entries.
If neither exists, report "No skill feedback collected yet. Feedback is gathered during Stage 4 retrospectives."
Group entries by skill name (across projects).
For each skill, show:
- Total invocations assessed + which projects contributed (from each entry's project field)
- Verdict distribution (yes/partial/no)
- Top suggestions (sorted by recency)
Highlight skills with 3+ negative verdicts (counted across all projects) as candidates for /team-shinchan:writing-skills
Output as a formatted table. If the user asks about one project only, filter entries by the project field first.

More from this repository

same repository

team-shinchan-bigproject

seokan-jeong/team-shinchan

Use when you have a large-scale, multi-phase project requiring orchestrated execution.

2026-06-238

team-shinchan-ralph

seokan-jeong/team-shinchan

Use when you need persistent looping until a task is fully complete.

2026-06-238

team-shinchan-fierce-review

seokan-jeong/team-shinchan

Deterministic adversarial code review for high-stakes scope — independent per-dimension review, a non-skippable per-finding refutation, completeness + interaction critics, and a deterministic 3-lens rubric judge panel. Opt-in main-loop Workflow tier.

2026-06-238

team-shinchan-fierce-compete

seokan-jeong/team-shinchan

Deterministic competitive code tournament — N builders independently solve one task and return patches, an Action-Kamen judge scores them head-to-head, the winner is picked by score and applied. Opt-in main-loop Workflow tier.

2026-06-198

team-shinchan-fierce-debate

seokan-jeong/team-shinchan

Deterministic adversarial debate for high-stakes or irreversible decisions — mandatory refutation plus a scored judge panel. Opt-in main-loop Workflow tier.

2026-06-198

team-shinchan-fierce-option-panel

seokan-jeong/team-shinchan

Default-on interview option-quality panel — N diverse generators produce structure-free options, a SelfCheckGPT majority-vote consensus filters hallucinations, a SteerConf cautious-confidence judge scores survivors, and a deterministic top-K is returned. Workflow tier; the single fierce-* skill that is ON by default.

2026-06-198

name	team-shinchan:skill-feedback
description	Use when the user wants to review accumulated skill feedback, verdict trends, or improvement candidates collected during Stage 4 retrospectives. Trigger on "show skill feedback", "스킬 피드백 보여줘", or finding which skills need /writing-skills work.
user-invocable	true

EXECUTE IMMEDIATELY

Steps

Read the global ledger ~/.shinchan/skill-feedback.jsonl — skill feedback is global because team-shinchan SKILLS are global plugin code, so it aggregates ACROSS every project. Also read the legacy per-project .shinchan-docs/skill-feedback.jsonl if it exists (pre-v4.50 data) and merge the entries.
If neither exists, report "No skill feedback collected yet. Feedback is gathered during Stage 4 retrospectives."
Group entries by skill name (across projects).
For each skill, show:
- Total invocations assessed + which projects contributed (from each entry's project field)
- Verdict distribution (yes/partial/no)
- Top suggestions (sorted by recency)
Highlight skills with 3+ negative verdicts (counted across all projects) as candidates for /team-shinchan:writing-skills
Output as a formatted table. If the user asks about one project only, filter entries by the project field first.