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

1. Segment feedback by user role and scenario.
2. Measure adoption:

• Active users.
• Usage count.
• Repeat usage.
• Task coverage.

1. Measure productivity:

• Baseline time.
• Skill-assisted time.
• Rework count.
• Output completeness.

1. Classify problems:

• Trigger unclear.
• Input hard to prepare.
• Output format wrong.
• Domain rule missing.
• Hallucination or unsupported conclusion.
• Permission or data-boundary issue.

1. Prioritize iterations by impact, frequency, risk, and effort.
2. 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.