Skills personwise-internal-change-adoption

📦

personwise-internal-change-adoption

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

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

Build Internal Change Adoption Courses

Internal change communications often leave employees uncertain about timelines, responsibilities, and support. This skill converts approved materials into an interactive, grounded 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-internal-change-adoption" from https://skillstore.io/skills/personwiseai-personwise-internal-change-adoption.md and its manifest at https://skillstore.io/api/skills/personwiseai-personwise-internal-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-internal-change-adoption.md Signed manifest GET /api/skills/personwiseai-personwise-internal-change-adoption/manifest Signed lockfile GET /api/skills/personwiseai-personwise-internal-change-adoption/lockfile

Test it

Using "personwise-internal-change-adoption". Create a private course from our approved reorganization memo for all affected employees.

Expected outcome:

A concise course explains the approved reason for the reorganization and separates confirmed role impacts from open decisions.
A timeline shows communicated milestones, employee actions, and named support channels.
The final result includes a private, login-required course link and verified run status.

Using "personwise-internal-change-adoption". Build a five-page adoption course for our new expense process using only the attached policy.

Expected outcome:

Five pages cover the process purpose, changed steps, employee responsibilities, timing, support, and a short self-check.
Unsupported exceptions are excluded, and unclear policy points are marked for the finance team.

Using "personwise-internal-change-adoption". Update our existing rollout course and share it with anyone who has the link.

Expected outcome:

The course is reviewed against current sources, updated with supported corrections, published with link access, and returned with a verified playable URL.

Security Audit

High Risk

v1 • 8/5/2026 Open versioned report

The 142 static alerts are false positives from Markdown formatting, signed descriptor data, and defensive installer operations. However, native publisher signature checks are disabled for macOS and Windows binaries, creating a high-severity supply-chain risk.

Files scanned

650

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (1)

High

assets/bootstrap.sh:54-66 assets/bootstrap.ps1:10-12 assets/bootstrap.ps1:85-88

Native Publisher Signature Enforcement Disabled

The macOS and Windows installers accept releases marked deferred-founder-approved while native signature checks remain disabled. They can install opaque binaries without platform publisher verification.

The scripts explicitly set native signature requirements to false and gate verification on a status that is not verified. SHA-256 pinning does not establish publisher identity.

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-internal-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-internal-change-adoption/security.svg)](https://skillstore.io/skills/personwiseai-personwise-internal-change-adoption?utm_source=security_passport_badge)

HTML badge

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

Embed card

<iframe src="https://skillstore.io/embed/skills/personwiseai-personwise-internal-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-internal-change-adoption security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/personwiseai-personwise-internal-change-adoption/audits/1

BibTeX citation

@techreport{personwiseai-personwiseai-personwise-internal-change-adoption-2026,
  author = {personwiseai},
  title = {personwise-internal-change-adoption security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/personwiseai-personwise-internal-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-internal-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-internal-change-adoption/audits/1"
identifiers:
  - type: other
    value: "skillstore:personwiseai-personwise-internal-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

Prepare Employees for a Reorganization

Convert approved leadership communications into a private course explaining reasons, role impacts, timing, and support channels.

Train Teams on a New Process

Create a source-grounded course that shows changed responsibilities, expected actions, and escalation paths for each affected team.

Support an Internal Software Rollout

Build an interactive rollout course covering the implementation timeline, employee tasks, training resources, and approved answers to common questions.

Try These Prompts

Create a Basic Adoption Course

Create a private internal change adoption course from [source materials]. Explain why the change is happening, what employees must do, and where support is available.

Tailor Training by Role

Build a [page count]-page adoption course for [audience]. Separate impacts for [roles] and include the approved timeline, support channels, and a short knowledge check.

Create a Materials-Only Rollout Course

Use only the attached rollout documents to create a private course. Flag unsupported or conflicting claims, preserve every source, and route open questions to [channel].

Resume and Publish a Reviewed Course

Resume PersonWise run [run ID]. Review the latest outline, script, and images against the approved sources. Fix objective issues, complete the run, then enable [access mode].

Best Practices

Provide final, approved communications and identify the affected audiences before course creation.
State the desired page count, language, and access mode, or accept the private default.
Review flagged ambiguities and route employee-specific questions to an authorized manager, HR contact, or change team.

Avoid

Do not request assurances about layoffs, roles, dates, or outcomes that approved sources do not support.
Do not upload files that the user did not select without disclosing the exact file and obtaining approval.
Do not describe private editor links as public share links or claim Topics submission means approval.