Explore skills
Showing 44251–44280 of 71536 skills
Execute the full end-to-end permission matrix against the live Uniffy app through the two Playwright MCP browsers: every sharing, access, denial, viewing, revocation, and request-access case on every content domain (notes, files, projects, tasks, calendar, chat, agents, automations, rooms), proven as the affected user. Covers the PostgreSQL-authoritative access behaviors: instant revocation in search and mentions, per-surface search authorization (spotlight, domain searches, filters, pagination), restricted chips, access requests, COMMENTER and role floors, expiry-aware grants, live org-default inheritance, group membership churn, delete and tag and bookmark revocation, attachment byte gating, and live no-reload pruning. Use when asked to run the permission matrix, matrix-test the permission system, do a full e2e sweep of sharing and access control, or validate a permissions PR end to end. Use `uniffy-e2e-flows` for a lighter single-domain permission loop and `uniffy-playwright` for one-off browser inspection. Skip for unit or integration tests, backend-only work, or when the dev stack is not running and the user has not asked to start it.
uniffy-io/uniffy
Stars: 24Claude CodeCodexStress-test a rough idea before writing requirements and save the agreed direction as brief.md.
rizanw/steno-spec
Stars: 1Claude CodeCodexBreak an approved steno design into an ordered, traceable task list (tasks.md). Use when the spec phase is "tasks".
rizanw/steno-spec
Stars: 1Claude CodeCodexReviews Swift Testing code for proper use of
existential-birds/beagle
Stars: 88Claude CodeCodexRetire a closed issue's working artifacts out of specs/ into the GitHub wiki. Use only when the user asks to archive a finished issue, empty out specs/ for a done task, or move an issue's requirements/architecture/tasks/review/QA docs to the wiki.
foyzulkarim/skills
Stars: 43Claude CodeCodexConvert an AWS CloudFormation stack or template to Pulumi. This skill MUST be loaded whenever a user requests migration or conversion of CloudFormation to Pulumi.
dirien/yet-another-agent-harness
Stars: 19Claude CodeCodexConvert or migrate Azure ARM (Azure Resource Manager) templates, Bicep templates, or code to Pulumi, including importing existing Azure resources. This skill MUST be loaded whenever a user requests migration, conversion, or import of ARM templates, Bicep templates, ARM code, Bicep code, or Azure resources to Pulumi.
dirien/yet-another-agent-harness
Stars: 19Claude CodeCodexBest practices for using Pulumi Automation API to programmatically orchestrate infrastructure operations. Covers multi-stack orchestration, embedding Pulumi in applications, architecture choices, and common patterns.
dirien/yet-another-agent-harness
Stars: 19Claude CodeCodexBest practices for writing reliable Pulumi programs. Covers Output handling, resource dependencies, component structure, secrets management, safe refactoring with aliases, and deployment workflows.
dirien/yet-another-agent-harness
Stars: 19Claude CodeCodexConvert an AWS CDK application to Pulumi. This skill MUST be loaded whenever a user requests migration or conversion of a CDK application to Pulumi.
dirien/yet-another-agent-harness
Stars: 19Claude CodeCodexGuide for authoring Pulumi ComponentResource classes. Use when creating reusable infrastructure components, designing component interfaces, setting up multi-language support, or distributing component packages.
dirien/yet-another-agent-harness
Stars: 19Claude CodeCodexGuidance for working with Pulumi ESC (Environments, Secrets, and Configuration). Use when users ask about managing secrets, configuration, environments, short-term credentials, configuring OIDC for AWS, Azure, GCP, integrating with secret stores (AWS Secrets Manager, Azure Key Vault, HashiCorp Vault, 1Password), or using ESC with Pulumi stacks.
dirien/yet-another-agent-harness
Stars: 19Claude CodeCodexConfigure or explicitly update SpecBind for a project and complete the resulting aftercare. Use for an explicit SpecBind binary or project-asset update request, initial post-install review, or later changes to Agents, role models, artifact language, project instructions, templates, shared Rules, operational adapters, Steering, or existing artifacts affected by configuration changes.
Huruikagi/pc-build-planner
Stars: 0Claude CodeCodexJudge whether the milestone's changes leave every persistent seam in the project coherent, and accept the one contract review that Tasks authoring waits on.
Huruikagi/pc-build-planner
Stars: 0Claude CodeCodexUse directly when the user asks why a Task failed or cannot be implemented. Establish the root cause, categorize it, and return a next action. Read-only; never starts implementation or applies the fix.
Huruikagi/pc-build-planner
Stars: 0Claude CodeCodexTurn a change request or Source Collection into confirmed Spec and milestone boundaries.
Huruikagi/pc-build-planner
Stars: 0Claude CodeCodexDrive the active milestone through every safe reachable planning, implementation, and validation action. Park branch-local attention and continue elsewhere; stop before release execution.
Huruikagi/pc-build-planner
Stars: 0Claude CodeCodexCompare what a change needs against what the repository already provides, and record the findings worth keeping. Informs the decision; does not make it.
Huruikagi/pc-build-planner
Stars: 0Claude CodeCodexImplement or resume one roadmap item — executing a Spec's approved task plan through returned review or diagnosis with dispatched implementers and reviewers, or performing and completing a Direct change. Do not use for a diagnosis-only request asking why work failed or cannot be implemented.
Huruikagi/pc-build-planner
Stars: 0Claude CodeCodexPlan active Spec work through Requirements, Design, Contract Review, and Tasks, run one explicitly requested planning phase for one named Spec, or prepare explicitly scoped project shared Contracts. Ordinary Spec planning uses one named Spec or explicit all-Spec scope.
Huruikagi/pc-build-planner
Stars: 0Claude CodeCodexClose the active milestone — bind the version, run the project's release procedure, judge whether it worked, and finalize the whole milestone once it did.
Huruikagi/pc-build-planner
Stars: 0Claude CodeCodexJudge whether one implemented task is done correctly, from the actual diff and the approved requirements, design, and plan.
Huruikagi/pc-build-planner
Stars: 0Claude CodeCodexReport where a Spec or active milestone is in its lifecycle and what can happen next. Read-only; do not use to judge whether completed implementation is actually done.
Huruikagi/pc-build-planner
Stars: 0Claude CodeCodexMaintain durable project guidance — bootstrap it, synchronize it after code changes, or document a long-lived project convention such as testing, API, security, or deployment.
Huruikagi/pc-build-planner
Stars: 0Claude CodeCodexIndependently judge whether a Spec's design is ready to be built on — requirement coverage, boundary, buildability, self-containment, and architectural fit.
Huruikagi/pc-build-planner
Stars: 0Claude CodeCodexUse only when every Task for a named Spec is complete and the user explicitly asks for lifecycle validation against the active Requirement IDs that records completion on GO. For a consequence-free claim check, use sb-verify-completion.
Huruikagi/pc-build-planner
Stars: 0Claude CodeCodexConsequence-free check of an explicit completion or success claim against fresh evidence. Changes nothing; do not use to advance a named Spec whose implementation may be accepted.
Huruikagi/pc-build-planner
Stars: 0Claude CodeCodexConfigure or explicitly update SpecBind for a project and complete the resulting aftercare. Use for an explicit SpecBind binary or project-asset update request, initial post-install review, or later changes to Agents, role models, artifact language, project instructions, templates, shared Rules, operational adapters, Steering, or existing artifacts affected by configuration changes.
Huruikagi/pc-build-planner
Stars: 0Claude CodeCodexJudge whether the milestone's changes leave every persistent seam in the project coherent, and accept the one contract review that Tasks authoring waits on.
Huruikagi/pc-build-planner
Stars: 0Claude CodeCodexUse directly when the user asks why a Task failed or cannot be implemented. Establish the root cause, categorize it, and return a next action. Read-only; never starts implementation or applies the fix.
Huruikagi/pc-build-planner
Stars: 0Claude CodeCodex