Explore skills
Showing 50221–50250 of 77104 skills
Cherwell ITSM integration. Manage data, records, and automate workflows. Use when the user wants to interact with Cherwell ITSM data.
membranedev/application-skills
Stars: 272Claude CodeCodexChift integration. Manage data, records, and automate workflows. Use when the user wants to interact with Chift data.
membranedev/application-skills
Stars: 272Claude CodeCodexChimp Rewriter integration. Manage data, records, and automate workflows. Use when the user wants to interact with Chimp Rewriter data.
membranedev/application-skills
Stars: 272Claude CodeCodexChipax integration. Manage data, records, and automate workflows. Use when the user wants to interact with Chipax data.
membranedev/application-skills
Stars: 272Claude CodeCodexChMeetings integration. Manage data, records, and automate workflows. Use when the user wants to interact with ChMeetings data.
membranedev/application-skills
Stars: 272Claude CodeCodexChocolatey integration. Manage data, records, and automate workflows. Use when the user wants to interact with Chocolatey data.
membranedev/application-skills
Stars: 272Claude CodeCodexCINC integration. Manage data, records, and automate workflows. Use when the user wants to interact with CINC data.
membranedev/application-skills
Stars: 272Claude CodeCodexCincopa integration. Manage data, records, and automate workflows. Use when the user wants to interact with Cincopa data.
membranedev/application-skills
Stars: 272Claude CodeCodexCircle integration. Manage data, records, and automate workflows. Use when the user wants to interact with Circle data.
membranedev/application-skills
Stars: 272Claude CodeCodexCircle integration. Manage data, records, and automate workflows. Use when the user wants to interact with Circle data.
membranedev/application-skills
Stars: 272Claude CodeCodexCircleCI integration. Manage Projects, Users, Organizations. Use when the user wants to interact with CircleCI data.
membranedev/application-skills
Stars: 272Claude CodeCodexCirrus Labs integration. Manage data, records, and automate workflows. Use when the user wants to interact with Cirrus Labs data.
membranedev/application-skills
Stars: 272Claude CodeCodexCisco AppDynamics integration. Manage data, records, and automate workflows. Use when the user wants to interact with Cisco AppDynamics data.
membranedev/application-skills
Stars: 272Claude CodeCodexCisco Meraki integration. Manage data, records, and automate workflows. Use when the user wants to interact with Cisco Meraki data.
membranedev/application-skills
Stars: 272Claude CodeCodexCisco Webex integration. Manage data, records, and automate workflows. Use when the user wants to interact with Cisco Webex data.
membranedev/application-skills
Stars: 272Claude CodeCodexUse when switching AI persona/language style. Syncs 13+ character profiles (Ding Yuanying, Lin Daiyu, Lu Xun, Li Yunlong, etc.) from GitHub, generates persona prompts with thinking patterns, rhetoric, and speech traits.
superzhang21/ghostwriter
Stars: 306Claude CodeCodexDevelop, modify, debug, review, maintain, and explain the SRS and Oryx codebases and the SRS Docker image toolchain. Use for planned changes to the next-generation SRS Go proxy, SRS browser player, ossrs/dev-docker images, or Oryx Go backend, React dashboard, integrated runtime, packaging, installers, releases, and tests; bug maintenance; issue and pull-request triage; pull-request review; and Learn Code questions. The C++ SRS server is in maintenance mode, and planned Go origin and edge development is not yet supported. NOT for end-user support, usage questions, or configuration help — use srs-support for those.
Ocyss/srs-auth
Stars: 0Claude CodeCodexFast, consistent Markdown auto-formatter for typographic cleanup, normalization, and clean semantic line breaks. Use when creating, editing, or cleaning Markdown; formatting LLM-generated docs; adopting Flowmark in a repository; adding Markdown format scripts or commit hooks; or replacing Prettier or another Markdown formatter.
jlevy/flowmark
Stars: 83Claude CodeCodexCompares tracked job postings against the candidate profile to identify skill gaps and generate a prioritized learning plan with study resources. Triggers on: /upskill, upskill, skill gaps, what should I learn, learning plan
zaheer037/job-search
Stars: 0Claude CodeCodexProduce an implementation-ready, caller-first structural design for a sufficiently understood engineering problem. Manual invocation only; use when the user explicitly asks to architect a change or define its types, signatures, data structures, and module boundaries. Use brainstorm for unresolved future behavior and explain-code for a neutral current-code walkthrough.
drafael/coding-harness
Stars: 1Claude CodeCodexProduce and compare at least two independent attempts at the same concrete artifact, then return one coherent synthesis with its verification result. Manual invocation only for direct use; an explicitly invoked workflow whose instructions permit arena delegation may run a bounded phase while retaining final judgment. Do not use to split a larger task into different work slices.
drafael/coding-harness
Stars: 1Claude CodeCodexAnalyze a concrete code change for credible breakage beyond the obvious diff and seek executable proof for the assumptions that make it safe. Manual invocation only; use for an explicitly requested blast-radius analysis of a local diff, commit range, branch comparison, or local patch.
drafael/coding-harness
Stars: 1Claude CodeCodexExplore unresolved future behavior, architecture, ownership, features, or substantive alternatives through collaborative dialogue before implementation. Use when the user explicitly asks to brainstorm, explore options, or think through a future change, or when another active skill identifies consequential decisions that still need exploration. Use explain-code for neutral current-code walkthroughs, architect when explicitly invoked for implementation-ready structural design, and technical-writing when available to structure an agreed design.
drafael/coding-harness
Stars: 1Claude CodeCodexInvestigate expected-versus-actual behavior, suspected defects, and historical design rationale. Use when someone asks why observed behavior differs from expectations, whether behavior is wrong, or why a design decision exists. Use explain-code for neutral questions about what code does or how it works, and wrong when the user rejects the assistant's current approach.
drafael/coding-harness
Stars: 1Claude CodeCodexFind actionable defects and risks through a focused, evidence-based review of correctness, regressions, security, performance, architecture, and testing. Use for requests to review, audit, critique, or identify improvements. Use blast-radius, when explicitly invoked and available, for cross-boundary consequence tracing and executable safety proof of a concrete change. Use explain-code when the user only wants to understand current behavior or architecture.
drafael/coding-harness
Stars: 1Claude CodeCodexSystematically debug and fix errors using structured investigation. Use when the user asks to "debug", "fix an error", "troubleshoot", "investigate a bug", or shares an error message or stack trace.
drafael/coding-harness
Stars: 1Claude CodeCodexDiscover the OS, available CLI tools, and suitable execution environments to verify material migration, transaction, concurrency, API, service-integration, or runtime claims during planning, implementation, or review. Prefer isolated local verification; support explicitly user-approved endpoint discovery and invocation through OpenAPI/Swagger, CI/CD, and cloud tests. Recommend missing tools with OS-appropriate installation instructions tied to the claim. Own cleanup and report evidence, blockers, and limits. Not a general workstation-setup or deployment skill.
drafael/coding-harness
Stars: 1Claude CodeCodexExplain current code behavior, structure, runtime flow, data flow, and component ownership. Use for ordinary walkthroughs, line-by-line explanations, subsystem mental models, and questions about what code does or how it works. Use teach, when explicitly invoked and available, for progressive learning; technical-writing, when available, for substantial standalone documentation; clarify for expectation mismatches or historical intent; code-review for finding problems; refactor-code for structural changes; brainstorm for unresolved future design; and architect, when explicitly invoked and available, for implementation-ready structural design.
drafael/coding-harness
Stars: 1Claude CodeCodexCatch the user up on changes in the current chat and every decision or action still waiting on them. Manual invocation only; use when the user explicitly invokes ketchup or requests this catch-up workflow. Read-only; distinguish verified state from reports and unknowns.
drafael/coding-harness
Stars: 1Claude CodeCodexChange existing code through narrow, behavior-preserving, test-backed simplification without speculative architecture or scope growth. Use for requests to refactor, clean up, restructure, or simplify code. Use explain-code instead when the user only wants an explanation of the current structure.
drafael/coding-harness
Stars: 1Claude CodeCodex