Is architecture-patterns safe to install?

SaferSkills independently audited architecture-patterns (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

library/methodologies/cc10x/skills/architecture-patterns/SKILL.md · 1 file

library/methodologies/cc10x/skills/architecture-patterns/SKILL.md1.6 KB · Markdown

name: architecture-patterns

description: System and API design guidance covering component boundaries, data flow, integration patterns, and scalability considerations.

allowed-tools: Read, Write, Edit, Bash, Grep, Glob, WebSearch

Architecture Patterns

Overview

Guidance for system architecture and API design decisions within CC10X workflows. Used during PLAN and BUILD workflows for architectural choices.

Domain Areas

Component Design

Single responsibility boundaries
Interface contracts and type safety
Dependency injection patterns
Module cohesion and coupling analysis

Data Flow

Request/response patterns
Event-driven architecture
State management strategies
Data transformation pipelines

Integration Patterns

API design (REST, GraphQL, RPC)
Message queuing and async processing
Service boundaries and communication
Error propagation across boundaries

Scalability

Horizontal vs vertical scaling considerations
Caching strategies
Database design and query optimization
Load balancing and distribution

Decision Checkpoints

Architectural decisions require user approval when:

Introducing new service boundaries
Changing data flow patterns
Adding new external dependencies
Modifying public API contracts

When to Use

During PLAN workflow architecture phases
During BUILD when architectural choices arise
When reviewing system design in REVIEW workflow

Agents Used

planner (architecture planning)
component-builder (architecture implementation)
code-reviewer (architecture review)

architecture-patterns— agent skill

Is architecture-patterns safe to install?

Architecture Patterns

Overview

Domain Areas

Component Design

Data Flow

Integration Patterns

Scalability

Decision Checkpoints

When to Use

Agents Used

Audit the pieces. Scan the whole. Decide.