Skills personwise-community-onboarding

📦

personwise-community-onboarding

Name: personwise-community-onboarding
Author: personwiseai

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

Build an Interactive Community Onboarding Course

Community guidelines often fail to give new members a clear starting path. This skill turns supplied materials into an interactive, askable PersonWise course.

Supports: Claude Codex Code(CC)

📊 64 Adequate

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-community-onboarding" from https://skillstore.io/skills/personwiseai-personwise-community-onboarding.md and its manifest at https://skillstore.io/api/skills/personwiseai-personwise-community-onboarding/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

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-community-onboarding.md Signed manifest GET /api/skills/personwiseai-personwise-community-onboarding/manifest Signed lockfile GET /api/skills/personwiseai-personwise-community-onboarding/lockfile

Test it

Using "personwise-community-onboarding". Create a private five-page onboarding course from our handbook and welcome guide.

Expected outcome:

Resolved course: five pages with private access.
Sources: handbook ready; welcome guide ready.
Review: outline, script, and factual grounding completed.
Delivery: login-required course link verified as playable.

Using "personwise-community-onboarding". Create a link-access course that explains our spaces, weekly events, and conduct rules.

Expected outcome:

Course arc: welcome, first actions, community spaces, weekly events, and conduct rules.
Grounding: all claims matched the supplied materials.
Access: link sharing enabled and the playable URL verified.

Using "personwise-community-onboarding". Update the existing course after our moderation contacts changed.

Expected outcome:

The support contacts were updated from the new policy document. Course structure stayed unchanged, and the private course was verified.

Security Audit

Medium Risk

v1 • 8/5/2026 Open versioned report

The scanner mistook Markdown backticks, fixed integrity commands, and signed descriptor data for execution or obfuscation. The workflow still installs vendor-native code with an automatic approval flag, while platform publisher signatures are not enforced.

Files scanned

649

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (2)

Medium

SKILL.md:74-79

Native CLI Install Uses an Automatic Approval Flag

The workflow directs the agent to pass --approve-install when the CLI is missing. Host policy may confirm, but the script receives its approval flag automatically.

The instruction explicitly supplies the approval flag and says not to add separate PersonWise approval. It still delegates installation permission to host policy.

Medium

assets/bootstrap.sh:50-68 assets/bootstrap.ps1:10-13 assets/bootstrap.ps1:83-88

Native Publisher Signatures Are Not Enforced

The installers accept deferred native signatures and rely on hashes embedded in the same skill release. This lacks independent publisher verification for downloaded executable code.

Both installers set native signature enforcement to false or deferred. Their signature checks cannot run for the bundled release settings.

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

HTML badge

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

Embed card

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

BibTeX citation

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

Welcome New Community Members

Create a start-here course that explains purpose, first-week actions, spaces, rituals, rules, and support contacts.

Onboard Paid Members

Turn membership guides into a private course without inventing benefits, tiers, or access promises.

Standardize Program Introductions

Build a repeatable interactive orientation from approved program documents, branding, and event imagery.

Try These Prompts

Create a Basic Onboarding Course

Create a community onboarding course from [source files]. Keep it private and use only supported facts.

Plan the First Member Week

Build a [page count]-page course for [community name]. Focus on first-week actions, spaces, norms, and support contacts from [sources].

Use Strict Source Grounding

Create a materials-only onboarding course from [documents]. Include every selected source and flag any unsupported claim before publication.

Refine and Publish an Existing Course

Review project [project ID] against [sources]. Correct factual issues, inspect visuals, preserve structure, and publish with [private or link] access.

Best Practices

Supply current guidelines, welcome materials, contact details, and approved branding before course creation.
State the desired page count and access mode, or accept the private default.
Review factual checkpoints and resolve unsupported claims before publishing or sharing.

Avoid

Do not ask the skill to invent benefits, rules, testimonials, member counts, or access tiers.
Do not upload agent-discovered local files without reviewing the exact path and purpose.
Do not treat a private editor URL as a public share link.