Skills poteto-principles
📦

poteto-principles

Content revision r1 Safe ⚙️ External commands🌐 Network access

Apply Engineering Principles to Software Changes

Software changes can repeat avoidable design, debugging, and verification mistakes. This skill gives coding assistants explicit engineering principles for making simpler, better-supported decisions.

Supports: Claude Codex Code(CC)
Maintain this Skill? Claim it 📊 75 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 "poteto-principles" from https://skillstore.io/skills/masseater-poteto-principles.md and its manifest at https://skillstore.io/api/skills/masseater-poteto-principles/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/masseater-poteto-principles.md Signed manifest GET /api/skills/masseater-poteto-principles/manifest Signed lockfile GET /api/skills/masseater-poteto-principles/lockfile

Test it

Using "poteto-principles". Two fixes changed retry timing, but the same workers still receive most of the load.

Expected outcome:

  • Shared assumption: retry timing causes the imbalance.
  • Next evidence: count work assignments per worker across repeated runs.
  • If the same workers dominate, inspect assignment rules before changing timing again.
  • Verify any correction with both per-worker distribution and end-to-end behavior.

Using "poteto-principles". Review a task model with a completion flag and an optional completion date.

Expected outcome:

  • The model permits a completed task without a completion date.
  • Represent open and completed tasks as distinct variants, with a required date for the completed variant.
  • Parse external records at the boundary and test both accepted and rejected states.

Using "poteto-principles". Our API refactor adds an adapter, but all callers are internal.

Expected outcome:

  • Confirm that no external users require compatibility.
  • Inventory internal callers and migrate them in verifiable units.
  • Remove the old API after caller migration and verify the new observable contract.
  • Use an adapter only when a specific transition requires it, with an explicit removal condition.

Security Audit

Safe
v1 • 10/24/2026 Open versioned report

All 31 static findings are false positives involving Markdown backticks, software engineering prose, attribution metadata, or readable multilingual text. No evidence found of prompt injection, credential theft, unauthorized network execution, or concealed payloads in the reviewed files. Semantic findings and remediation are empty.

25
Files scanned
382
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (25)
SKILL.md:20 SKILL.md:22 SKILL.md:23 SKILL.md:24 SKILL.md:25 SKILL.md:26 SKILL.md:27 SKILL.md:28 SKILL.md:29 SKILL.md:30 SKILL.md:31 SKILL.md:32 SKILL.md:33 SKILL.md:34 SKILL.md:35 SKILL.md:36 SKILL.md:37 SKILL.md:38 SKILL.md:39 SKILL.md:40 SKILL.md:41 SKILL.md:42 SKILL.md:43 SKILL.md:44 SKILL.md:45
🌐 Network access (1)
SKILL.md:5
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
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
Security Assessment

Copy report link

https://skillstore.io/skills/masseater-poteto-principles/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/masseater-poteto-principles/security.svg)](https://skillstore.io/skills/masseater-poteto-principles?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/masseater-poteto-principles?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/masseater-poteto-principles/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/masseater-poteto-principles.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

masseater. (2026). poteto-principles security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/masseater-poteto-principles/audits/1

BibTeX citation

@techreport{masseater-masseater-poteto-principles-2026, author = {masseater}, title = {poteto-principles security audit report (audit version 1)}, institution = {Skillstore}, year = {2026}, number = {1}, url = {https://skillstore.io/skills/masseater-poteto-principles/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: "poteto-principles security audit report (audit version 1)" version: "unspecified" type: report authors: - name: "masseater" date-released: "2026-10-24" url: "https://skillstore.io/skills/masseater-poteto-principles/audits/1" identifiers: - type: other value: "skillstore:masseater-poteto-principles:audit:1" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium
45
Architecture
85
Maintainability
87
Content
65
Community
83
Spec Compliance

What You Can Build

Diagnose recurring failures

Use reproduction and evidence to identify a shared faulty assumption after repeated fixes fail.

Plan a coordinated API migration

Inventory internal callers, define verification boundaries, and remove the legacy path when compatibility requirements permit.

Review design and test quality

Assess domain models, validation boundaries, reader load, and whether tests assert observable behavior.

Try These Prompts

Beginner: Review a small change 
Review [change] using poteto-principles. Identify unnecessary complexity, unclear state, and missing verification. Explain your recommendations without editing files.
Intermediate: Diagnose a recurring bug 
Investigate [bug] and these failed fixes: [attempts]. Reproduce the failure, identify shared assumptions, and propose the smallest root-cause fix with a behavioral regression test.
Advanced: Plan an API migration 
Plan migration from [old API] to [new API]. Inventory callers and compatibility requirements. Define reversible phases, verification boundaries, and conditions for removing the old API.
Expert: Review retry and concurrency safety 
Review [workflow] for shared mutable state, retries, and partial failures. Propose isolation or serialization, reconciliation steps, and direct checks for repeated runs and interrupted execution.

Best Practices

  • Provide the relevant code, observed behavior, constraints, and verification commands before requesting recommendations.
  • Define compatibility requirements and approval boundaries before planning migrations or autonomous edits.
  • Keep reproduction steps, direct checks, and measurement evidence with each proposed change.

Avoid

  • Applying every principle mechanically without checking project constraints or existing invariants.
  • Removing validation before confirming that every external input is parsed at the correct boundary.
  • Treating compilation, mock call counts, or agent reports as proof of correct user-visible behavior.

Frequently Asked Questions

What is poteto-principles?
It is a written collection of engineering principles for design, implementation, debugging, refactoring, migration, verification, and documentation work.
Can I use it with Claude, Codex, and Claude Code?
The marketplace metadata lists all three tools. Actual file access, editing, and verification depend on the capabilities and permissions of your environment.
Does the skill include scripts or an automated checker?
No. It contains Markdown guidance that recommends creating repeatable tools and checks when appropriate.
Is the guidance specific to TypeScript?
No. Most principles are language-independent. The type-system reference includes examples from several languages and points to a separate TypeScript skill.
Does it allow irreversible actions without approval?
No. Its autonomy guidance explicitly requires confirmation for force-pushing, deleting production data, and sending external messages.
Does it include the linked benchmark checklist?
No. The measurement guidance links to a separate benchmark checklist that is not bundled with this skill.

Developer Details

Author

masseater

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Repository

https://github.com/masseater/skills/tree/4810c8f1186a229ca57d2f278c0a94f0fc862fec/skills/poteto-principles

Ref

4884e8ca178242496c82c517dcebea18c1f716fd

Maintenance freshness

10/24/2026

Usage

0 downloads · 0 views

File structure

📁 references/

📄 attack-the-premise.md

📄 boundary-discipline.md

📄 build-the-lever.md

📄 encode-lessons-in-structure.md

📄 exhaust-the-design-space.md

📄 experience-first.md

📄 explain-the-number.md

📄 fix-root-causes.md

📄 foundational-thinking.md

📄 guard-the-context-window.md

📄 laziness-protocol.md

📄 make-operations-idempotent.md

📄 migrate-callers-then-delete-legacy-apis.md

📄 minimize-reader-load.md

📄 model-the-domain.md

📄 never-block-on-the-human.md

📄 outcome-oriented-execution.md

📄 prove-it-works.md

📄 redesign-from-first-principles.md

📄 separate-before-serializing-shared-state.md

📄 sequence-verifiable-units.md

📄 subtract-before-you-add.md

📄 test-behavior-not-implementation.md

📄 type-system-discipline.md

📄 SKILL.md

More from masseater

View all

Related Skills

View all