pa-enablement-orchestrator — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited pa-enablement-orchestrator (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Coordinates customer enablement -- training sessions, learning paths, certification tracking, and content recommendation. Part of the Product Adoption & Value Realisation pillar. Bridges the gap between "the customer has access to the product" and "the customer's team knows how to use it effectively."
This is a coordination and recommendation skill. It schedules, tracks, and surfaces relevant resources. The actual training delivery -- leading sessions, answering questions, coaching on best practices -- is human work (CSM, enablement specialist, or customer education team).
Determine what enablement is needed and why:
| Trigger Source | Need Type | Assessment |
|---|---|---|
| New customer onboarding | Foundational training | Standard for all new accounts. Tier and segment determine depth |
| Adoption gap (untouched feature, high relevance) | Feature-specific training | Customer has access but is not using it. Likely a knowledge or awareness gap |
| Adoption gap (abandoned feature) | Re-training or investigation | Customer tried it and stopped. May be a knowledge gap, a product friction issue, or a personnel change (the trained user left). Investigate before prescribing training |
| New team onboarding | Team-specific training | Existing customer adding a new team. They need targeted onboarding, not the full programme |
| Product release | Feature update training | New capabilities released. Relevant customers need to know what changed and how to use it |
| Personnel change | Knowledge transfer | Key user left. Their replacement needs training. The need is urgent because institutional knowledge is leaving |
Match each need to available resources from the enablement catalogue (see references/enablement-resources.md):
| Need Type | Preferred Resource | Delivery Method | Fallback if Resource Does Not Exist |
|---|---|---|---|
| Foundational product training | Self-serve learning path | LMS or help centre | Live kickoff session with CSM or enablement specialist |
| Feature-specific training | Recorded webinar or guided tutorial | Video library or in-app guidance | Live demo in the next check-in call |
| Use-case deep dive | Live training session | Scheduled call with CSM or specialist | Tailored documentation + async support |
| New feature rollout | Release notes + guided walkthrough | Email with in-app guidance | Mention in next touchpoint with offer to demo |
| Advanced configuration | Technical workshop | Scheduled session with technical resource | Documentation + async technical support |
| Certification | Structured programme with assessment | LMS with certification tracking | Manual tracking by CSM until LMS is available |
| Knowledge transfer (personnel change) | Abbreviated onboarding path | Condensed version of the foundational path, focused on the departing user's workflows | 1:1 training session with CSM |
For each account with identified enablement needs, create a structured plan:
{
"account_id": "string",
"enablement_plan": {
"created": "2026-03-10",
"status": "active",
"items": [
{
"id": "EN-2026-0042",
"topic": "Advanced Reporting",
"need_source": "adoption_gap",
"need_detail": "Feature untouched. 78% of segment peers use it. Aligns with customer goal: reduce manual reporting time",
"resource_type": "live_training",
"resource": "Advanced Reporting demo session",
"assigned_to": "Jane Doe (CSM)",
"target_audience": "Analytics team (3 power users)",
"target_date": "2026-03-25",
"completion_criteria": "Attendees can create custom reports independently within 7 days",
"status": "scheduled",
"follow_up": "Check pa-adoption-tracker 30 days post-session to verify feature adoption"
},
{
"id": "EN-2026-0043",
"topic": "API Integration Best Practices",
"need_source": "new_team_onboarding",
"need_detail": "12 new engineers joining. Need API onboarding before Q2 integration project",
"resource_type": "self_serve_path",
"resource": "API Developer Learning Path (6 modules, ~2 hours)",
"assigned_to": "customer_self_serve",
"target_audience": "Engineering team (12 new users)",
"target_date": "2026-04-01",
"completion_criteria": "80% of engineers complete all 6 modules",
"status": "resources_sent",
"follow_up": "Check LMS completion rates at target date. Follow up individually with non-completers if <80%"
}
],
"overall_progress": {
"total_items": 2,
"completed": 0,
"in_progress": 2,
"blocked": 0
}
}
}For live training sessions:
For self-serve paths:
After enablement delivery, measure:
| Metric | Source | Success Criteria |
|---|---|---|
| Completion rate | LMS or manual tracking | >80% of target audience completed the programme |
| Adoption change | pa-adoption-tracker | Feature moved from untouched/explored to partially adopted or core adopted within 60 days |
| Usage lift | bi-usage-monitor | Measurable increase in feature usage after enablement |
| Customer satisfaction | Post-training survey or CSM feedback | Positive feedback on relevance and quality |
| Time-to-competence | Product analytics | Time from training completion to independent feature usage |
Feed outcomes back into the enablement plan:
| Decision Point | Context Provided | What the Human Decides |
|---|---|---|
| Enablement plan approval | Adoption gaps, available resources, customer context | Which gaps to address, in what order, and with what approach. The plan is a recommendation; the CSM decides what fits the relationship |
| Live training delivery | Session outline, attendee list, pre-materials | How to run the session -- what to emphasise, how to adapt to the audience, how to make it valuable beyond just product training |
| Root cause diagnosis | Adoption gap that persists post-enablement | Whether the issue is knowledge (more training), motivation (change management), or product (feature gap). This distinction determines the next intervention |
| Resource creation request | Gap identified with no existing resource | Whether to escalate to the enablement or content team for new resource creation, address through 1:1 coaching, or accept the gap |
| Customer communication | Enablement recommendations, available resources | How to position enablement with the customer. "Training" can feel condescending if positioned poorly. "Helping your team get more value from features you are already paying for" is better framing |
Required:
Strongly recommended:
Downstream consumers:
references/enablement-resources.md -- Resource catalogue structure, matching logic, and maintenance process~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.