By memorysaver
Build, list, and execute agentic workflows as Markdown files: generate pipelines from natural language by matching skills in a registry, orchestrate multi-step executions with subagents, and validate JSON outputs using TypeScript scripts via bun.
npx claudepluginhub memorysaver/looplia-core --plugin looplia-coreScaffold a new workflow definition
Build a looplia workflow from natural language. Create looplia pipeline, generate workflow automation.
List available Looplia workflows
Execute a looplia workflow on content. Run looplia pipeline, start workflow automation.
Load the skill catalog for workflow building. This skill should be used when discovering available looplia skills or listing what capabilities are available. Use when someone says "what looplia skills are installed", "list available skills", "/build", "what can looplia do", or "show me all looplia capabilities". v0.7.0: Replaces plugin-registry-scanner with skill catalog for faster access. Auto-syncs from all sources on every build to ensure freshest skill catalog.
This skill should be used when matching user requirements to available skills from a compiled registry. It receives a skill registry (from registry-loader) and user requirements, then scores each skill based on capability alignment, producing prioritized matches with confidence scores. Triggers: "match skills to requirements", "find relevant skills for workflow", "which skill handles X", "score skill capabilities", "/build" (after registry load), "find skills for this task", "match my requirements to skills". Second step in looplia workflow building pipeline: takes user requirements and skill registry, recommends skill sequences with missions. Designs one workflow step → one skill-executor → multiple skills orchestration pattern.
This skill should be used when the user wants to execute a looplia workflow, run workflow steps, or process a workflow.md file. Use when someone says "run the looplia workflow", "execute this looplia pipeline", "/run writing-kit", "start the looplia automation", or "process these workflow steps". Architecture: One workflow step triggers one general-purpose subagent call, which then invokes skills to accomplish the step's mission. Each step = separate context window. Handles sandbox management, per-step orchestration, and validation state tracking. v0.6.9: Unified general-purpose subagent strategy for all providers (context offload).
This skill should be used when the user wants to create a new looplia workflow, generate a workflow definition file, or compose workflow steps from skill recommendations. Use when someone says "create a looplia workflow", "generate workflow.md", "compose workflow steps", "build me an automation pipeline", or "/build" (final step). Final step in looplia workflow building: transforms skill recommendations into valid v0.7.0 workflow YAML/Markdown files. Each step uses skill: + mission: syntax, following the one workflow step → one skill-executor → multiple skills architecture. v0.7.0: Generates explicit `skills:` declaration for selective plugin loading. v0.6.3: Supports input-less workflows using input-less capable skills (e.g., search).
This skill should be used when the user wants to validate a looplia workflow output, check if an artifact meets validation criteria, or debug validation failures. Use when someone says "validate this looplia output", "check if the workflow output is valid", "verify the artifact JSON", or "debug why validation failed". Runs deterministic validation scripts against JSON artifacts. Primarily used for manual retry/debugging since automatic validation is handled by PostToolUse hooks. Part of looplia's one step → one skill-executor → multiple skills architecture.
Complete collection of battle-tested Claude Code configs from an Anthropic hackathon winner - agents, skills, hooks, rules, and legacy command shims evolved over 10+ months of intensive daily use
Complete collection of battle-tested Claude Code configs agents, skills, hooks, rules, and legacy command shims evolved over 10+ months of intensive daily use
Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Works with Claude Code, Kiro, Clawd CLI, Gemini CLI, Cursor, Continue, Hermes, and 17+ AI coding assistants. Now with Arabic, German, Spanish, and Chinese (Simplified & Traditional) support.
Unity Development Toolkit - Expert agents for scripting/refactoring/optimization, script templates, and Agent Skills for Unity C# development
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.