igor1309/synopsis
synopsis/SKILL.md
Use when the user needs a concise description of a component, module, product, or entire codebase for someone with zero project context. Triggers on "synopsis", "describe this for outsiders", "write a description", "explain what this does", "elevator pitch", or when producing text for READMEs, marketplace listings, or onboarding docs.
development
Updated Apr 20, 2026
$ install --global
skillsauthnpx skillsauth add igor1309/skills synopsisInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 20, 2026, 2:00 AM3.8s1 file scanned
SKILL.md
- name:
- synopsis
- version:
- 1.0.0
- description:
- >
- allowed-tools:
- Read, Grep, Glob, Agent
Synopsis
Produce a concise, behavior-focused description of the target for a reader with zero project context.
The target is: $ARGUMENTS
If $ARGUMENTS is empty, infer from conversation context. If unclear, ask.
Process
- Explore. Read docs, README, and code related to the target. Use both — docs tell intent, code tells truth.
- Synthesize. Write the synopsis following the constraints below.
- Present. Print the synopsis. Stop.
No file writes. No follow-up suggestions. Just the text.
Constraints
- Audience: someone who knows nothing about this project.
- Focus: behavior and input/output contract. Not architecture, not implementation, not tech stack (unless the tech is the product).
- Negative space: state key things the target does NOT do, when those set important expectations.
- Length: ~100 words by default. If the user specifies a different budget, use that.
- Tone: direct, declarative. No marketing fluff, no hedging.
Quality Checklist
Before presenting, verify:
- Could a stranger understand what this does without reading the code? → yes
- Does it mention how it works internally? → no (remove it)
- Does it state what goes in and what comes out? → yes
- Does it name what the target explicitly does NOT do? → yes, if relevant
- Is it within the word budget? → yes
Related Skills
igor1309/tdd-scaffold-review
testing
VerifiedTrustedCommunity
Evaluates test name scaffolds for TDD readiness by determining if each test name provides enough specification clarity to write a failing test. Use when reviewing test scaffolds, evaluating executable specifications, or assessing whether test names clearly define testable behavior without implementation ambiguity.
SKILL.mdUpdated Apr 20, 2026
igor1309/tdd-interactive
development
VerifiedTrustedCommunity
Interactive Test-Driven Development workflow with reviewer-in-the-loop. Implements the RED-GREEN-REFACTOR cycle with two mandatory verification gates where a reviewer (human or AI) approves work before progression. Applies to any code development that follows test-first methodology: features, bug fixes, refactoring, or enhancements. Invoked when TDD discipline with step-by-step verification is required.
SKILL.mdUpdated Apr 20, 2026
igor1309/swift-package-manifest
development
VerifiedTrustedCommunity
Clean, maintainable Package.swift creation and editing using the static property pattern from Facebook iOS SDK. Use when creating new Package.swift files, refactoring existing ones, adding modules/targets to Swift packages, or organizing Swift Package Manager manifests for better maintainability.
SKILL.mdUpdated Apr 20, 2026
igor1309/skill-review
development
VerifiedTrustedCommunity
Review and improve existing Claude Code skills. Use when evaluating skill quality, auditing skill collections, asking "review my skill", "is this skill effective", "improve skill description", or maintaining a skill library.
SKILL.mdUpdated Apr 20, 2026