القائمة
Help people discover and join Codex community events, form teams, submit projects or talks, judge entries, and organize events.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/globodex/codex-events --skill codex-eventsيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
عرض SKILL.md
Use when implementing Auth0 authentication in Nuxt 3/4 applications, configuring session management, protecting routes with middleware, or integrating API access tokens - provides setup patterns, composable usage, and security best practices for the @auth0/auth0-nuxt SDK
Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), feature flags (Flagship), networking (Tunnel, Spectrum), security (WAF, DDoS), and infrastructure-as-code (Terraform, Pulumi). Use for any Cloudflare development task. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
Use when you want to (1) brand an Auth0 tenant's Universal Login to match a website or brand assets (colors, logo, fonts, page layout, text); (2) manually update one or more branding values (logos, colors, fonts, borders, backgrounds, text strings, or the page template) without extraction; (3) rewrite login text to match a voice and tone; (4) reset branding to Auth0 defaults; or (5) check whether a tenant is set up for branding to take effect end-to-end. Does not cover Advanced Customizations for Universal Login (ACUL); use the `acul-screen-generator` skill for that.
| name | codex-events |
| description | Help people discover and join Codex community events, form teams, submit projects or talks, judge entries, and organize events. |
Use only the macro tools and actions exposed for the authenticated user. A missing action means the user does not currently have that capability; do not approximate it with another role's action.
Each macro accepts an action and optional input. Call it with only action when you need the exact field schema. Call it again with input to execute. Never invent fields or send an arbitrary REST path or method.
For event-specific work, establish the event before calling a mutation. When the user has overlapping responsibilities, ask which capacity they intend only when it changes the action or information they can access.
events_read exposes get.events.builder.catalog and post.events.builder.analyze, and that events_upsert exposes post.events.events_read with get.events.builder.catalog before recommending blocks or templates.post.events.builder.analyze through events_read as often as useful.post.events through events_upsert only after that confirmation.For every consequential mutation, state the affected event or record and the intended outcome, then obtain confirmation immediately before the call. Read-only inspection and builder analysis do not require confirmation.
If a workflow requires authentication, account linking, file upload, CSV import, or another capability absent from the tool list, direct the user to the Codex Events web application.