T09 · Insecure Skill Coding Practices
- Location
assets/requirements-template.md:11- Finding
Plaintext Collection of Excessive Multigenerational Personal Data
- Content
View full analysis
Vulnerability Details
File Location:
assets/requirements-template.md, lines 11–67
Vulnerability Type: Plaintext sensitive-data handling without minimization, retention, or storage safeguards
Risk Level: MediumVulnerable Code Snippet
The following is an English rendering of the affected template fields:
markdown ## 1. Basic Information - **Father's full name**: - **Mother's full name**: - **Surname**: - **Gender**: - **Birth time**: Gregorian calendar, including the exact hour and minute - **Birthplace**: Province, city, and district ## 3. Parents' Bazi Information (Optional) ### Father - **Birth time**: Gregorian calendar, including the exact hour and minute - **Birthplace**: - **Bazi**: - **Day master**: - **Favorable and unfavorable elements**: ### Mother - **Birth time**: Gregorian calendar, including the exact hour and minute - **Birthplace**: - **Bazi**: - **Day master**: - **Favorable and unfavorable elements**: ## 4. Names of Senior Family Members - **Paternal grandfather**: - **Paternal grandmother**: - **Maternal grandfather**: - **Maternal grandmother**: - **Other senior family members whose names must be avoided**: - **Characters that must be avoided**: - **Homophones requiring caution**:Technical Analysis
The template instructs users to copy a Markdown document and enter full parental names, exact birth times, detailed birth locations, and the identities of several senior family members. These fields create a structured record of family relationships and precise biographical data.
The data is stored as ordinary plaintext. The skill does not provide:
- Data-minimization guidance.
- A warning against committing the completed template to source control.
- Secure-storage or file-permission requirements.
- A retention period or deletion procedure.
- Redaction guidance for AI conversations, backups, logs, or cloud synchronization.
- A recommendation to provide only taboo characters instead of complete relat ...[truncated 2276 chars]
- Remediation
View remediation
Remediation Suggestions
-
Minimize collected information
- Request only the child's surname rather than both parents' full names.
- Request only characters or pronunciations that must be avoided, rather than complete relatives' names.
- Do not retain exact parental birth times or locations after optional calculations are complete.
- Clearly distinguish required fields from optional fields.
-
Provide a privacy-preserving template
- Add a redacted mode that uses aliases or initials.
- Permit approximate locations when exact coordinates or districts are unnecessary.
- Keep optional parental bazi information in a separate document so it is not collected by default.
-
Add explicit handling warnings
- Warn users not to commit completed templates to public or shared repositories.
- Warn that submitting the document to an AI service may place its contents in conversation history or service logs.
- Recommend excluding completed files through
.gitignoreand backup rules where appropriate.
-
Define storage and deletion controls
- Recommend local encrypted storage and restrictive file permissions.
- Specify that completed documents should be deleted after the naming process unless the user explicitly chooses retention.
- Provide instructions for removing copies from AI history, synchronized storage, backups, and repository history.
-
Use transient processing where possible
- Perform optional calculations without writing raw birth information into a persistent project file.
- Store only derived results necessary for later comparison.
- Redact personal information from generated candidate and comparison reports.
-