Skip to content
skillsafebeta
← Report library
Purpose / Other

Python Design Patterns Skill Security Audit

What the author says it does (original text)

Python design patterns including KISS, Separation of Concerns, Single Responsibility, and composition over inheritance. Use this skill when designing a new service or component from scratch and choosing how to layer responsibilities, when refactoring a God class or monolithic function that has grown too large, when deciding whether to add a new abstraction or live with duplication, when evaluating

Independent security check

No obvious risks found in this check

Files checked
2
Risks found
0
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.No risks found
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.No risks found
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.No risks found

Inside this skill

7 instruction sections

This Skill is guidance for Python software design, intended to help design, refactor, and evaluate code structure; it recommends simplicity, separation of responsibilities, and composition.

View source
SKILL.md:8In the instructionsOpen original file
Write maintainable Python code using fundamental design principles. These patterns help you build systems that are easy to understand, test, and modify.
SKILL.md:21In the instructionsOpen original file
### 1. KISS (Keep It Simple)Choose the simplest solution that works. Complexity must be justified by concrete requirements.### 2. Single Responsibility (SRP)Each unit should have one reason to change. Separate concerns into focused components.### 3. Composition Over InheritanceBuild behavior by combining objects, not extending classes.### 4. Rule of ThreeWait until you have three instances before abstracting. Duplication is often better than premature abstraction.

The main file directs the agent to read the bundled detailed reference only when the short guidance is insufficient; the supplied file set shows that reference is present.

View source
SKILL.md:48In the instructionsOpen original file
## Detailed patterns and worked examplesDetailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient.

Database, cache, external-API, and notification code in the detailed file appears in instructional examples illustrating layering and dependency injection. The visible content does not direct the agent to execute these snippets, install software, read user files, use credentials, or transmit real data.

View source
references/details.md:95In the instructionsOpen original file
### Pattern 3: Separation of ConcernsOrganize code into distinct layers with clear responsibilities.
references/details.md:117In the instructionsOpen original file
┌─────────────────────────────────────────────────────┐│  Repository Layer (data access)                      ││  - SQL queries                                       ││  - External API calls                                ││  - Cache operations                                  │└─────────────────────────────────────────────────────┘
references/details.md:264In the instructionsOpen original file
### Pattern 7: Dependency InjectionPass dependencies through constructors for testability.
Start here · InstructionsSKILL.md
python-design-patterns
Lines connect the instruction file to its sections, not an observed execution order. Select a section to read the source.

File reference map

References: 1
Files making referencesReferenced content
Lines show actual file references, not execution order. Select a node to highlight its connections and inspect the files and source locations. Dashed lines include files that still need locating.
Files and check records2 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
  • references/details.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
  • references/details.mdSupporting file

Operations mentioned in code and instructions

Read files
SKILL.md:50In the instructionsOpen original file
Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient.
Lines read
440
File checksum (to compare versions)
d8c9c02a0ca891d73d24f8c9c7492442bd005e44e214180c941acf0d1bddb567