Skills personwise-product-change-adoption

📦

personwise-product-change-adoption

Name: personwise-product-change-adoption
Author: personwiseai

Content revision r1 High Risk 🌐 Network access⚙️ External commands📁 Filesystem access

Build Product Change Adoption Courses

Product changes often fail when users cannot understand their impact or required actions. This skill converts approved materials into a grounded, interactive adoption course.

Supports: Claude Codex Code(CC)

⚠️ 38 Poor

Stop for confirmation before installing.

Review the plan and obtain explicit user consent before changing files.

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "personwise-product-change-adoption" from https://skillstore.io/skills/personwiseai-personwise-product-change-adoption.md and its manifest at https://skillstore.io/api/skills/personwiseai-personwise-product-change-adoption/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/personwiseai-personwise-product-change-adoption.md Signed manifest GET /api/skills/personwiseai-personwise-product-change-adoption/manifest Signed lockfile GET /api/skills/personwiseai-personwise-product-change-adoption/lockfile

Test it

Using "personwise-product-change-adoption". Create a private course from release notes for a five-slide account.

Expected outcome:

A five-slide private course covering the change, affected users, migration steps, documented caveats, and support options.

Using "personwise-product-change-adoption". Build migration training from two selected documents.

Expected outcome:

Both selected documents are processed as grounded sources.
The course preserves documented dates, steps, and limitations.
The final response reports course status and the correct private viewing link.

Using "personwise-product-change-adoption". Publish the completed adoption course for link sharing.

Expected outcome:

The course is verified as playable, link access is enabled, and the returned share link is reported without exposing credentials.

Security Audit

High Risk

v1 • 8/5/2026 Open versioned report

All 142 static findings are false positives caused by verified installer operations, Markdown code formatting, local integrity checks, and signed descriptor data. Two semantic risks remain: selected documents can be uploaded to PersonWise without separate transfer confirmation, and course creation consumes an existing credit without transaction confirmation.

Files scanned

650

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (2)

High

SKILL.md:140-145 SKILL.md:199-207

Implicit Third-Party Document Upload

The skill treats named, attached, or selected documents as authorized for upload to PersonWise without separately disclosing that their contents leave the local environment.

The instructions explicitly pre-authorize selected files and direct source add uploads. No separate confirmation or sensitivity check is required before transfer.

Medium

SKILL.md:132-138 SKILL.md:169-171

Course Credits Consumed Without Transaction Confirmation

The skill interprets a course-creation request as authorization to consume existing course credits without a separate confirmation immediately before creation.

The authorization rule explicitly says not to ask again before consuming a credit. Purchases are prohibited, but a limited account entitlement is still consumed.

Risk Factors

🌐 Network access (2)

assets/bootstrap.ps1:43 assets/bootstrap.sh:132

⚙️ External commands (50)

📁 Filesystem access (7)

assets/bootstrap.sh:81 assets/bootstrap.sh:83 assets/bootstrap.sh:128 assets/bootstrap.sh:16 assets/bootstrap.sh:18 assets/bootstrap.sh:128 assets/bootstrap.sh:180

Audited by: codex

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/personwiseai-personwise-product-change-adoption/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/personwiseai-personwise-product-change-adoption/security.svg)](https://skillstore.io/skills/personwiseai-personwise-product-change-adoption?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/personwiseai-personwise-product-change-adoption?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/personwiseai-personwise-product-change-adoption/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/personwiseai-personwise-product-change-adoption.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

personwiseai. (2026). personwise-product-change-adoption security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/personwiseai-personwise-product-change-adoption/audits/1

BibTeX citation

@techreport{personwiseai-personwiseai-personwise-product-change-adoption-2026,
  author = {personwiseai},
  title = {personwise-product-change-adoption security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/personwiseai-personwise-product-change-adoption/audits/1},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "personwise-product-change-adoption security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "personwiseai"
date-released: "2026-08-05"
url: "https://skillstore.io/skills/personwiseai-personwise-product-change-adoption/audits/1"
identifiers:
  - type: other
    value: "skillstore:personwiseai-personwise-product-change-adoption:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Launch Feature Training

Convert approved release notes into an interactive course explaining benefits, affected users, and required actions.

Guide Customer Migrations

Create a source-grounded migration course with deadlines, ordered steps, caveats, and support routes.

Prepare Internal Enablement

Build role-specific training for a breaking change using supplied documentation and approved screenshots.

Try These Prompts

Create a Basic Adoption Course

Create a product change adoption course from the attached release notes. Keep all claims grounded in the source and use private access.

Build a Migration Guide

Build a migration course from these guides. Explain who is affected, required steps, deadlines, caveats, and the documented support channel.

Tailor Training by Audience

Create an adoption course for administrators and end users. Separate their impacts and actions while preserving every source constraint.

Review and Publish an Existing Course

Resume the existing course. Verify source status, review every checkpoint, correct unsupported statements, inspect available visuals, then enable link access after completion.

Best Practices

Provide current release notes, migration documentation, and approved screenshots.
State the intended audience, access mode, and desired course length.
Review deadlines, compatibility claims, and support routes before publication.

Avoid

Do not ask the skill to invent dates, compatibility promises, pricing, or migration outcomes.
Do not upload confidential documents without confirming third-party processing is permitted.
Do not treat a Topics submission as approval or a private editor link as publicly shareable.