[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MC2AVVGBTHHSRVC1K55QW0":3,"skill-same:01M6MC2AVVGBTHHSRVC1K55QW0":86},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":61,"ownerHtmlUrl":62,"ownerBlogUrl":63,"ownerDescription":64,"updatedAt":65,"install":66,"resources":79},"01M6MC2AVVGBTHHSRVC1K55QW0","django-q2",null,"Use when adding, changing, testing, or debugging Django Q2 background tasks, scheduled jobs, qcluster workers, Redis broker configuration, or ORM broker fallback in Django projects.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1571,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fdjango-q2\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"django q2","django","background-jobs","when","background","scheduled","broker","clients","background tasks","configuration","jobs","workers","testing","use","orm","projects","redis","code","tasks","debugging","codex","2026-11-10 10:12:30",false,"---\nname: django-q2\ndescription: \"Use when adding, changing, testing, or debugging Django Q2 background tasks, scheduled jobs, qcluster workers, Redis broker configuration, or ORM broker fallback in Django projects.\"\nlicense: MIT\ncompatibility: Codex, Claude Code, and other Agent Skills-compatible clients.\nmetadata:\n  version: \"0.1.0\"\n  displayName: Django Q2\n  category: Django\n  tags: django,django-q2,background-jobs,redis\n---\n\n# Django Q2 Background Jobs\n\nUse this before touching task enqueueing, schedules, worker deployment,\n`Q_CLUSTER`, or code imported by Django Q2 workers.\n\n## Configuration Checks\n\n- The dependency is `django-q2`; the Python import path is `django_q`.\n- `django_q` is in `INSTALLED_APPS`; its migrations provide task result,\n  schedule, and broker models.\n- Find `Q_CLUSTER` in the project's settings module before changing task,\n  worker, or broker behavior.\n- Confirm the configured broker. Redis is common, often through an environment\n  variable such as `REDIS_URL`; the ORM broker is useful for low-throughput or\n  Redis-free deployments.\n- Confirm the project's worker command. The base command is\n  `python manage.py qcluster`, but projects may wrap it with `uv`, Poetry,\n  Docker Compose, process managers, or platform-specific worker declarations.\n- If Redis is removed as the broker, review any Redis-dependent cache, health\n  check, Docker, deployment, and documentation references separately.\n\n## Mental Model\n\n- Web code calls `async_task(...)` or creates `Schedule` rows.\n- The broker stores queued task packages until a `qcluster` process reserves\n  work.\n- Worker processes execute importable Python functions and save results or\n  failures.\n- The scheduler runs inside the cluster. Schedules are database rows; they do\n  nothing unless `qcluster` is running.\n\n## Adding Tasks\n\n1. Put the task function in the app that owns the behavior, usually a\n   `tasks.py` module or another importable module already used by the project.\n2. Keep the function importable at module import time. Do not rely on request\n   objects, local closures, or process-local state.\n3. Pass durable identifiers such as primary keys, not model instances, open\n   files, connections, or large payloads.\n4. Make the task idempotent. Redis does not give exactly-once execution\n   guarantees, and receipt-based brokers can re-run work.\n5. If the task depends on a just-saved database row, enqueue it from\n   `transaction.on_commit(...)`.\n\n```python\ndef send_welcome_email(user_id: int) -> None:\n    from django.contrib.auth import get_user_model\n\n    user = get_user_model().objects.get(pk=user_id)\n    ...\n```\n\n```python\nfrom django.db import transaction\nfrom django_q.tasks import async_task\n\ntransaction.on_commit(\n    lambda: async_task(\"myapp.tasks.send_welcome_email\", user.pk)\n)\n```\n\nUse `q_options` when Django Q2 options would collide with task kwargs:\n\n```python\nasync_task(\n    \"myapp.tasks.rebuild_report\",\n    report_id,\n    q_options={\"timeout\": 300, \"group\": \"reports\"},\n)\n```\n\n## Scheduling Work\n\nPrefer named, idempotent schedules created by a migration, admin action, or\nsetup command. Avoid creating schedules unconditionally at import time or app\nstartup.\n\n```python\nfrom django_q.models import Schedule\n\nSchedule.objects.get_or_create(\n    name=\"clear-expired-sessions\",\n    defaults={\n        \"func\": \"django.core.management.call_command\",\n        \"args\": \"'clearsessions'\",\n        \"schedule_type\": Schedule.HOURLY,\n    },\n)\n```\n\nUse `Schedule.objects.get_or_create(name=..., defaults={...})` when seeding\nschedules so repeated setup does not duplicate jobs. Cron schedules require the\noptional `croniter` dependency; do not use `Schedule.CRON` unless the project\nincludes it.\n\nMissed schedules catch up by default. Set `Q_CLUSTER[\"catch_up\"] = False` when\na job should run once after downtime instead of replaying every missed interval.\n\n## Broker Choices\n\n### Redis Broker\n\nUse Redis when the project already depends on it for workers or deployment:\n\n```python\nQ_CLUSTER = {\n    \"name\": \"...\",\n    \"timeout\": 3600,\n    \"workers\": 4,\n    \"redis\": REDIS_URL,\n}\n```\n\nRedis is fast and usually fits projects that already run Redis for cache,\nDocker, or deployment workers. The default Redis broker does not support\ndelivery receipts. If a worker host dies catastrophically while executing a\ntask, the in-flight package can be lost; if task code raises, Django Q2 records\na failure. Use idempotent task design, explicit retries in task code where\nneeded, and monitoring for failures.\n\n### ORM Broker\n\nUse the Django database broker only for low-throughput deployments, local\nsimplicity, or environments where Redis is unavailable:\n\n```python\nQ_CLUSTER = {\n    \"name\": \"...\",\n    \"timeout\": 3600,\n    \"retry\": 4800,\n    \"workers\": 4,\n    \"max_attempts\": 2,\n    \"orm\": \"default\",\n}\n```\n\nWhen switching to ORM:\n\n- Remove the `\"redis\"` broker key; configure one broker per cluster unless you\n  intentionally use custom clusters.\n- Run migrations for `django_q`. If the broker uses a non-default database\n  alias, run migrations with `--database \u003Calias>`.\n- Increase `\"poll\"` above the default `0.2` seconds, for example `\"poll\": 2.0`,\n  when you need lower database polling pressure and can tolerate higher queue\n  pickup latency.\n- The ORM broker enables the Queued Tasks admin table.\n- Review Redis-dependent cache, health check, Docker, and deployment settings\n  separately. Schedules are always database rows; the broker setting controls\n  queued task packages, not the schedule table.\n\n## Testing\n\n- Test task business logic by calling the function directly.\n- Test enqueueing with synchronous mode:\n  - per call: `async_task(\"myapp.tasks.fn\", arg, sync=True)`\n  - per test: override `Q_CLUSTER[\"sync\"] = True`\n- For worker\u002Fbroker integration, run\n  the project's `qcluster` command in a separate process and wait for\n  `result(task_id, 200)` or a similar bounded wait; do not rely on arbitrary\n  sleeps.\n- Use `pytest.mark.django_db(transaction=True)` when a real worker process must\n  observe committed database rows.\n\n## Debugging Checklist\n\n- Is a `qcluster` process running with the same settings module, `SECRET_KEY`,\n  broker URL, and cluster name as the web process?\n- Can the worker import the dotted task path?\n- Did database migrations run, including `django_q` migrations?\n- Is Redis reachable from both web and worker containers, or is the ORM broker\n  polling the expected database?\n- Did a scheduled task duplicate because setup created another `Schedule` row\n  with no stable name?\n- Did downtime trigger schedule catch-up?\n- Is task failure visible in Django admin, logs, or the configured error\n  reporter?\n\n## References\n\n- Official docs: https:\u002F\u002Fdjango-q2.readthedocs.io\u002Fen\u002Fmaster\u002F\n- Upstream repo: https:\u002F\u002Fgithub.com\u002Fdjango-q2\u002Fdjango-q2\n","# Django Q2 Background Jobs\n\nUse this before touching task enqueueing, schedules, worker deployment,\n`Q_CLUSTER`, or code imported by Django Q2 workers.\n\n## Configuration Checks\n\n- The dependency is `django-q2`; the Python import path is `django_q`.\n- `django_q` is in `INSTALLED_APPS`; its migrations provide task result,\n  schedule, and broker models.\n- Find `Q_CLUSTER` in the project's settings module before changing task,\n  worker, or broker behavior.\n- Confirm the configured broker. Redis is common, often through an environment\n  variable such as `REDIS_URL`; the ORM broker is useful for low-throughput or\n  Redis-free deployments.\n- Confirm the project's worker command. The base command is\n  `python manage.py qcluster`, but projects may wrap it with `uv`, Poetry,\n  Docker Compose, process managers, or platform-specific worker declarations.\n- If Redis is removed as the broker, review any Redis-dependent cache, health\n  check, Docker, deployment, and documentation references separately.\n\n## Mental Model\n\n- Web code calls `async_task(...)` or creates `Schedule` rows.\n- The broker stores queued task packages until a `qcluster` process reserves\n  work.\n- Worker processes execute importable Python functions and save results or\n  failures.\n- The scheduler runs inside the cluster. Schedules are database rows; they do\n  nothing unless `qcluster` is running.\n\n## Adding Tasks\n\n1. Put the task function in the app that owns the behavior, usually a\n   `tasks.py` module or another importable module already used by the project.\n2. Keep the function importable at module import time. Do not rely on request\n   objects, local closures, or process-local state.\n3. Pass durable identifiers such as primary keys, not model instances, open\n   files, connections, or large payloads.\n4. Make the task idempotent. Redis does not give exactly-once execution\n   guarantees, and receipt-based brokers can re-run work.\n5. If the task depends on a just-saved database row, enqueue it from\n   `transaction.on_commit(...)`.\n\n```python\ndef send_welcome_email(user_id: int) -> None:\n    from django.contrib.auth import get_user_model\n\n    user = get_user_model().objects.get(pk=user_id)\n    ...\n```\n\n```python\nfrom django.db import transaction\nfrom django_q.tasks import async_task\n\ntransaction.on_commit(\n    lambda: async_task(\"myapp.tasks.send_welcome_email\", user.pk)\n)\n```\n\nUse `q_options` when Django Q2 options would collide with task kwargs:\n\n```python\nasync_task(\n    \"myapp.tasks.rebuild_report\",\n    report_id,\n    q_options={\"timeout\": 300, \"group\": \"reports\"},\n)\n```\n\n## Scheduling Work\n\nPrefer named, idempotent schedules created by a migration, admin action, or\nsetup command. Avoid creating schedules unconditionally at import time or app\nstartup.\n\n```python\nfrom django_q.models import Schedule\n\nSchedule.objects.get_or_create(\n    name=\"clear-expired-sessions\",\n    defaults={\n        \"func\": \"django.core.management.call_command\",\n        \"args\": \"'clearsessions'\",\n        \"schedule_type\": Schedule.HOURLY,\n    },\n)\n```\n\nUse `Schedule.objects.get_or_create(name=..., defaults={...})` when seeding\nschedules so repeated setup does not duplicate jobs. Cron schedules require the\noptional `croniter` dependency; do not use `Schedule.CRON` unless the project\nincludes it.\n\nMissed schedules catch up by default. Set `Q_CLUSTER[\"catch_up\"] = False` when\na job should run once after downtime instead of replaying every missed interval.\n\n## Broker Choices\n\n### Redis Broker\n\nUse Redis when the project already depends on it for workers or deployment:\n\n```python\nQ_CLUSTER = {\n    \"name\": \"...\",\n    \"timeout\": 3600,\n    \"workers\": 4,\n    \"redis\": REDIS_URL,\n}\n```\n\nRedis is fast and usually fits projects that already run Redis for cache,\nDocker, or deployment workers. The default Redis broker does not support\ndelivery receipts. If a worker host dies catastrophically while executing a\ntask, the in-flight package can be lost; if task code raises, Django Q2 records\na failure. Use idempotent task design, explicit retries in task code where\nneeded, and monitoring for failures.\n\n### ORM Broker\n\nUse the Django database broker only for low-throughput deployments, local\nsimplicity, or environments where Redis is unavailable:\n\n```python\nQ_CLUSTER = {\n    \"name\": \"...\",\n    \"timeout\": 3600,\n    \"retry\": 4800,\n    \"workers\": 4,\n    \"max_attempts\": 2,\n    \"orm\": \"default\",\n}\n```\n\nWhen switching to ORM:\n\n- Remove the `\"redis\"` broker key; configure one broker per cluster unless you\n  intentionally use custom clusters.\n- Run migrations for `django_q`. If the broker uses a non-default database\n  alias, run migrations with `--database \u003Calias>`.\n- Increase `\"poll\"` above the default `0.2` seconds, for example `\"poll\": 2.0`,\n  when you need lower database polling pressure and can tolerate higher queue\n  pickup latency.\n- The ORM broker enables the Queued Tasks admin table.\n- Review Redis-dependent cache, health check, Docker, and deployment settings\n  separately. Schedules are always database rows; the broker setting controls\n  queued task packages, not the schedule table.\n\n## Testing\n\n- Test task business logic by calling the function directly.\n- Test enqueueing with synchronous mode:\n  - per call: `async_task(\"myapp.tasks.fn\", arg, sync=True)`\n  - per test: override `Q_CLUSTER[\"sync\"] = True`\n- For worker\u002Fbroker integration, run\n  the project's `qcluster` command in a separate process and wait for\n  `result(task_id, 200)` or a similar bounded wait; do not rely on arbitrary\n  sleeps.\n- Use `pytest.mark.django_db(transaction=True)` when a real worker process must\n  observe committed database rows.\n\n## Debugging Checklist\n\n- Is a `qcluster` process running with the same settings module, `SECRET_KEY`,\n  broker URL, and cluster name as the web process?\n- Can the worker import the dotted task path?\n- Did database migrations run, including `django_q` migrations?\n- Is Redis reachable from both web and worker containers, or is the ORM broker\n  polling the expected database?\n- Did a scheduled task duplicate because setup created another `Schedule` row\n  with no stable name?\n- Did downtime trigger schedule catch-up?\n- Is task failure visible in Django admin, logs, or the configured error\n  reporter?\n\n## References\n\n- Official docs: https:\u002F\u002Fdjango-q2.readthedocs.io\u002Fen\u002Fmaster\u002F\n- Upstream repo: https:\u002F\u002Fgithub.com\u002Fdjango-q2\u002Fdjango-q2\n",{"name":5,"license":15,"metadata":50,"description":7,"compatibility":55},{"tags":51,"version":52,"category":53,"displayName":54},"django,django-q2,background-jobs,redis","0.1.0","Django","Django Q2","Codex, Claude Code, and other Agent Skills-compatible clients.","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fdjango-q2",490,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 02:12:02",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill django-q2",{"tool":72,"command":73},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill django-q2",{"tool":75,"command":76},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill django-q2","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fdjango-q2\u002FSKILL.md",true,[80],{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"assets\u002Fapp-icon.png","ASSET","资产文件",53182,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fdjango-q2\u002Fassets\u002Fapp-icon.png",[87,96,103,110,135,160],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":91,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":95},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":91,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":95},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":91,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":95},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":91,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":45},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[117,118,119,120,121,122,123,124,125,126,43,27,127,128,129,130,131,132,133,134],"search","deja search","never","error","ready","memory","re","decide","fix","design","you","done","reviewer","io","change","cli","merge","past",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":91,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":45},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[142,143,144,130,145,146,147,148,149,150,151,152,153,154,122,155,156,157,158,159],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":91,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":175,"publishedAt":45},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[166,169,172],{"categoryNo":167,"categoryName":168,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":170,"categoryName":171,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":173,"categoryName":174,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[162,176,177,178,179,180,181,156,182,123,183,184,185,186,27,187,188,189,190,191],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]