[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BCZBKY8NAZWR6F0V50BVSA":3,"skill-same:01M7BCZBKY8NAZWR6F0V50BVSA":62},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":13,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M7BCZBKY8NAZWR6F0V50BVSA","render-cron-jobs",null,"Configures and troubleshoots scheduled tasks on Render using cron job services. Use when the user needs to run something on a schedule, write a cron expression, set up a periodic job, migrate from Heroku Scheduler, choose between cron jobs and background workers, or fix a cron that isn't firing. Trigger terms: cron job, scheduled task, periodic job, cron expression, schedule, run every, timer, Heroku Scheduler migration.","vikasvardhanv\u002Fjerry_skills","vikasvardhanv","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99010657?v=4","01M7B2B0VN78W7529RQX5BR6DZ","01M7B2B0WDNTXJHRK3QNPNWRP6",0,"MIT","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fopenai\u002Fplugins\u002Frender\u002Fskills\u002Frender-cron-jobs\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: render-cron-jobs\ndescription: >-\n  Configures and troubleshoots scheduled tasks on Render using cron job\n  services. Use when the user needs to run something on a schedule, write a\n  cron expression, set up a periodic job, migrate from Heroku Scheduler,\n  choose between cron jobs and background workers, or fix a cron that isn't\n  firing.\n  Trigger terms: cron job, scheduled task, periodic job, cron expression,\n  schedule, run every, timer, Heroku Scheduler migration.\nlicense: MIT\ncompatibility: Render cron job services\nmetadata:\n  author: Render\n  version: \"1.0.0\"\n  category: compute\n---\n\n# Render Cron Jobs\n\nThis skill covers **Cron Job** services on Render: how schedules run, what the platform guarantees, and how they differ from workers and workflows. Pair it with Blueprint and deploy skills when authoring `render.yaml` or Dashboard settings.\n\n## When to Use\n\n- **Scheduled** work that **starts on a cron**, runs a command, and **exits** when finished\n- Choosing between **cron**, **background worker**, or **workflow** for periodic or long-running jobs\n- **Blueprint** fields for `type: cron`, `schedule`, and commands\n- **Constraints**: no disk, single concurrent run, 12-hour max duration, private-network **outbound** only\n- **UTC** scheduling pitfalls (expressions are **not** local time)\n\nExpression cheat sheets, framework `startCommand` examples, and Heroku Scheduler migration mapping live under `references\u002F`.\n\n## Configuration\n\n- **Schedule**: a **cron expression evaluated in UTC**, not the team’s local timezone. All times in the Dashboard and Blueprints are UTC.\n- **Command**: any valid **Linux shell command** or **bash script** path. The process must **exit** when work is done—**billing is based on run duration** (prorated by the second).\n- **Source**:\n  - **Git repository** — Render **builds on push** (same deploy model as other repo-backed services); the built artifact runs on each scheduled invocation.\n  - **Prebuilt Docker image** — the image is **pulled before each run** and is **not retained between runs** (no warm cache of the image layer set across invocations in the same way as a long-lived service).\n\n## Constraints\n\n- **No persistent disk** — cron job services **cannot** provision or attach Render persistent disks; plan for object storage or databases instead.\n- **Single-run guarantee** — at most **one active run** per cron service at a time. A new scheduled tick does not start a second overlapping instance.\n- **Maximum run length**: **12 hours** per invocation.\n- **Pricing**: **$1\u002Fmonth minimum** per cron job service; usage is **prorated by the second** beyond plan\u002Fminimum rules that apply to your account.\n- **Private network**: cron jobs **can send** traffic **to** other services on the private network; they **cannot receive** inbound private-network connections (no internal hostname for accepting traffic from other services).\n\n## Execution Behavior\n\n- **Manual “Trigger Run”** while a run is **active**: Render **cancels** the active run, then **starts** a new one.\n- **New Git build \u002F deploy** does **not** affect a run already **in progress**—the in-flight process keeps using the revision it started with until it exits.\n- **Docker-based crons**: the image is **pulled fresh for each run**; do not assume layer or image reuse across invocations like a continuously running container.\n- **UTC everywhere**: cron expressions and “midnight” in docs mean **UTC**. A common mistake is copying a local-time schedule into the expression without converting to UTC.\n\n## Cron vs Worker vs Workflow\n\n| Need | Use | Why |\n|------|-----|-----|\n| Periodic task **under 12h** | **Cron Job** | Scheduled, simple, exits when done |\n| **Continuous** job processing | **Background Worker** | Always running, polls a queue |\n| Periodic but **over 12h** | **Background Worker** | No 12h cron run ceiling |\n| **Scheduled parallel** compute | **Cron Job + Workflow** | Cron triggers workflow runs on a schedule; workflows fan out or orchestrate parallel steps |\n\n## Blueprint Configuration\n\nCron services use **`type: cron`** with a **`schedule`** and the usual build\u002Fstart and env wiring:\n\n```yaml\nservices:\n  - type: cron\n    name: nightly-cleanup\n    schedule: \"0 * * * *\" # hourly at minute 0 — must be quoted in YAML\n    buildCommand: pip install -r requirements.txt\n    startCommand: python cleanup.py\n    envVars:\n      - key: DATABASE_URL\n        fromDatabase:\n          name: my-db\n          property: connectionString\n```\n\n- **`schedule`**: standard five-field cron (`minute hour day-of-month month day-of-week`), **UTC**.\n- **`buildCommand`** \u002F **`startCommand`**: same roles as other non-Docker services; Docker images use image + start command as configured for image-backed crons.\n- **`envVars`**: same patterns as web services and workers (secrets, linked databases, etc.).\n\n**YAML note**: the `schedule` value **must be quoted** so characters like `*` are not parsed as YAML aliases or flow syntax.\n\n## Common Patterns\n\n- **Database cleanup** — archive or delete stale rows on a schedule\n- **Report generation** — build CSV\u002FPDF and upload to object storage or email\n- **External API sync** — pull or push batches on an interval\n- **Cache warming** — hit endpoints or rebuild caches before peak traffic\n- **Scheduled emails** — digest or reminder sends driven by cron + mail\u002FAPI\n\n## References\n\n| Topic | File |\n|--------|------|\n| Expression examples, framework commands, errors, env vars | `references\u002Fcron-patterns.md` |\n| Heroku Scheduler → Render mapping, blueprint example | `references\u002Fmigration-from-scheduler.md` |\n\n## Related Skills\n\n- **render-deploy** — First-time deploy, service creation, Dashboard flow\n- **render-blueprints** — Full `render.yaml` schema, previews, common mistakes\n- **render-background-workers** — Long-lived processes, queues, no 12h cap\n- **render-workflows** — Orchestrated and parallel jobs, often triggered on a schedule from cron\n","# Render Cron Jobs\n\nThis skill covers **Cron Job** services on Render: how schedules run, what the platform guarantees, and how they differ from workers and workflows. Pair it with Blueprint and deploy skills when authoring `render.yaml` or Dashboard settings.\n\n## When to Use\n\n- **Scheduled** work that **starts on a cron**, runs a command, and **exits** when finished\n- Choosing between **cron**, **background worker**, or **workflow** for periodic or long-running jobs\n- **Blueprint** fields for `type: cron`, `schedule`, and commands\n- **Constraints**: no disk, single concurrent run, 12-hour max duration, private-network **outbound** only\n- **UTC** scheduling pitfalls (expressions are **not** local time)\n\nExpression cheat sheets, framework `startCommand` examples, and Heroku Scheduler migration mapping live under `references\u002F`.\n\n## Configuration\n\n- **Schedule**: a **cron expression evaluated in UTC**, not the team’s local timezone. All times in the Dashboard and Blueprints are UTC.\n- **Command**: any valid **Linux shell command** or **bash script** path. The process must **exit** when work is done—**billing is based on run duration** (prorated by the second).\n- **Source**:\n  - **Git repository** — Render **builds on push** (same deploy model as other repo-backed services); the built artifact runs on each scheduled invocation.\n  - **Prebuilt Docker image** — the image is **pulled before each run** and is **not retained between runs** (no warm cache of the image layer set across invocations in the same way as a long-lived service).\n\n## Constraints\n\n- **No persistent disk** — cron job services **cannot** provision or attach Render persistent disks; plan for object storage or databases instead.\n- **Single-run guarantee** — at most **one active run** per cron service at a time. A new scheduled tick does not start a second overlapping instance.\n- **Maximum run length**: **12 hours** per invocation.\n- **Pricing**: **$1\u002Fmonth minimum** per cron job service; usage is **prorated by the second** beyond plan\u002Fminimum rules that apply to your account.\n- **Private network**: cron jobs **can send** traffic **to** other services on the private network; they **cannot receive** inbound private-network connections (no internal hostname for accepting traffic from other services).\n\n## Execution Behavior\n\n- **Manual “Trigger Run”** while a run is **active**: Render **cancels** the active run, then **starts** a new one.\n- **New Git build \u002F deploy** does **not** affect a run already **in progress**—the in-flight process keeps using the revision it started with until it exits.\n- **Docker-based crons**: the image is **pulled fresh for each run**; do not assume layer or image reuse across invocations like a continuously running container.\n- **UTC everywhere**: cron expressions and “midnight” in docs mean **UTC**. A common mistake is copying a local-time schedule into the expression without converting to UTC.\n\n## Cron vs Worker vs Workflow\n\n| Need | Use | Why |\n|------|-----|-----|\n| Periodic task **under 12h** | **Cron Job** | Scheduled, simple, exits when done |\n| **Continuous** job processing | **Background Worker** | Always running, polls a queue |\n| Periodic but **over 12h** | **Background Worker** | No 12h cron run ceiling |\n| **Scheduled parallel** compute | **Cron Job + Workflow** | Cron triggers workflow runs on a schedule; workflows fan out or orchestrate parallel steps |\n\n## Blueprint Configuration\n\nCron services use **`type: cron`** with a **`schedule`** and the usual build\u002Fstart and env wiring:\n\n```yaml\nservices:\n  - type: cron\n    name: nightly-cleanup\n    schedule: \"0 * * * *\" # hourly at minute 0 — must be quoted in YAML\n    buildCommand: pip install -r requirements.txt\n    startCommand: python cleanup.py\n    envVars:\n      - key: DATABASE_URL\n        fromDatabase:\n          name: my-db\n          property: connectionString\n```\n\n- **`schedule`**: standard five-field cron (`minute hour day-of-month month day-of-week`), **UTC**.\n- **`buildCommand`** \u002F **`startCommand`**: same roles as other non-Docker services; Docker images use image + start command as configured for image-backed crons.\n- **`envVars`**: same patterns as web services and workers (secrets, linked databases, etc.).\n\n**YAML note**: the `schedule` value **must be quoted** so characters like `*` are not parsed as YAML aliases or flow syntax.\n\n## Common Patterns\n\n- **Database cleanup** — archive or delete stale rows on a schedule\n- **Report generation** — build CSV\u002FPDF and upload to object storage or email\n- **External API sync** — pull or push batches on an interval\n- **Cache warming** — hit endpoints or rebuild caches before peak traffic\n- **Scheduled emails** — digest or reminder sends driven by cron + mail\u002FAPI\n\n## References\n\n| Topic | File |\n|--------|------|\n| Expression examples, framework commands, errors, env vars | `references\u002Fcron-patterns.md` |\n| Heroku Scheduler → Render mapping, blueprint example | `references\u002Fmigration-from-scheduler.md` |\n\n## Related Skills\n\n- **render-deploy** — First-time deploy, service creation, Dashboard flow\n- **render-blueprints** — Full `render.yaml` schema, previews, common mistakes\n- **render-background-workers** — Long-lived processes, queues, no 12h cap\n- **render-workflows** — Orchestrated and parallel jobs, often triggered on a schedule from cron\n",{"name":5,"license":14,"metadata":23,"description":7,"compatibility":27},{"author":24,"version":25,"category":26},"Render","1.0.0","compute","Render cron job services","main","1eb986d0b0ecc180291597e08eb5a58288843536","skills\u002Fopenai\u002Fplugins\u002Frender\u002Fskills\u002Frender-cron-jobs","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv","2026-08-25 13:16:33",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add vikasvardhanv\u002Fjerry_skills --skill render-cron-jobs",{"tool":40,"command":41},"bunx","bunx skills add vikasvardhanv\u002Fjerry_skills --skill render-cron-jobs",{"tool":43,"command":44},"pnpm","pnpm dlx skills add vikasvardhanv\u002Fjerry_skills --skill render-cron-jobs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fopenai\u002Fplugins\u002Frender\u002Fskills\u002Frender-cron-jobs\u002FSKILL.md",true,[48,54,58],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"agents\u002Fopenai.yaml","REFERENCE","参考文档",210,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fopenai\u002Fplugins\u002Frender\u002Fskills\u002Frender-cron-jobs\u002Fagents\u002Fopenai.yaml",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fcron-patterns.md",2674,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fopenai\u002Fplugins\u002Frender\u002Fskills\u002Frender-cron-jobs\u002Freferences\u002Fcron-patterns.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fmigration-from-scheduler.md",2749,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fopenai\u002Fplugins\u002Frender\u002Fskills\u002Frender-cron-jobs\u002Freferences\u002Fmigration-from-scheduler.md",[63,70,77,84,91,98],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M7BESR1CJ3H5SP9XM8KYJZ9W","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M7BES1YA6R97W7QPMFFM1PED","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M7BERNHYGY035AR00VRT03KE","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M7BERCK1EAKTWW7R436WAR0J","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":18},"01M7BEQZAZAQRTXFJRY7RHV3TY","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":18},"01M7BEQKJ45K31QK5VRAQSVJCJ","grants","NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance\u002FInnovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget\u002Fscope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fgrants\u002Fskills\u002Fgrants\u002FSKILL.md",[],[]]