richfrem/create-stateful-skill
plugins/agent-scaffolders/skills/create-stateful-skill/SKILL.md
Scaffolds an advanced stateful agent skill with session memory and state management. NOT for simple stateless skills (use `create-skill`) and NOT for GitHub agentic workflows (use `create-agentic-workflow`).
$ install --global
skillsauthnpx skillsauth add richfrem/agent-plugins-skills create-stateful-skillInstall 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: Jul 13, 2026, 6:11 AM37.6s1 file scanned
SKILL.md
- name:
- create-stateful-skill
- plugin:
- agent-scaffolders
- description:
- >
- argument-hint:
- [skill-name]
- allowed-tools:
- Bash, Read, Write
Follow the create-stateful-skill skill workflow to scaffold an advanced agent skill
with L4 state management, lifecycle artifacts, and chained commands.
Inputs
$ARGUMENTS— optional skill name or use-case description. Omit to start with discovery.
Steps
- If
$ARGUMENTSprovides a skill name or context, use it to seed discovery - Follow the create-stateful-skill phased workflow: confirm which L4 patterns are needed (state management, lifecycle artifacts, tone configuration, chained commands, escalation taxonomy), design the state schema and lifecycle checkpoints, then scaffold the skill directory with full L4 scaffolding
- Report created skill path and explain the state management strategy
Output
Skill directory with SKILL.md implementing selected L4 patterns, state schema,
lifecycle artifact templates, and chained command definitions.
Edge Cases
- If
$ARGUMENTSis empty: begin with discovery — identify which L4 patterns apply - If the use case is simple (no persistent state, no chaining): recommend
create-skillinstead — stateful scaffolding adds complexity that simple skills don't need - If the workflow requires human checkpoints: design explicit escalation taxonomy steps
Related Skills
richfrem/issue-worktree-agent
testing
VerifiedTrustedCommunity
Skill for creating and managing isolated git worktrees (`.worktrees/issue-NNN`) for issue execution branches. USE ONLY when setting up or cleaning up isolated git worktrees for specific issue execution. DO NOT USE for managing local task files (use `task-agent`) or escalating tasks to issues (use `github-issue-backlog-agent`).
4SKILL.mdUpdated Jul 29, 2026
richfrem/issue-pr-lifecycle-agent
data-ai
VerifiedTrustedCommunity
Skill for orchestrating the end-to-end GitHub issue lifecycle flow: Issue -> Worktree -> Implementation -> PR Creation -> Resolution Closure. USE ONLY when running or dry-running full lifecycle orchestration for resolving an issue with a PR. DO NOT USE for isolated worktree management only (use `issue-worktree-agent`) or logging issues (use `github-issue-agent`).
4SKILL.mdUpdated Jul 29, 2026
richfrem/github-issue-prioritizer
tools
VerifiedTrustedCommunity
Automatically ranks GitHub issues (P0-P3) based on friction tier, frequency, and blockages, synchronizing priority labels and GitHub Projects v2 custom fields.
4SKILL.mdUpdated Jul 29, 2026
richfrem/github-issue-backlog-agent
testing
VerifiedTrustedCommunity
Bridge skill for escalating ephemeral local task scratchpad items (`tasks/*.md`) into durable, taxonomy-validated, evidence-rich GitHub Issues. USE ONLY when promoting a single-session local task into durable repository backlog. DO NOT USE for managing local kanban boards (use `task-agent` instead) or directly querying/commenting on issues (use `github-issue-agent` instead).
4SKILL.mdUpdated Jul 29, 2026