Skill adoption feedback
Skill onyx679/automotive-ve-ai-skills-kit/skills/skill-adoption-feedback
AI Skill templates and workflow scoring tools for automotive value engineering and VAVE productivity scenarios
npx -y skills add onyx679/automotive-ve-ai-skills-kit --skill skill-adoption-feedbackAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Track AI Skill usage, user feedback, productivity impact, quality issues, and iteration priorities for internal business-process Skills. Use after piloting Claude Code, Codex, OpenCode, or similar agent Skills with business teams.
SKILL.md
1.8 KB, as published. Nobody here has run it
Skill Adoption Feedback
Use this skill to turn scattered user feedback into an iteration plan and measurable adoption report.
Inputs
- Usage logs or manual usage counts.
- User feedback forms.
- Interview notes.
- Before/after task-time samples.
- Examples of good and bad Skill outputs.
- Version history.
Workflow
- Segment feedback by user role and scenario.
- Measure adoption:
- Active users.
- Usage count.
- Repeat usage.
- Task coverage.
- Measure productivity:
- Baseline time.
- Skill-assisted time.
- Rework count.
- Output completeness.
- Classify problems:
- Trigger unclear.
- Input hard to prepare.
- Output format wrong.
- Domain rule missing.
- Hallucination or unsupported conclusion.
- Permission or data-boundary issue.
- Prioritize iterations by impact, frequency, risk, and effort.
- Produce a version plan.
Output
# Skill Adoption Report
## Executive Summary
## Adoption Metrics
| Metric | Current | Baseline/Target | Trend | Notes |
|---|---:|---:|---|---|
## Feedback Themes
| Theme | User Role | Frequency | Example | Root Cause |
|---|---|---:|---|---|
## Quality Issues
| Issue | Severity | Evidence | Fix |
|---|---|---|---|
## Iteration Backlog
| Priority | Change | Expected Impact | Effort | Owner |
|---|---|---|---|---|
## Next Pilot Plan
Quality Checks
- Do not treat usage count alone as success.
- Always include output quality and user trust.
- Separate product issues from training issues.
- Keep sensitive examples redacted.