Showing 39421–39450 of 77200 skills
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
opsmill/nornir-infrahub
Generate a custom checklist for the current feature based on user requirements.
opsmill/nornir-infrahub
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
opsmill/nornir-infrahub
Create or update the project constitution from interactive or provided principle inputs.
opsmill/nornir-infrahub
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
opsmill/nornir-infrahub
Execute the implementation plan by processing and executing all tasks defined in tasks.md
opsmill/nornir-infrahub
Execute the implementation planning workflow using the plan template to generate design artifacts.
opsmill/nornir-infrahub
Create or update the feature specification from a natural language feature description.
opsmill/nornir-infrahub
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
opsmill/nornir-infrahub
Deprecated: Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
opsmill/nornir-infrahub
브랜치 이름과 커밋 메시지를 팀 규칙대로 만든다. 사람이 /git-convention 또는 $git-convention으로 부를 때만 쓴다
prgrms-be-devcourse/NBE12-14-final-homestamp
CoinGecko API documentation - cryptocurrency market data API, price feeds, market cap, volume, historical data. Use when integrating CoinGecko API, building crypto price trackers, or accessing cryptocurrency market data.
aiskillstore/marketplace
Tatsh/patreon-archiver
Run a task iteratively over a user-specified duration by dispatching subagents. The orchestrator stays strictly linear and time-checked, but each iteration fans out MULTIPLE subagents in parallel over independent units (and those subagents may fan out further). Shared state — a compact progress digest and a growing environment cheatsheet — lives on disk and is passed to every subagent BY REFERENCE, killing the per-subagent rediscovery tax. Every subagent first reads an initialiser preamble that points it at that shared state and makes it write findings back, so the cheatsheet populates itself; role prompts are produced ONCE on the filesystem by a single scaffold command and dispatched by path, never re-typed per dispatch. Subagents persist their results to disk and return only a tiny status, so the orchestrator's context stays small and lasts. The orchestrator classifies the goal as FINITE or OPEN-ENDED: finite lists may finish early; open-ended goals use the full duration, never idle, never manufacture busywork. Use when the user gives a task and a duration and wants it ground out iteratively by subagents over that time.
av/skills
Run work as an explicit event-driven state machine executed by subagents. The orchestrator is the runtime from the canonical loop — `state, effects = init(machine); execute(effects); while state is active: event = nextEvent(); state, effects = transition(machine, state, event); execute(effects); return state.output`. All routing judgment is authored ONCE, at plan time, into a machine file (states, event alphabet, transition table, budgets, final states); at runtime the orchestrator does pure table lookups and dispatches effects — it never decides, never authors, never ingests artifacts. Subagent/sync protocol is the timeboxed-iterating one: role prompts scaffolded once to disk and dispatched BY PATH, an initialiser preamble every subagent reads first, a self-populating cheatsheet, per-unit files, tiny structured returns, independent measurement gate. Use when the user says "workmachine", "run this as a state machine", "state-machine this", or when a goal has a small number of clearly named phases with explicit outcomes (built / passed / failed / blocked) and you want the routing to be auditable rather than judged on the fly. For clock-driven loops use timeboxed-iterating; for wide graphs with judged edge criteria use workgraph.
av/skills
Package completed data analysis and ML work so an independent recipient can reproduce the claimed results, verify artifact lineage, and operate the handoff within its stated scope. Use when finalizing a project, study, model package, or review bundle; not for deploying to a live system.
aiopshwang/data-analysis-ml-agent-skills
A relentless interview to sharpen a plan or design.
egma-ai/egma
Stop. That last message did not land — re-pitch it.
egma-ai/egma
Add a new warp route to the Nexus UI whitelist. Checks out the nexus branch of hyperlane-warp-ui-template, adds the warp route ID to warpRouteWhitelist.ts, and opens a PR targeting the nexus branch.
recoil-labs/recoil-link
Post-deployment ownership transfer and registry PR for a warp route. Transfers ownership from the temporary deployer address to real owners, adds CoinGecko ID, commits, and opens a registry PR. Run after warp-deploy-init completes deployment.
recoil-labs/recoil-link
Sub-skill de agent-ready-cloudflare: Implement API Catalog
fabricioctelles/skills
Sub-skill de agent-ready-cloudflare: Implement llms.txt
fabricioctelles/skills
Sub-skill de agent-ready-cloudflare: Implement robots.txt
fabricioctelles/skills
Sub-skill de agent-ready-cloudflare: Implement sitemap.xml
fabricioctelles/skills
Sub-skill de agent-ready-cloudflare: Implement Web Bot Auth
fabricioctelles/skills
Sub-skill de agent-ready-cloudflare: Implement WebMCP
fabricioctelles/skills
Living status scorecard for Cogni agent infrastructure — InProc↔LangGraph-Server alignment, built-vs-designed inventory, and the agent/langgraph doc DRY/drift/consolidation state. The stable mental model lives in agent-infrastructure-expert; this is the dated state that moves as graphs, executors, and evals ship. Use to check "what's actually built vs paper", "where do InProc and Server diverge", "which agent specs are stale/duplicated/safe-to-delete". Update THIS, not the expert skill.
cogni-dao/cogni
Akash runtime canon for how Cogni nodes run on decentralized compute. Use when working on Akash placement, leases, providers, bids, escrow, compute egress, or debugging a node that will not come up on Akash. Nodes ship through POST /api/v1/deploy/workloads; the hub owns that journey. Triggers on: 'akash', 'lease', 'placement', 'bid', 'provider', 'escrow', 'zencloud', 'egress', 'node-deploy', 'sequencer'.
cogni-dao/cogni
Evaluate the project's biggest constraint to achieving its mission using Theory of Constraints. Performs independent research, challenges assumptions, and records a dated finding against the constraint taxonomy (https://cognidao.org/knowledge/constraint-toc-taxonomy) through a hub contribution. Use this skill whenever the user asks about constraints, bottlenecks, blockers, what to work on next, strategic priorities, or "what's holding us back." Also use it when the user wants a strategic health check, wants to understand where the project stands, or asks about TOC analysis. Even if the user just says "evaluate" or "triage" without specifics, this skill is likely what they want.
cogni-dao/cogni
Use when contributing or refining durable knowledge in a Cogni node hub, including migrating existing documentation. Recall existing knowledge before research or writing; route predictions to EDO and useful human visuals to their authoring guide. Routine progress stays in work items.
cogni-dao/cogni