sofer/problem-statement
skills/problem-statement/SKILL.md
Turn a vague or underspecified request into a self-contained problem statement. Use when the user has a rough idea, when a request would fail if handed directly to an agent, or before non-trivial work that needs shared understanding.
$ install --global
skillsauthnpx skillsauth add sofer/.agents problem-statementInstall 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: May 1, 2026, 6:39 AM101.7s1 file scanned
SKILL.md
- name:
- problem-statement
- description:
- Turn a vague or underspecified request into a self-contained problem statement. Use when the user has a rough idea, when a request would fail if handed directly to an agent, or before non-trivial work that needs shared understanding.
Problem statement
Purpose
Create a clear, portable statement of the problem before planning or implementation.
Process
- Take the user's request as given.
- Identify the gaps that matter:
- missing context
- ambiguous terms
- unstated assumptions
- audience or user
- success criteria
- constraints and non-goals
- risks or failure modes
- Infer safe details from context when the inference is low-risk.
- Ask only questions where guessing would affect correctness, scope, risk, ownership, or verification.
- Rewrite the request as a self-contained problem statement.
Output
Produce:
## Problem statement
[One paragraph to half a page that someone could understand without the prior conversation.]
## Assumptions
- [What was inferred and why]
## Open questions
- [Only questions that still affect execution]
## Risks
- [Ways the work could be technically correct but wrong]
For small tasks, keep the output shorter and use chat as the record. For non-trivial work, this can become the basis for a lightweight plan or spec.
Related Skills
sofer/agent-config-audit
tools
VerifiedTrustedCommunity
Check whether Claude and Codex have equivalent access to shared agent resources, skills, hooks, plugins, MCP servers, permissions, startup behaviour, and provider-specific adapter config. Use when comparing agent environments, debugging missing capabilities after restart, or deciding whether to symlink a resource or configure a runtime.
4SKILL.mdUpdated May 10, 2026
sofer/skill-usage
testing
VerifiedTrustedCommunity
Record substantive skill use in an append-only local log. Use after choosing or invoking a non-system skill for real work, when a skill is inspected but not used, or when a skill fails to apply. Do not use for routine system skills or incidental file reads.
4SKILL.mdUpdated May 1, 2026
sofer/learning
data-ai
VerifiedTrustedCommunity
Append a one-line learning to ~/.agents/learning-log.md. Use when the user types /learning, or when something genuinely worth remembering surfaced during work and the user confirms it should be captured.
4SKILL.mdUpdated May 1, 2026
sofer/evaluate
testing
VerifiedTrustedCommunity
Define evaluation criteria, tests, or quality checks for a deliverable, implementation, workflow, or recurring agent task. Use when defining done, improving a test harness, or checking whether output meets its specification.
4SKILL.mdUpdated May 1, 2026