Skip to content

Explore skills

Search every indexed skill by name, description, repository or instructions, then narrow the results.

Showing 73141–73170 of 74274 skills

healereric-cielo/mofloRun moflo's Healer (`flo healer`, alias for `flo doctor`) from inside the Claude session. Audit-only by default; pass `--fix` to apply auto-repairs, `-c <component>` for a single check. Use when something feels off (missing moflo.yaml, daemon dead, statusline empty, hooks not firing) or as a periodic health check. Distinct from Claude Code's built-in `/doctor`, which diagnoses Claude Code itself, not moflo.Stars: 19Updated Claude CodeCodexUnverifiedInstall
luminariumeric-cielo/mofloPrint the localhost URL for The Luminarium — moflo's daemon dashboard — for the current project. Use when the user asks for "the luminarium link", "the moflo dashboard", "the daemon UI", or anything synonymous. Each project gets a deterministic port in 33000–33999; the actual bound port is recorded in `.moflo/daemon.lock`.Stars: 19Updated Claude CodeCodexUnverifiedInstall
meditateeric-cielo/mofloDeliberate session retrospective — look back over what you just did, distill the durable, reusable lessons (not session trivia), and write them to the learnings memory namespace, deduped against what is already stored. Use at the END of a meaningful chunk of work to capture high-signal lessons worth keeping long-term. The curated counterpart to moflo's passive session-continuity capture.Stars: 19Updated Claude CodeCodexUnverifiedInstall
memory-optimizationeric-cielo/mofloTune moflo's memory stack for speed, RAM, and index quality. Covers HNSW parameters (M, efConstruction, ef), vector quantization, batch operations, and common bottlenecks. Use when scaling past ~100k entries or when search latency regresses.Stars: 19Updated Claude CodeCodexUnverifiedInstall
memory-patternseric-cielo/mofloPersistent memory patterns for moflo agents — session memory, long-term knowledge, pattern learning, and cross-session context via moflo's node:sqlite + HNSW vector store. Use when building stateful agents or assistants that need to remember across runs.Stars: 19Updated Claude CodeCodexUnverifiedInstall
memory-teameric-cielo/mofloGuided setup for sharing moflo's durable learnings through a git-tracked artifact — for a whole TEAM on one repo, OR for one person across several MACHINES (a team of one). Use when the user says "share learnings with my team", "commit our moflo memory", "sync memory across my laptop and desktop", "set up memory.team_artifact", "auto-export learnings on every PR", or "learnings.jsonl keeps conflicting". Installs a pre-commit hook so the artifact rides along in every commit. An existing learnings.jsonl moves to the conflict-free layout automatically. For many worktrees on ONE machine, use /memory-worktree.Stars: 19Updated Claude CodeCodexUnverifiedInstall
memory-worktreeeric-cielo/mofloVerify, customize, or opt out of moflo's AUTOMATIC durable-learning sharing across git worktrees / Conductor workspaces on one machine. As of the worktree-auto-sharing change this is on by default — learnings converge across a repo's worktrees with no setup. Use when the user asks "is memory shared across my worktrees?", "where are my worktree learnings stored?", "turn off worktree memory sharing", "share learnings across my separate clones", or "point my worktrees at a custom store". For a team or cross-machine (git-tracked) sharing, use /memory-team instead.Stars: 19Updated Claude CodeCodexUnverifiedInstall
optimize-learningseric-cielo/mofloAudit and curate the `learnings` memory namespace — the one namespace nothing re-derives, so the only one that rots. Runs moflo's mechanical audit to nominate stale, unused, and near-duplicate entries, then decides entry by entry whether to keep, retire, compress, or merge, and propagates the result to the shared artifact. Use when memory search returns stale or duplicated hits, after retiring a big chunk of work whose supporting entries went stale with it, or as a periodic pass once the namespace passes a few hundred entries.Stars: 19Updated Claude CodeCodexUnverifiedInstall
perf-auditeric-cielo/mofloAlias for /quicken — see that skill's description.Stars: 19Updated Claude CodeCodexUnverifiedInstall
publisheric-cielo/mofloBump version, build, test, publish to npm, and install locallyStars: 19Updated Claude CodeCodexUnverifiedInstall
quickeneric-cielo/mofloStars: 19Updated Claude CodeCodexUnverifiedInstall
reasoningbank-intelligenceeric-cielo/mofloAdaptive learning for moflo agents via ReasoningBank: trajectory storage, verdict judgment, memory distillation, consolidation, and MMR retrieval. Use when building agents that should improve from experience across runs.Stars: 19Updated Claude CodeCodexUnverifiedInstall
reset-epiceric-cielo/mofloReset an epic's test data — close PRs, delete branches, reopen issues, revert codeStars: 19Updated Claude CodeCodexUnverifiedInstall
spell-buildereric-cielo/mofloCreate, edit, and validate spell definitions (YAML/JSON) that compose connectors and step commands into end-to-end spells. Use when building new spell definitions, modifying existing ones, or exploring available spell components.Stars: 19Updated Claude CodeCodexUnverifiedInstall
spell-scheduleeric-cielo/mofloSchedule a moflo spell to run on the local machine via the moflo daemon (cron, interval, or one-time). Use when the user wants to schedule, automate, or recurringly run one of THEIR spells locally — e.g. "schedule the oap spell every hour", "run my audit spell every weekday at 9am", "fire X once tomorrow morning". This is the LOCAL daemon path. For remote Anthropic-cloud agents, use /schedule instead.Stars: 19Updated Claude CodeCodexUnverifiedInstall
test-gapseric-cielo/mofloAlias for /ward — see that skill's description.Stars: 19Updated Claude CodeCodexUnverifiedInstall
vector-searcheric-cielo/mofloSemantic vector search with moflo — RAG over your own documents, similarity matching, context-aware retrieval via HNSW (node:sqlite-backed). Use when building retrieval layers for chat, search, or context-assembly.Stars: 19Updated Claude CodeCodexUnverifiedInstall
verifyeric-cielo/mofloVerify-before-done — exercise the current change end-to-end against its acceptance criteria (the SDD plan's, or the ticket's) and report a per-criterion PASS/FAIL verdict, then record the outcome to memory. This is the concrete action that satisfies moflo's verify-before-done gate (`gates.verify_before_done` / `/flo -v` / `/flo -sd`). Use before `gh pr create` when the change must be proven to work, not just tested in passing. Verifies only — it does not fix; on FAIL it reports the gaps and stops.Stars: 19Updated Claude CodeCodexUnverifiedInstall
warderic-cielo/mofloStars: 19Updated Claude CodeCodexUnverifiedInstall
skillevaluator-operationsmouadja02/skillsUse when validating, comparing, or release-gating agent skills with NVIDIA SkillEvaluator — choose a static, overlap, harness, or live A/B tier; forecast dependencies and cost; run with explicit isolation and permission gates; and report exact evidence without overstating skipped tiers.Stars: 13Updated Claude CodeCodexUnverifiedInstall
cdpwellwelwel/weslley.ioVisual verification of a running page through Chrome's DevTools Protocol, capturing screenshots and measuring the rendered DOM. Use when a frontend change can only be confirmed once rendered, for layout, spacing, alignment, overflow, or theme tokens.Stars: 13Updated Claude CodeCodexUnverifiedInstall
engineeringwellwelwel/weslley.ioAuthoritative engineering reference covering code conventions, comments, TypeScript type rules, testing, and commit messages. Use before writing or changing any source file, and when suggesting a commit message.Stars: 13Updated Claude CodeCodexUnverifiedInstall
imageswellwelwel/weslley.ioResponsive image generation and audit through a deterministic hook. It encodes every declared master into AVIF and WebP at the widths devices actually render, detects drift between masters and their generated variants, and pairs with the Picture component so pages serve the smallest fitting source. Use when adding, changing, or auditing raster images.Stars: 13Updated Claude CodeCodexUnverifiedInstall
refinewellwelwel/weslley.ioConfronts a scope with the engineering, testing, and writer skills, each where it applies, and with the architecture a long-lived project needs, then brings it into line. It removes what should not exist, simplifies, decouples, sharpens responsibilities and names, and places files and directories where they belong. The scope is the unstaged, staged, or current work, commits, a branch, paths, a focus, or the whole workspace, named in any language.Stars: 13Updated Claude CodeCodexUnverifiedInstall
testingwellwelwel/weslley.ioAuthoritative reference for deciding whether a test should exist and what it must assert. Use before writing or changing tests, and when investigating a test failure.Stars: 13Updated Claude CodeCodexUnverifiedInstall
uiwellwelwel/weslley.ioDesign engineering principles for making interfaces feel polished. Use when building UI, reviewing frontend code, or working on any visual detail, from animations, hover states, shadows, borders, and typography to optical alignment and tabular numbers.Stars: 13Updated Claude CodeCodexUnverifiedInstall
writerwellwelwel/weslley.ioAuthoritative reference for writing the project's prose. Use before writing, editing, or translating any document, command text, comment, or user-facing message.Stars: 13Updated Claude CodeCodexUnverifiedInstall
asyncSystemorph/MeshWeaverForwarding AccessContext through async/reactive boundaries, and the no-async rule on the actor-model mesh. Use when writing or reviewing any hub-reachable / Blazor-view / agent-round / IIoPool code that creates, reads, or updates a mesh node, OR when a write "silently does nothing" / "Access denied" appears after a .Subscribe / IIoPool / Observable.Create hop. The async/await/ToTask/.Wait/.Result/.GetAwaiter/FirstAsync family and lost AccessContext are the two ways async boundaries cause wedges and storms. Grounded in AsynchronousCalls.md, SyncedMeshNodeQueries.md, AccessContextPropagation.md.Stars: 12Updated Claude CodeCodexUnverifiedInstall
ciSystemorph/MeshWeaverWhat CI proves, what it cannot prove, and how to write a gate that cannot pass on no evidence. Use when authoring or changing a GitHub Actions workflow, adding a required check, wiring a satellite repo CI, or reasoning about whether a green run actually covers your change. Covers the absolute no-skip-trapdoor rule (a gate must never carry continue-on-error on its input step nor an if that asks whether a secret is set — GitHub paints a skipped job the same colour as a passed one), the reusable workflow_call jobs satellite repos must call instead of hand-rolling, why runs on main are deliberately never cancelled, and the large body of in-mesh C# that no dotnet build or test ever type-checks.Stars: 12Updated Claude CodeCodexUnverifiedInstall
debugSystemorph/MeshWeaverDebug a deadlock / hang / timeout in the mesh — a test that times out, a hub handler whose response never arrives, a GetRemoteStream / GetMeshNodeStream / GetQuery that never emits, an agent round or per-instance-hub activation that parks forever. Use whenever something times out and you need to find WHERE the message flow breaks down. The timeout is the symptom, never the bug — raising it just hangs longer. Grounded in DebuggingMessageFlow.md.Stars: 12Updated Claude CodeCodexUnverifiedInstall