[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75B9EYGGEX2PVMB5M374NN9":3,"skill-same:01M75B9EYGGEX2PVMB5M374NN9":75},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M75B9EYGGEX2PVMB5M374NN9","hugging-science",null,"Use when the user is doing AI\u002FML work in a scientific domain — biology, chemistry, physics, astronomy, climate, genomics, materials science, medicine, ecology, energy, conservation, engineering, mathematics, scientific reasoning, drug discovery, protein design, weather modeling, theorem proving, single-cell, PDE solving, or anything similar. Hugging Science (huggingscience.co) is a curated catalog of scientific datasets, models, blog posts, and interactive Spaces; the `hugging-science` org on Hugging Face hosts community datasets, models, and demo Spaces. This skill helps you discover the right resource AND actually use it — loading datasets via `datasets`, running models via `transformers` or the HF Inference API, calling Spaces like BoltzGen via `gradio_client`, and citing blog posts for methodology. Trigger this skill whenever a user mentions a scientific ML task, asks for \"a dataset\u002Fmodel for X\" where X is a scientific topic, wants to fine-tune on scientific data, asks about protein \u002F molecule \u002F genome \u002F climate \u002F materials \u002F astronomy \u002F pathology \u002F weather ML, or needs AI tools for research — even if they never say \"Hugging Science\" explicitly. The catalog is purpose-built for LLM agents (it ships an `llms-full.txt`); prefer it over generic web search for these tasks.","Lord1Egypt\u002Fai-skillforge","Lord1Egypt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99746359?v=4","01M7592YDNT0XK9WJ0T2MQVPDN","Mohamed Mounir Ali AL Keshita","01M7597M9CBBVAPX1CYE1KFTSM",2,"MIT","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fai-skillforge\u002Fblob\u002Fmain\u002Fjs\u002Fskills\u002Fscientific\u002Fhugging-science\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: hugging-science\ndescription: Use when the user is doing AI\u002FML work in a scientific domain — biology, chemistry, physics, astronomy, climate, genomics, materials science, medicine, ecology, energy, conservation, engineering, mathematics, scientific reasoning, drug discovery, protein design, weather modeling, theorem proving, single-cell, PDE solving, or anything similar. Hugging Science (huggingscience.co) is a curated catalog of scientific datasets, models, blog posts, and interactive Spaces; the `hugging-science` org on Hugging Face hosts community datasets, models, and demo Spaces. This skill helps you discover the right resource AND actually use it — loading datasets via `datasets`, running models via `transformers` or the HF Inference API, calling Spaces like BoltzGen via `gradio_client`, and citing blog posts for methodology. Trigger this skill whenever a user mentions a scientific ML task, asks for \"a dataset\u002Fmodel for X\" where X is a scientific topic, wants to fine-tune on scientific data, asks about protein \u002F molecule \u002F genome \u002F climate \u002F materials \u002F astronomy \u002F pathology \u002F weather ML, or needs AI tools for research — even if they never say \"Hugging Science\" explicitly. The catalog is purpose-built for LLM agents (it ships an `llms-full.txt`); prefer it over generic web search for these tasks.\nmetadata:\n    skill-author: Lord1Egypt\n---\n\n# Hugging Science\n\nHugging Science is a curated, LLM-friendly index of scientific datasets, models, blog posts, and interactive demos for ML researchers. Use it when a scientific ML question lands in front of you — it's much higher signal than generic search and the entries are pre-filtered for quality and openness.\n\nThere are two related surfaces, and you should use both:\n\n- **The catalog at `huggingscience.co`** — a static, parseable index of resources across 17 scientific domains. It exposes `llms.txt` (compact), `llms-full.txt` (full content), and `topics\u002F\u003Cslug>.md` (per-domain). These are markdown files designed to be fetched and read.\n- **The `hugging-science` Hugging Face organization** — `huggingface.co\u002Fhugging-science` — community-submitted datasets, a few models, and ~27 interactive Spaces (notably BoltzGen for protein\u002Fbinder design, Dataset Quest for submissions, and Science Release Heatmap for ecosystem visualization).\n\nThe catalog *points to* resources hosted on the broader Hugging Face Hub. So an entry like `arcinstitute\u002Fopengenome2` is a regular HF dataset that you load with the `datasets` library; an entry like `facebook\u002Fesm2_t33_650M_UR50D` is a regular HF model you load with `transformers`. The catalog's job is curation and discovery; usage goes through standard Hugging Face APIs.\n\n## When to use this skill\n\nEngage this skill when the user's task involves AI\u002FML applied to science. Common signals:\n\n- Names a scientific domain (protein, genome, molecule, crystal, weather, climate, galaxy, EEG, microbiome, pathology, plasma, …)\n- Asks \"is there a dataset\u002Fmodel for X\" where X is scientific\n- Wants to fine-tune on scientific data, evaluate on scientific benchmarks, or reproduce a scientific ML paper\n- Asks about specific known scientific models (Evo-2, ESM2, BoltzGen, Nucleotide Transformer, AlphaFold-derived, etc.)\n- Needs an interactive demo for a scientific task (binder design, theorem proving, etc.)\n\nIf the task is generic ML (recommendation systems, chatbot RAG, vision on cats and dogs), this skill is **not** the right tool — defer to general HF Hub knowledge instead.\n\n## Core workflow\n\nMost invocations follow this five-step loop. Don't skip discovery — the value of Hugging Science is that it has already filtered hundreds of resources down to high-signal picks per domain.\n\n### 1. Identify the domain(s)\n\nMap the user's task to one or more of the 17 topic slugs:\n\n`astronomy` · `benchmark` · `biology` · `biotechnology` · `chemistry` · `climate` · `conservation` · `earth-science` · `ecology` · `energy` · `engineering` · `genomics` · `materials-science` · `mathematics` · `medicine` · `physics` · `scientific-reasoning`\n\nSome tasks span multiple topics (e.g., drug discovery → `chemistry` + `biology` + `medicine`). Fetch each relevant topic.\n\n### 2. Fetch the relevant catalog content\n\nUse the bundled script for clean, structured access:\n\n```bash\npython scripts\u002Ffetch_catalog.py topic biology\npython scripts\u002Ffetch_catalog.py topic materials-science --filter models\npython scripts\u002Ffetch_catalog.py search \"protein language model\"\npython scripts\u002Ffetch_catalog.py all     # full llms-full.txt\n```\n\nYou can also fetch the raw markdown directly:\n\n- `https:\u002F\u002Fhuggingscience.co\u002Fllms.txt` — compact index\n- `https:\u002F\u002Fhuggingscience.co\u002Fllms-full.txt` — every entry, every domain\n- `https:\u002F\u002Fhuggingscience.co\u002Ftopics\u002F\u003Cslug>.md` — one domain (slug is hyphenated, e.g. `materials-science.md`, `earth-science.md`, `scientific-reasoning.md`)\n\nEach entry is a markdown block with `Type`, `Tags`, `HuggingFace` URL (or `Link` for blogs), and a one-line description. See `references\u002Ftopics-and-slugs.md` for the entry schema and slug list.\n\n### 3. Pick the right resource(s)\n\nRead the descriptions and tags. Match to the user's task with judgment, not keyword overlap. Things to weigh:\n\n- **Scale fit** — Evo-2 40B is overkill for a quick sequence classification on a laptop; ESM2 35M might be perfect.\n- **License and access** — most are open, but check the underlying HF model card.\n- **Modality alignment** — DNA vs. protein vs. SMILES vs. crystal structure; many \"biology\" models are not interchangeable.\n- **Recency \u002F supersession** — if both an older and newer entry cover the same task, prefer newer unless there's a reason not to.\n\nIf you're not sure which resource to pick, briefly present the top 2–3 candidates to the user with their tradeoffs, then proceed once they choose. Don't pick silently when the choice materially changes the work.\n\nFor domain-specific go-to picks (the \"if in doubt, start here\" entries), see `references\u002Fflagship-resources.md`.\n\n### 4. Use the resource\n\nThe mechanics depend on resource type. Read the matching reference file before writing code:\n\n- **Datasets** → `references\u002Fusing-datasets.md` — loading via `datasets`, streaming for huge corpora, common columns, splits\n- **Models** → `references\u002Fusing-models.md` — local `transformers`, Hugging Face Inference API, Inference Providers for very large models, GPU sizing\n- **Spaces (interactive demos)** → `references\u002Fusing-spaces.md` — `gradio_client` pattern with a worked BoltzGen example\n\nThe reference files are short and focused. If you're already fluent in the relevant API, skim; if not, read fully before writing code. The patterns are different from generic HF usage in a few important places (e.g., `trust_remote_code` requirements, scientific-data dtype gotchas).\n\n### 5. Cite the methodology\n\nWhen the catalog has a blog post matching the task (`Type: blog` or in the Blog Posts section of a topic file), include its URL when you explain your approach to the user. Methodology blogs are written by the dataset\u002Fmodel authors and answer \"why this design\" questions that model cards usually skip. Treat them like citations — a one-line \"see \u003Clink> for the methodology behind X\" is plenty.\n\n## Authentication: HF_TOKEN\n\nMany catalog resources are gated (clinical data, large foundation models, private Spaces). Authenticate via the `HF_TOKEN` environment variable.\n\n**Load `HF_TOKEN` from a `.env` file when available** — that's where the user keeps secrets. Use `python-dotenv` at the top of any script that hits the HF API:\n\n```python\nfrom dotenv import load_dotenv\nload_dotenv()    # picks up HF_TOKEN from .env in cwd or any parent dir\n```\n\nIf `.env` doesn't exist or doesn't define `HF_TOKEN`, fall back gracefully — many resources are public and work without it. Don't hard-code tokens, don't echo them, and don't suggest `huggingface-cli login` as the primary path; the user prefers `.env`.\n\nThe `.env` file should contain a line like:\n\n```\nHF_TOKEN=hf_...\n```\n\nIf you're creating a new project, also add `.env` to `.gitignore` if it isn't already there.\n\n## A few important things to remember\n\n**The catalog is curated, not exhaustive.** If a user needs a specific resource and Hugging Science doesn't list it, that doesn't mean it doesn't exist on HF Hub. Search HF Hub directly as a fallback. But always *start* with the catalog when the domain matches — the curation is the value.\n\n**The entries are pointers.** Don't try to \"use Hugging Science\" as if it were an API. There is no Hugging Science inference endpoint. Every actionable resource lives on HF Hub or as a HF Space, and you use it via the standard HF tooling.\n\n**Many scientific models require `trust_remote_code=True`.** Custom architectures (Evo-2, many genomics\u002Fmaterials models) ship custom modeling code. This is normal in this ecosystem. Pass the flag and inform the user.\n\n**Scientific datasets are often large and weirdly-shaped.** Genomics corpora can be billions of tokens; cosmology images can be hundreds of GB; materials datasets contain non-standard objects (crystal structures, graphs). Use streaming (`streaming=True` on `load_dataset`) by default for anything claimed to be over a few GB, and inspect schema before assuming columns.\n\n**Spaces are great for one-off scientific generations.** If the user wants to design a binder for a target protein or run inference on a hosted model demo, calling the Space via `gradio_client` is faster and cheaper than spinning up the model locally. Check `references\u002Fusing-spaces.md` first — `huggingface.co\u002Fhugging-science` has ~27 of these.\n\n**The catalog itself may evolve.** Entries get added regularly; occasionally entries change slugs. If a URL 404s, refetch the topic file or `llms.txt` to get the current state — don't paper over the failure.\n\n## Bundled resources\n\n- `scripts\u002Ffetch_catalog.py` — fetch and filter catalog content. Run with `--help` for full usage. Use this in preference to ad-hoc WebFetch calls when you need structured access.\n- `references\u002Ftopics-and-slugs.md` — exact topic slugs, what each covers, and the entry schema.\n- `references\u002Fusing-datasets.md` — patterns and gotchas for loading scientific datasets.\n- `references\u002Fusing-models.md` — running scientific models locally, via Inference API, or via Inference Providers.\n- `references\u002Fusing-spaces.md` — calling HF Spaces (notably BoltzGen) programmatically with `gradio_client`.\n- `references\u002Fflagship-resources.md` — go-to dataset\u002Fmodel picks per domain when the user wants a sensible default.\n","# Hugging Science\n\nHugging Science is a curated, LLM-friendly index of scientific datasets, models, blog posts, and interactive demos for ML researchers. Use it when a scientific ML question lands in front of you — it's much higher signal than generic search and the entries are pre-filtered for quality and openness.\n\nThere are two related surfaces, and you should use both:\n\n- **The catalog at `huggingscience.co`** — a static, parseable index of resources across 17 scientific domains. It exposes `llms.txt` (compact), `llms-full.txt` (full content), and `topics\u002F\u003Cslug>.md` (per-domain). These are markdown files designed to be fetched and read.\n- **The `hugging-science` Hugging Face organization** — `huggingface.co\u002Fhugging-science` — community-submitted datasets, a few models, and ~27 interactive Spaces (notably BoltzGen for protein\u002Fbinder design, Dataset Quest for submissions, and Science Release Heatmap for ecosystem visualization).\n\nThe catalog *points to* resources hosted on the broader Hugging Face Hub. So an entry like `arcinstitute\u002Fopengenome2` is a regular HF dataset that you load with the `datasets` library; an entry like `facebook\u002Fesm2_t33_650M_UR50D` is a regular HF model you load with `transformers`. The catalog's job is curation and discovery; usage goes through standard Hugging Face APIs.\n\n## When to use this skill\n\nEngage this skill when the user's task involves AI\u002FML applied to science. Common signals:\n\n- Names a scientific domain (protein, genome, molecule, crystal, weather, climate, galaxy, EEG, microbiome, pathology, plasma, …)\n- Asks \"is there a dataset\u002Fmodel for X\" where X is scientific\n- Wants to fine-tune on scientific data, evaluate on scientific benchmarks, or reproduce a scientific ML paper\n- Asks about specific known scientific models (Evo-2, ESM2, BoltzGen, Nucleotide Transformer, AlphaFold-derived, etc.)\n- Needs an interactive demo for a scientific task (binder design, theorem proving, etc.)\n\nIf the task is generic ML (recommendation systems, chatbot RAG, vision on cats and dogs), this skill is **not** the right tool — defer to general HF Hub knowledge instead.\n\n## Core workflow\n\nMost invocations follow this five-step loop. Don't skip discovery — the value of Hugging Science is that it has already filtered hundreds of resources down to high-signal picks per domain.\n\n### 1. Identify the domain(s)\n\nMap the user's task to one or more of the 17 topic slugs:\n\n`astronomy` · `benchmark` · `biology` · `biotechnology` · `chemistry` · `climate` · `conservation` · `earth-science` · `ecology` · `energy` · `engineering` · `genomics` · `materials-science` · `mathematics` · `medicine` · `physics` · `scientific-reasoning`\n\nSome tasks span multiple topics (e.g., drug discovery → `chemistry` + `biology` + `medicine`). Fetch each relevant topic.\n\n### 2. Fetch the relevant catalog content\n\nUse the bundled script for clean, structured access:\n\n```bash\npython scripts\u002Ffetch_catalog.py topic biology\npython scripts\u002Ffetch_catalog.py topic materials-science --filter models\npython scripts\u002Ffetch_catalog.py search \"protein language model\"\npython scripts\u002Ffetch_catalog.py all     # full llms-full.txt\n```\n\nYou can also fetch the raw markdown directly:\n\n- `https:\u002F\u002Fhuggingscience.co\u002Fllms.txt` — compact index\n- `https:\u002F\u002Fhuggingscience.co\u002Fllms-full.txt` — every entry, every domain\n- `https:\u002F\u002Fhuggingscience.co\u002Ftopics\u002F\u003Cslug>.md` — one domain (slug is hyphenated, e.g. `materials-science.md`, `earth-science.md`, `scientific-reasoning.md`)\n\nEach entry is a markdown block with `Type`, `Tags`, `HuggingFace` URL (or `Link` for blogs), and a one-line description. See `references\u002Ftopics-and-slugs.md` for the entry schema and slug list.\n\n### 3. Pick the right resource(s)\n\nRead the descriptions and tags. Match to the user's task with judgment, not keyword overlap. Things to weigh:\n\n- **Scale fit** — Evo-2 40B is overkill for a quick sequence classification on a laptop; ESM2 35M might be perfect.\n- **License and access** — most are open, but check the underlying HF model card.\n- **Modality alignment** — DNA vs. protein vs. SMILES vs. crystal structure; many \"biology\" models are not interchangeable.\n- **Recency \u002F supersession** — if both an older and newer entry cover the same task, prefer newer unless there's a reason not to.\n\nIf you're not sure which resource to pick, briefly present the top 2–3 candidates to the user with their tradeoffs, then proceed once they choose. Don't pick silently when the choice materially changes the work.\n\nFor domain-specific go-to picks (the \"if in doubt, start here\" entries), see `references\u002Fflagship-resources.md`.\n\n### 4. Use the resource\n\nThe mechanics depend on resource type. Read the matching reference file before writing code:\n\n- **Datasets** → `references\u002Fusing-datasets.md` — loading via `datasets`, streaming for huge corpora, common columns, splits\n- **Models** → `references\u002Fusing-models.md` — local `transformers`, Hugging Face Inference API, Inference Providers for very large models, GPU sizing\n- **Spaces (interactive demos)** → `references\u002Fusing-spaces.md` — `gradio_client` pattern with a worked BoltzGen example\n\nThe reference files are short and focused. If you're already fluent in the relevant API, skim; if not, read fully before writing code. The patterns are different from generic HF usage in a few important places (e.g., `trust_remote_code` requirements, scientific-data dtype gotchas).\n\n### 5. Cite the methodology\n\nWhen the catalog has a blog post matching the task (`Type: blog` or in the Blog Posts section of a topic file), include its URL when you explain your approach to the user. Methodology blogs are written by the dataset\u002Fmodel authors and answer \"why this design\" questions that model cards usually skip. Treat them like citations — a one-line \"see \u003Clink> for the methodology behind X\" is plenty.\n\n## Authentication: HF_TOKEN\n\nMany catalog resources are gated (clinical data, large foundation models, private Spaces). Authenticate via the `HF_TOKEN` environment variable.\n\n**Load `HF_TOKEN` from a `.env` file when available** — that's where the user keeps secrets. Use `python-dotenv` at the top of any script that hits the HF API:\n\n```python\nfrom dotenv import load_dotenv\nload_dotenv()    # picks up HF_TOKEN from .env in cwd or any parent dir\n```\n\nIf `.env` doesn't exist or doesn't define `HF_TOKEN`, fall back gracefully — many resources are public and work without it. Don't hard-code tokens, don't echo them, and don't suggest `huggingface-cli login` as the primary path; the user prefers `.env`.\n\nThe `.env` file should contain a line like:\n\n```\nHF_TOKEN=hf_...\n```\n\nIf you're creating a new project, also add `.env` to `.gitignore` if it isn't already there.\n\n## A few important things to remember\n\n**The catalog is curated, not exhaustive.** If a user needs a specific resource and Hugging Science doesn't list it, that doesn't mean it doesn't exist on HF Hub. Search HF Hub directly as a fallback. But always *start* with the catalog when the domain matches — the curation is the value.\n\n**The entries are pointers.** Don't try to \"use Hugging Science\" as if it were an API. There is no Hugging Science inference endpoint. Every actionable resource lives on HF Hub or as a HF Space, and you use it via the standard HF tooling.\n\n**Many scientific models require `trust_remote_code=True`.** Custom architectures (Evo-2, many genomics\u002Fmaterials models) ship custom modeling code. This is normal in this ecosystem. Pass the flag and inform the user.\n\n**Scientific datasets are often large and weirdly-shaped.** Genomics corpora can be billions of tokens; cosmology images can be hundreds of GB; materials datasets contain non-standard objects (crystal structures, graphs). Use streaming (`streaming=True` on `load_dataset`) by default for anything claimed to be over a few GB, and inspect schema before assuming columns.\n\n**Spaces are great for one-off scientific generations.** If the user wants to design a binder for a target protein or run inference on a hosted model demo, calling the Space via `gradio_client` is faster and cheaper than spinning up the model locally. Check `references\u002Fusing-spaces.md` first — `huggingface.co\u002Fhugging-science` has ~27 of these.\n\n**The catalog itself may evolve.** Entries get added regularly; occasionally entries change slugs. If a URL 404s, refetch the topic file or `llms.txt` to get the current state — don't paper over the failure.\n\n## Bundled resources\n\n- `scripts\u002Ffetch_catalog.py` — fetch and filter catalog content. Run with `--help` for full usage. Use this in preference to ad-hoc WebFetch calls when you need structured access.\n- `references\u002Ftopics-and-slugs.md` — exact topic slugs, what each covers, and the entry schema.\n- `references\u002Fusing-datasets.md` — patterns and gotchas for loading scientific datasets.\n- `references\u002Fusing-models.md` — running scientific models locally, via Inference API, or via Inference Providers.\n- `references\u002Fusing-spaces.md` — calling HF Spaces (notably BoltzGen) programmatically with `gradio_client`.\n- `references\u002Fflagship-resources.md` — go-to dataset\u002Fmodel picks per domain when the user wants a sensible default.\n",{"name":5,"metadata":24,"description":7},{"skill-author":9},"main","3f88e1b76af67701a6405069a542e21a997d2868","js\u002Fskills\u002Fscientific\u002Fhugging-science",0,"https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fai-skillforge","https:\u002F\u002Fgithub.com\u002FLord1Egypt","Unbreakable. Unstoppable. Unmatched⚡.\r\n Speaker of machine tongues 🤖  | World-builder of decentralized dreams 🌐 | Defender of the digital realm🛡️.","2026-06-05 10:16:24",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Lord1Egypt\u002Fai-skillforge --skill hugging-science",{"tool":39,"command":40},"bunx","bunx skills add Lord1Egypt\u002Fai-skillforge --skill hugging-science",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Lord1Egypt\u002Fai-skillforge --skill hugging-science","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fai-skillforge\u002Fblob\u002Fmain\u002Fjs\u002Fskills\u002Fscientific\u002Fhugging-science\u002FSKILL.md",true,[47,53,57,61,65,69],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fflagship-resources.md","REFERENCE","参考文档",4458,"https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fai-skillforge\u002Fblob\u002Fmain\u002Fjs\u002Fskills\u002Fscientific\u002Fhugging-science\u002Freferences\u002Fflagship-resources.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Ftopics-and-slugs.md",3971,"https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fai-skillforge\u002Fblob\u002Fmain\u002Fjs\u002Fskills\u002Fscientific\u002Fhugging-science\u002Freferences\u002Ftopics-and-slugs.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fusing-datasets.md",4910,"https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fai-skillforge\u002Fblob\u002Fmain\u002Fjs\u002Fskills\u002Fscientific\u002Fhugging-science\u002Freferences\u002Fusing-datasets.md",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fusing-models.md",5659,"https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fai-skillforge\u002Fblob\u002Fmain\u002Fjs\u002Fskills\u002Fscientific\u002Fhugging-science\u002Freferences\u002Fusing-models.md",{"path":66,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fusing-spaces.md",4935,"https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fai-skillforge\u002Fblob\u002Fmain\u002Fjs\u002Fskills\u002Fscientific\u002Fhugging-science\u002Freferences\u002Fusing-spaces.md",{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"scripts\u002Ffetch_catalog.py","SCRIPT","脚本",10717,"https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fai-skillforge\u002Fblob\u002Fmain\u002Fjs\u002Fskills\u002Fscientific\u002Fhugging-science\u002Fscripts\u002Ffetch_catalog.py",[76,83,90,97,104,111],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M75GWTHWA52GYQKS347FF6CD","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fai-skillforge\u002Fblob\u002Fmain\u002Fskills\u002Fscientific\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M75GW9FBP9NAFBSNVJ23RHSX","what-if-oracle","Run structured What-If scenario analysis with multi-branch possibility exploration. Use this skill when the user asks speculative questions like \"what if...\", \"what would happen if...\", \"what are the possibilities\", \"explore scenarios\", \"scenario analysis\", \"possibility space\", \"what could go wrong\", \"best case \u002F worst case\", \"risk analysis\", \"contingency planning\", \"strategic options\", or any question about uncertain futures. Also trigger when the user faces a fork-in-the-road decision, wants to stress-test an idea, or needs to think through consequences before committing.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fai-skillforge\u002Fblob\u002Fmain\u002Fskills\u002Fscientific\u002Fwhat-if-oracle\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M75GW351MZZQ1V7207PDCX5D","venue-templates","Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fai-skillforge\u002Fblob\u002Fmain\u002Fskills\u002Fscientific\u002Fvenue-templates\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M75GVYGMAZDV2NHWSV6PP6TK","vaex","Use this skill for processing and analyzing large tabular datasets (billions of rows) that exceed available RAM. Vaex excels at out-of-core DataFrame operations, lazy evaluation, fast aggregations, efficient visualization of big data, and machine learning on large datasets. Apply when users need to work with large CSV\u002FHDF5\u002FArrow\u002FParquet files, perform fast statistics on massive datasets, create visualizations of big data, or build ML pipelines that do not fit in memory.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fai-skillforge\u002Fblob\u002Fmain\u002Fskills\u002Fscientific\u002Fvaex\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M75GVS0ADH3DZ3QB564EVYC9","usfiscaldata","Query the U.S. Treasury Fiscal Data API for federal financial data including national debt, government spending, revenue, interest rates, exchange rates, and savings bonds. Access 54 datasets and 182 data tables with no API key required. Use when working with U.S. federal fiscal data, national debt tracking (Debt to the Penny), Daily Treasury Statements, Monthly Treasury Statements, Treasury securities auctions, interest rates on Treasury securities, foreign exchange rates, savings bonds, or any U.S. government financial statistics.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fai-skillforge\u002Fblob\u002Fmain\u002Fskills\u002Fscientific\u002Fusfiscaldata\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":19},"01M75GVDTBSXRQ4Q11RVJQC56M","treatment-plans","Generate concise (3-4 page), focused medical treatment plans in LaTeX\u002FPDF format for all clinical specialties. Supports general medical treatment, rehabilitation therapy, mental health care, chronic disease management, perioperative care, and pain management. Includes SMART goal frameworks, evidence-based interventions with minimal text citations, regulatory compliance (HIPAA), and professional formatting. Prioritizes brevity and clinical actionability.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fai-skillforge\u002Fblob\u002Fmain\u002Fskills\u002Fscientific\u002Ftreatment-plans\u002FSKILL.md",[],[]]