Skip to content
skillsafebeta
← Report library
Purpose / Other

Persona Customer Support Skill Security Audit

What the author says it does (original text)

Manage customer support — track tickets, respond, escalate issues.

Independent security check

Security risks found

Files checked
1
Risks found
3
Could it run dangerous commands?Looks for programs run straight after downloading, remote control of your computer, and hidden commands.No risks found
Could it expose your files or keys?Looks for uploads of files containing passwords or keys, and keys written directly in the code.Risks found: 1
Medium risk

Customer email or ticket data may be copied into unspecified shared destinations

Source references: 1
What we found

The Skill converts customer emails into tasks, appends status to a tracking sheet, and posts urgent issues to “the team Chat space,” but identifies none of those destinations and requires no restriction of sensitive fields before transfer.

Why this matters

If a destination is selected incorrectly or shared too broadly, unrelated people in the organization could see customer names, message content, contact details, or issue descriptions.

These are live operational instructions: customer emails are converted into tasks, status is written to a tracking sheet, and urgent issues are sent to a team Chat space. The source does not identify the task destination, sheet, or Chat space, or define which sensitive customer fields must be excluded. Execution could therefore disclose ticket data to an overly broad or incorrect shared destination. Users can require explicit destinations, an allowed-field list, and confirmation of the target and content before the first write or send.

SKILL.md:30In the instructionsOpen original file
- Triage the support inbox with `gws gmail +triage --query 'label:support'`.- Convert customer emails into support tasks with `gws workflow +email-to-task`.- Log ticket status updates in a tracking sheet with `gws sheets +append`.- Escalate urgent issues to the team Chat space.- Schedule follow-up calls with customers using `gws calendar +insert`.
Could it delete files or keep running?Looks for broad file deletion, disk overwrites, and programs set to start automatically.No risks found
Could it bypass safety checks?Looks for skipped website security checks, excessive file access, or actions that skip your approval.Risks found: 1
Medium risk

The suggested Gmail filters would persistently change email handling

Source references: 2
What we found

The tips recommend Gmail filters that automatically label support requests, without specifying matching rules, exclusions, testing, or confirmation. A filter is a persistent account configuration, not merely an email view.

Why this matters

An overly broad or incorrect rule could continually misclassify customer mail, causing important requests to disappear from the expected workflow or receive the wrong handling.

This appears under “Tips,” so it is advice rather than a mandatory workflow step. Even so, setting Gmail filters is a persistent account configuration change that can automatically reclassify future mail. No matching criteria, exclusions, test, or confirmation requirement is given; an overly broad rule could mislabel support messages and affect handling decisions. Users can require a draft-only filter, a preview of matched mail, and confirmation of the rule and scope before activation.

SKILL.md:37In the instructionsOpen original file
- Use `gws gmail +triage --labels` to see email categories at a glance.- Set up Gmail filters for auto-labeling support requests.- Use `--format table` for quick status dashboard views.
Show 1 other places
SKILL.md:35In the instructionsOpen original file
## Tips- Use `gws gmail +triage --labels` to see email categories at a glance.- Set up Gmail filters for auto-labeling support requests.- Use `--format table` for quick status dashboard views.
Could it mislead the AI or hide text?Checks the skill instructions for requests to ignore you, influence the report, or hide text in invisible characters.No risks found
Could it change links or payment recipients without asking?Looks for forced referral or payment changes combined with instructions to hide the change.Risks found: 1
Medium risk

The Skill can create customer follow-up events without a confirmation step

Source references: 1
What we found

The instructions directly call for `gws calendar +insert`, but do not define the calendar, attendees, time, timezone, or human approval before invitations are sent.

Why this matters

A wrong customer, time, or calendar could produce an inappropriate invitation, expose attendee information, occupy staff schedules, or create an incorrect customer-service commitment.

The instruction explicitly calls for creating customer follow-up calls through Google Calendar, which changes a calendar and may notify customers or other invitees. Scheduling is consistent with customer support, but the source does not specify the calendar, attendees, time, timezone, or a pre-send confirmation condition. This could produce an incorrect booking or unintended notification. Users can restrict it to drafting and require confirmation of those fields before event creation or invitation delivery.

SKILL.md:33In the instructionsOpen original file
- Escalate urgent issues to the team Chat space.- Schedule follow-up calls with customers using `gws calendar +insert`.

Inside this skill

3 instruction sections

The Skill depends on Google Workspace access to Gmail, Sheets, Chat, and Calendar, and operates those services through `gws` commands.

View source
SKILL.md:8In the instructionsOpen original file
    category: "persona"    requires:      bins:        - gws      skills:        - gws-gmail        - gws-sheets        - gws-chat        - gws-calendar---

Its workflow triages support email, converts messages into tasks, and writes ticket status updates to a tracking sheet.

View source
SKILL.md:29In the instructionsOpen original file
## Instructions- Triage the support inbox with `gws gmail +triage --query 'label:support'`.- Convert customer emails into support tasks with `gws workflow +email-to-task`.- Log ticket status updates in a tracking sheet with `gws sheets +append`.- Escalate urgent issues to the team Chat space.

The workflow also escalates urgent issues to a team Chat space and creates calendar events for customer follow-up calls.

View source
SKILL.md:32In the instructionsOpen original file
- Log ticket status updates in a tracking sheet with `gws sheets +append`.- Escalate urgent issues to the team Chat space.- Schedule follow-up calls with customers using `gws calendar +insert`.
Start here · InstructionsSKILL.md
persona-customer-support
Lines connect the instruction file to its sections, not an observed execution order. Select a section to read the source.
Files and check records1 files

Coverage and gaps

Content covered in each file

These are the source ranges included in this check, not a guarantee that every issue has been resolved.

  • SKILL.mdFull text included

This report is for the version above. We read the available code and instructions without running the skill or checking extra packages it installs. This is not a promise of safety: a different version or setup may behave differently.

  • SKILL.mdInstructions

Operations mentioned in code and instructions

Connect to websites
SKILL.md:37In the instructionsOpen original file
- Use `gws gmail +triage --labels` to see email categories at a glance.- Set up Gmail filters for auto-labeling support requests.- Use `--format table` for quick status dashboard views.
Lines read
40
File checksum (to compare versions)
2444666943fa3f4774a974c0f8ce2a18fcaacb5d7815ec9b465b547dbbd3a93a