Loading…
Showing 7351–7380 of 10180 skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| discerndonald-ada/workinggeniusExplore the paths first where none are on record (the `invent` skill), then attack every path adversarially with one blind attacker per path, commit to one, and present the commitment — consequences for the user to confirm, kills on the record. Use when the user asks to run discernment on a tracked piece of work (`/discern`, or in words), or asks for a ready-made plan to be attacked before it is built. A work whose `next:` names this stage is not that ask, because the flow never advances itself, and a plan handed over to be implemented is not an invitation to attack it or to start the flow. | Stars: 6 | Updated | Claude CodeCodex | Verified | Install |
| genius-filedonald-ada/workinggeniusRead and update Working Genius work files — the work's folder holding the bounded snapshot a cold session acts on, the append-only log behind it, and the contract that binds the unbuilt slices. Use when a stage skill needs the work-file discipline, when the user asks what work is in flight or where a piece of work left off, or before resuming any work tracked under .genius/. | Stars: 6 | Updated | Claude CodeCodex | Verified | Install |
| record-prosedonald-ada/workinggeniusHow the flow's records are written — every document under .genius/, snapshot to backlog line. Use when writing or rewriting any of them, or when another skill needs the prose discipline. | Stars: 6 | Updated | Claude CodeCodex | Verified | Install |
| didww-connectdidww/aiConnect a DIDWW phone number to ANY AI voice platform: helps choose the platform, then wires the SIP trunk pair and number. Use whenever the user wants a voice AI agent on a DIDWW number and has not committed to a platform, asks which AI platform to use with DIDWW, or names a platform that has no dedicated didww-to-X skill installed. Covers ElevenLabs, Vapi, Retell, Ultravox, Vogent, OpenAI Realtime, xAI, LiveKit and the enterprise-gated platforms. | Stars: 7 | Updated | Claude CodeCodex | Verified | Install |
| didww-to-elevenlabsdidww/aiConnect a DIDWW phone number to an ElevenLabs voice agent over SIP, as automatically as both platforms allow. Use whenever the user wants an ElevenLabs agent (Agents Platform, Conversational AI) on a real phone number via DIDWW, mentions pairing DIDWW with ElevenLabs, importing a SIP trunk into ElevenLabs, sip.rtc.elevenlabs.io, or debugging calls between the two. Covers inbound, outbound, transfers and verification. | Stars: 7 | Updated | Claude CodeCodex | Verified | Install |
| didww-to-livekitdidww/aiConnect a DIDWW phone number to a LiveKit Agents worker over SIP, on LiveKit Cloud or self-hosted: inbound trunk, dispatch rule to a named agent, optional outbound trunk. Use whenever the user wants a LiveKit agent (any STT, LLM and TTS combination, including Claude as the brain) answering a real number via DIDWW, mentions sip.livekit.cloud, SIP inbound trunks or dispatch rules, lk sip commands, agent_name dispatch, or debugging calls between DIDWW and LiveKit. This is the bring-your-own-brain pairing: the agent is code the user runs. | Stars: 7 | Updated | Claude CodeCodex | Verified | Install |
| didww-to-openai-realtimedidww/aiPoint a DIDWW phone number directly at OpenAI's Realtime API over SIP, with a generated webhook backend for call control. Use whenever the user wants gpt-realtime answering a real phone number via DIDWW, mentions sip.api.openai.com, realtime.call.incoming webhooks, Realtime SIP, or debugging calls between DIDWW and OpenAI. This is the developer-grade pairing: the agent behavior is code the user owns. | Stars: 7 | Updated | Claude CodeCodex | Verified | Install |
| didww-to-retelldidww/aiConnect a DIDWW phone number to a Retell AI agent over custom telephony, with full MCP automation: Retell's official MCP can create agents AND import numbers. Use whenever the user wants a Retell agent on a real phone number via DIDWW, mentions pairing DIDWW with Retell, custom telephony, sip.retellai.com, import-phone-number, or debugging calls between the two. | Stars: 7 | Updated | Claude CodeCodex | Verified | Install |
| didww-to-ultravoxdidww/aiConnect a DIDWW phone number to an Ultravox Realtime voice agent over SIP. Use whenever the user wants an Ultravox agent on a real phone number via DIDWW, mentions pairing DIDWW with Ultravox, an account SIP domain, agent_ addresses, allowedCidrRanges, or debugging calls between the two. Covers the address-based routing model that makes Ultravox different from every number-import platform. | Stars: 7 | Updated | Claude CodeCodex | Verified | Install |
| didww-to-vapididww/aiConnect a DIDWW phone number to a Vapi assistant over BYO SIP trunking, as automatically as Vapi allows. Use whenever the user wants a Vapi assistant on a real phone number via DIDWW, mentions pairing DIDWW with Vapi, byo-sip-trunk credentials, sip.vapi.ai, or debugging calls between the two. Covers inbound, outbound, transfers and agent binding, following Vapi's and DIDWW's own DIDWW guides. | Stars: 7 | Updated | Claude CodeCodex | Verified | Install |
| didww-to-vogentdidww/aiConnect a DIDWW phone number to a Vogent voice agent over SIP import. Use whenever the user wants a Vogent agent on a real phone number via DIDWW, mentions pairing DIDWW with Vogent, sip_import numbers, sip.vogent.ai, or debugging calls between the two. | Stars: 7 | Updated | Claude CodeCodex | Verified | Install |
| didww-to-xaididww/aiPoint a DIDWW phone number at xAI's Grok voice over SIP. Use whenever the user wants Grok answering a real phone number via DIDWW, mentions sip.voice.x.ai, xAI realtime calls, registering a phone number with xAI, or debugging calls between DIDWW and Grok. Developer-grade: agent behavior is configured per call over a websocket the user's code owns. | Stars: 7 | Updated | Claude CodeCodex | Verified | Install |
| long-poll-waitKbediako/evergreen-codex-skillsMonitor an external process, CI run, or cloud job until an authoritative terminal result or explicit handoff. Excludes native Codex children and app tasks. | Stars: 5 | Updated | Claude CodeCodex | Verified | Install |
| native-agent-deliberationKbediako/evergreen-codex-skillsCompare competing strategies through independent agent viewpoints when a consequential decision needs evidence, tradeoffs, and dissent. | Stars: 5 | Updated | Claude CodeCodex | Verified | Install |
| native-codex-coordinationKbediako/evergreen-codex-skillsChoose between solo work, native-agent execution, deliberation, evaluation, and waiting when the appropriate coordination workflow is unclear. | Stars: 5 | Updated | Claude CodeCodex | Verified | Install |
| native-subagents-firstKbediako/evergreen-codex-skillsCoordinate native Codex subagents for requested parallel work or independent execution and review scopes. Use for ownership, worker selection, and lifecycle management. | Stars: 5 | Updated | Claude CodeCodex | Verified | Install |
| voice-delegate-guidanceKbediako/evergreen-codex-skillsCoordinate operative Codex Voice handoffs through delegated work, including transcript-tail delivery, or honor explicit delegate-only mode. Excludes quoted wrappers and delegated workers. | Stars: 5 | Updated | Claude CodeCodex | Verified | Install |
| wait-for-subagents-patientlyKbediako/evergreen-codex-skillsWait for quiet native Codex children and reconcile their state before declaring a stall, interrupting, replacing, or handing off without a result. | Stars: 5 | Updated | Claude CodeCodex | Verified | Install |
| skillifyjscraik/Agent-SkillsCapture a completed Codex workflow as a reusable SKILL.md package by analyzing session context plus optional session-collector evidence, interviewing the user with structured prompts, and writing a validated skill artifact. Use when the user asks to skillify or operationalize a repeatable process. | Stars: 9 | Updated | Claude CodeCodex | Verified | Install |
| codex-model-routing-teamzjp1997720/codex-model-routing-team在 Codex App 中为复杂、可并行的知识工作或编程任务自动创建多个可指定模型与推理强度的后台任务,由主 Agent 负责规划、分工、集成和验收。用于多来源调研、多章节内容、复杂 Skill/PPT、跨模块开发、独立验证或 2 个以上互不依赖工作流;也用于用户明确要求模型路由、后台 Worker、Agents Team 或持久项目协作。简单问答、状态查询、单文件小改、强顺序任务和发布/付款/删除/账户操作不得自动触发。 | Stars: 160 | Updated | Claude CodeCodex | Verified | Install |
| securingAppsReactMcpp2-inc/keycloak-skillsWire Keycloak login into a React SPA with oidc-spa, and register or repair the OIDC client the app needs, driven through the Keycloak MCP server's tools. Use this whenever someone wants login added to a browser app - login/logout controls, route protection, reading the signed-in user - against a Keycloak realm. Covers the oidc-spa v10 builder API (which replaced the removed createReactOidc), why the registered redirect URI needs a trailing slash, why updating an existing client must be a merge rather than a rebuild, and why web origins are a separate setting from redirect URIs that fails only in a real browser. | Stars: 5 | Updated | Claude CodeCodex | Verified | Install |
| corporateSsoLoginRestp2-inc/keycloak-skillsSet up corporate SSO / enterprise SSO on a self-managed Keycloak — send a user to their own company's identity provider based on the domain of the email address they type, while everyone else keeps password login — using the Admin REST API only (no MCP server involved). Use this whenever someone says "I want corporate SSO login", "we need enterprise SSO", "SSO for our customer", "let our customer log in with their company account", "log in with my company's SSO automatically", "redirect to my corporate IdP", "authenticate to my corporate IdP", "home realm discovery", "IdP discovery by email domain", "onboard an enterprise customer's SSO" — even if they only say "corporate SSO". Covers the organization + verified-domain + linked-IdP mechanism that performs the discovery, why an identity-provider-redirector execution is the wrong answer, and how to verify the routing by actually logging in. | Stars: 5 | Updated | Claude CodeCodex | Verified | Install |
| credentialEnrollmentMcpp2-inc/keycloak-skillsEnroll a NEW credential on a user who ALREADY exists in a Keycloak realm - a TOTP authenticator, a passkey, a replacement password, recovery codes - driven through the Keycloak MCP server's tools where they exist, with the genuine gaps covered by documented REST recipes. Use whenever someone wants users to "set up 2FA", "enroll in TOTP", "register an authenticator app", "set up my passkey", or asks how a user actually gets their first credential. Two variants, and the PREREQUISITE picks between them rather than preference: a required action set on the user reaches anyone who can already log in and needs no mail at all, while an emailed enrollment link is the only thing that reaches a user with no credential - and needs realm SMTP AND a verified email address, because the link authenticates whoever opens it. Both are silently inert unless the action is registered AND enabled, which is the single most common cause of "I configured it and nothing happened". Not authoring or binding a login flow - this is the step that makes such a flow usable. | Stars: 5 | Updated | Claude CodeCodex | Verified | Install |
| emailOtpLoginMcpp2-inc/keycloak-skillsTurn on passwordless login by a one-time code emailed to the user, on a Phase Two hosted Keycloak, driven through the Keycloak MCP server. Use this for "email OTP", "email a one-time code", "6-digit login code by email", or "passwordless login with a code instead of a link". Covers authoring the flow with importAuthenticationFlow (none ships auto-created), the load-bearing identifier-step choice that decides whether the realm leaks which addresses have accounts, setSmtpSettings, and setBruteForceProtection. Not Keycloak's TOTP/HOTP authenticator apps, and not magic link. | Stars: 5 | Updated | Claude CodeCodex | Verified | Install |
| emailOtpLoginRestp2-inc/keycloak-skillsTurn on passwordless login by a one-time code emailed to the user, on a self-managed Keycloak running the p2-inc keycloak-magic-link extension, using the Admin REST API only (no MCP server). Use this for "email OTP", "email a one-time code", "6-digit login code by email", or "passwordless login with a code instead of a link". Covers authoring the flow (none ships auto-created), the load-bearing identifier-step choice that decides whether the realm leaks which addresses have accounts, realm SMTP, and why brute-force protection matters for a 6-digit code. Not Keycloak's TOTP/HOTP authenticator apps, and not magic link (a clicked link rather than a typed code). | Stars: 5 | Updated | Claude CodeCodex | Verified | Install |
| idpFederationLoginMcpp2-inc/keycloak-skillsBroker a partner company's own OIDC identity provider into a Phase Two hosted Keycloak realm as a plain "log in with <partner>" button - driven through the Keycloak MCP server. Use this whenever someone asks to "let our partner's staff log in with their own account", "add a login-with-X button", "federate a partner's identity provider", or "broker an external OIDC provider" - with NO organization membership requirement and NO domain-based auto-routing attached. Covers createOidcIdp, mapping claims onto the brokered user with addIdpAttributeMapper, and verifying with more than one real user so no hidden per-user gate slips in. Not admin:org-restrict-login / admin:idp-org-restrict-login (those gate on organization membership) and not admin:corporate-sso-login (that routes by email domain) - this is an unconditional login button, nothing more. | Stars: 5 | Updated | Claude CodeCodex | Verified | Install |
| idpFederationLoginRestp2-inc/keycloak-skillsBroker a partner company's own OIDC identity provider into a self-managed Keycloak realm as a plain "log in with <partner>" button, using the Admin REST API only (no MCP server involved). Use this whenever someone asks to "let our partner's staff log in with their own account", "add a login-with-X button", "federate a partner's identity provider", or "broker an external OIDC provider" - with NO organization membership requirement and NO domain-based auto-routing attached. Covers POST identity-provider/instances, mapping claims onto the brokered user with oidc-user-attribute-idp-mapper, and verifying with more than one real user so no hidden per-user gate slips in. Not admin:org-restrict-login / admin:idp-org-restrict-login (those gate on organization membership) and not admin:corporate-sso-login (that routes by email domain) - this is an unconditional login button, nothing more. | Stars: 5 | Updated | Claude CodeCodex | Verified | Install |
| idpInitiatedSsoMcpp2-inc/keycloak-skillsWire IdP-initiated SSO ("portal tiles") from an already-federated SAML identity provider such as Okta or Microsoft Entra ID into ONE specific Keycloak client, when the Keycloak MCP server is available. Use this whenever someone asks for an Okta dashboard tile or an Entra "My Apps" tile that drops the user straight inside a particular application already logged in, for an app-embed link, or for "IdP-initiated SSO" / "unsolicited SAML response" into a named client. Covers which MCP tools help (whoAmI, listIdentityProviders, listClients, createSamlClient) and - critically - the two things the MCP surface cannot do here at all: add IdP-initiated SSO to an EXISTING client, and target an OIDC client. Both need raw Admin REST, so recognise the gap and drop to REST instead of thrashing with create/delete cycles. Not plain "let our users log in with Okta/Entra" federation - that is ordinary SP-initiated brokering, one login button serving every client. | Stars: 5 | Updated | Claude CodeCodex | Verified | Install |
| idpInitiatedSsoRestp2-inc/keycloak-skillsWire IdP-initiated SSO ("portal tiles") from an already-federated SAML identity provider such as Okta or Microsoft Entra ID into ONE specific Keycloak client, using the Admin REST API only (no MCP server involved). Use this whenever someone asks for an Okta dashboard tile or an Entra "My Apps" tile that drops the user straight inside a particular application already logged in, for an app-embed link, or for "IdP-initiated SSO" / "unsolicited SAML response" into a named client. Covers the broker endpoint /realms/{realm}/broker/{alias}/endpoint/clients/{urlName}, the three CLIENT attributes that control it, Keycloak's strict binding-selection priority and the extra steps an OIDC target needs, and why RelayState cannot choose the client. Not plain "let our users log in with Okta/Entra" federation - that is ordinary SP-initiated brokering, one login button serving every client. | Stars: 5 | Updated | Claude CodeCodex | Verified | Install |
| identityProviderOrgRestrictLoginRestp2-inc/keycloak-skillsRestrict FEDERATED (external identity provider) login to members of one organization on a self-managed Keycloak - the user authenticates at their own company's IdP and only gets in when they belong to the organization the application named in account_hint - using the Admin REST API only (no MCP server involved). Use this whenever someone asks for "corporate organization restriction", "restrict SSO login to a team/tenant", "only let this customer's staff into their own org", "organization-restricted corporate login", "gate IdP login by org membership", or a "post-broker organization check". Covers the organization-owned IdP link that makes the gate work at all, authoring and binding a post-broker login flow containing ext-select-org (the stock post-broker flow has none, so binding it gates nothing), the match_by_org_name name-vs-ID choice, and verifying by driving real brokered logins. Requires the p2-inc keycloak-orgs extension. Not domain-based routing to an IdP (that restricts nobody) and not the local-password organization gate. | Stars: 5 | Updated | Claude CodeCodex | Verified | Install |