[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74YG3147JV6FWA51NHFEKC3":3,"skill-same:01M74YG3147JV6FWA51NHFEKC3":55},{"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":31,"commitSha":32,"skillDirectory":33,"forksCount":34,"repositoryHtmlUrl":35,"repositoryHomepageUrl":36,"ownerHtmlUrl":37,"ownerBlogUrl":38,"ownerDescription":39,"updatedAt":40,"install":41,"resources":54},"01M74YG3147JV6FWA51NHFEKC3","cover-letter-to-editor",null,"Write journal submission cover letters, presubmission inquiries, transfer requests, and reviewer suggestion or exclusion lists that help a manuscript get past editorial triage. Use when submitting a paper to a journal, pitching a manuscript to an editor (presubmission enquiry), transferring after rejection, explaining a resubmission or appeal, or preparing the editor-facing parts of a submission such as the significance pitch, suggested reviewers and conflicts. Not for job or fellowship application letters.","KalarisLabs\u002Fresearch-agent-skills","KalarisLabs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F300878568?v=4","01M74Y7MT23GXXC56VM6TVSXZY","Kalarislabs","01M74Y7MTQM9REXZX4SNXWX95C",132,"MIT","https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fcover-letter-to-editor\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: cover-letter-to-editor\ndescription: Write journal submission cover letters, presubmission inquiries, transfer requests, and reviewer suggestion or exclusion lists that help a manuscript get past editorial triage. Use when submitting a paper to a journal, pitching a manuscript to an editor (presubmission enquiry), transferring after rejection, explaining a resubmission or appeal, or preparing the editor-facing parts of a submission such as the significance pitch, suggested reviewers and conflicts. Not for job or fellowship application letters.\nlicense: MIT\ncompatibility: No runtime dependencies.\nmetadata:\n  version: \"1.0\"\n  category: research-writing\n  maintainer: Kalaris Labs\n  author: Kalaris Labs (Sayan Chowdhury)\n  tags: cover letter, journal submission, editor, presubmission inquiry, suggested reviewers, desk rejection\n---\n\n# Cover Letters and Editor Communications\n\nAt selective journals an editor decides in minutes whether to send a paper to\nreview. The cover letter is your only direct pitch: why *this* journal's\nreaders need *this* result now. It does not summarize the abstract.\n\n## Before writing\n\nCollect: the journal's scope\u002Faims statement and article type; the main finding in\none sentence with its key number; 1-3 recent papers **in this journal** your work\nbuilds on or challenges; required declarations (see the journal's guide).\n\n## Structure (one page)\n\n1. **Opening**: manuscript title, article type, journal. One sentence.\n2. **The finding and why it matters**, 2-4 sentences: the problem, what you found (with the key number),\n   and what it changes. Written for a smart non-specialist editor.\n3. **Why this journal**: connect to the journal's readership and scope, and cite recent papers it\n   published if you extend or overturn them. Avoid flattery.\n4. **What is new vs. prior work**: one or two sentences, concrete (larger cohort, first causal\n   evidence, 10× faster, new mechanism).\n5. **Declarations** the journal asks for: not under consideration elsewhere, all authors approved,\n   preprint server and DOI if posted, competing interests, related manuscripts under review, data availability.\n6. **Reviewers**: suggested reviewers (name, institution, email, expertise, *no* conflicts: not\n   recent co-authors or same institution). Opposed reviewers with a brief, professional reason.\n7. Sign-off by the corresponding author with contact details.\n\n## Template\n\n```text\nDear Dr. [Editor surname],\n\nWe submit our manuscript \"[Title]\" for consideration as a [Article type] in [Journal].\n\n[Problem in one sentence]. Here we show that [main finding with key number], using [approach\nand scale]. This [resolves \u002F overturns \u002F enables] [specific consequence].\n\nThis work will interest [Journal]'s readers in [fields] because [reason]. It builds on\n[Author et al., Journal, Year], which [what they showed], by [what you add].\n\nThe manuscript has not been published and is not under consideration elsewhere. All authors\napproved the submission. A preprint is available at [server, DOI]. The authors declare [no\ncompeting interests \u002F the interests listed in the manuscript].\n\nSuggested reviewers: [Name, Institution, email: expertise]. [...]\nWe request that [Name] not review this manuscript due to [brief professional reason].\n\nSincerely,\n[Name, affiliation, email, ORCID]\n```\n\n## Variants\n\n- **Presubmission inquiry** (Nature Portfolio, PLOS Biology, Cell Press and others): abstract +\n  ~200-word pitch focused on significance. The editor answers \"would consider\" or \"not suitable\".\n- **Transfer after rejection**: mention the previous journal and decision. If reviews transfer,\n  summarize how you addressed them.\n- **Resubmission after reject-and-resubmit**: list the main changes and link to the full response\n  to reviewers (see `rebuttal-and-response-to-reviewers`).\n- **Appeal**: only for clear reviewer error or misunderstanding of central points. Be factual,\n  brief and specific, and offer additional evidence.\n\n## Don'ts\n\n- Don't repeat the abstract, or use hype (\"groundbreaking\", \"paradigm-shifting\").\n- Don't overclaim beyond the manuscript or bury required declarations.\n- Don't suggest reviewers with conflicts, or friends, or fabricated contacts. This is research misconduct.\n- Don't exceed one page unless the journal asks for more.\n\n## Related skills\n\n`abstract-and-title`, `rebuttal-and-response-to-reviewers`, `reproducibility-statement`,\njournal-format skills (`nature-portfolio`, `science-aaas`, `cell-press`, `plos`, ...), `venue-templates`.\n","# Cover Letters and Editor Communications\n\nAt selective journals an editor decides in minutes whether to send a paper to\nreview. The cover letter is your only direct pitch: why *this* journal's\nreaders need *this* result now. It does not summarize the abstract.\n\n## Before writing\n\nCollect: the journal's scope\u002Faims statement and article type; the main finding in\none sentence with its key number; 1-3 recent papers **in this journal** your work\nbuilds on or challenges; required declarations (see the journal's guide).\n\n## Structure (one page)\n\n1. **Opening**: manuscript title, article type, journal. One sentence.\n2. **The finding and why it matters**, 2-4 sentences: the problem, what you found (with the key number),\n   and what it changes. Written for a smart non-specialist editor.\n3. **Why this journal**: connect to the journal's readership and scope, and cite recent papers it\n   published if you extend or overturn them. Avoid flattery.\n4. **What is new vs. prior work**: one or two sentences, concrete (larger cohort, first causal\n   evidence, 10× faster, new mechanism).\n5. **Declarations** the journal asks for: not under consideration elsewhere, all authors approved,\n   preprint server and DOI if posted, competing interests, related manuscripts under review, data availability.\n6. **Reviewers**: suggested reviewers (name, institution, email, expertise, *no* conflicts: not\n   recent co-authors or same institution). Opposed reviewers with a brief, professional reason.\n7. Sign-off by the corresponding author with contact details.\n\n## Template\n\n```text\nDear Dr. [Editor surname],\n\nWe submit our manuscript \"[Title]\" for consideration as a [Article type] in [Journal].\n\n[Problem in one sentence]. Here we show that [main finding with key number], using [approach\nand scale]. This [resolves \u002F overturns \u002F enables] [specific consequence].\n\nThis work will interest [Journal]'s readers in [fields] because [reason]. It builds on\n[Author et al., Journal, Year], which [what they showed], by [what you add].\n\nThe manuscript has not been published and is not under consideration elsewhere. All authors\napproved the submission. A preprint is available at [server, DOI]. The authors declare [no\ncompeting interests \u002F the interests listed in the manuscript].\n\nSuggested reviewers: [Name, Institution, email: expertise]. [...]\nWe request that [Name] not review this manuscript due to [brief professional reason].\n\nSincerely,\n[Name, affiliation, email, ORCID]\n```\n\n## Variants\n\n- **Presubmission inquiry** (Nature Portfolio, PLOS Biology, Cell Press and others): abstract +\n  ~200-word pitch focused on significance. The editor answers \"would consider\" or \"not suitable\".\n- **Transfer after rejection**: mention the previous journal and decision. If reviews transfer,\n  summarize how you addressed them.\n- **Resubmission after reject-and-resubmit**: list the main changes and link to the full response\n  to reviewers (see `rebuttal-and-response-to-reviewers`).\n- **Appeal**: only for clear reviewer error or misunderstanding of central points. Be factual,\n  brief and specific, and offer additional evidence.\n\n## Don'ts\n\n- Don't repeat the abstract, or use hype (\"groundbreaking\", \"paradigm-shifting\").\n- Don't overclaim beyond the manuscript or bury required declarations.\n- Don't suggest reviewers with conflicts, or friends, or fabricated contacts. This is research misconduct.\n- Don't exceed one page unless the journal asks for more.\n\n## Related skills\n\n`abstract-and-title`, `rebuttal-and-response-to-reviewers`, `reproducibility-statement`,\njournal-format skills (`nature-portfolio`, `science-aaas`, `cell-press`, `plos`, ...), `venue-templates`.\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":30},{"tags":25,"author":26,"version":27,"category":28,"maintainer":29},"cover letter, journal submission, editor, presubmission inquiry, suggested reviewers, desk rejection","Kalaris Labs (Sayan Chowdhury)","1.0","research-writing","Kalaris Labs","No runtime dependencies.","main","29fe36d26127205057d5e0ed8425f6b0e9a8c13a","skills\u002Fcover-letter-to-editor",16,"https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills","https:\u002F\u002Fdocs.kalarislabs.com\u002Fresearch-agent-skills","https:\u002F\u002Fgithub.com\u002FKalarisLabs","kalarislabs.com","Applied AI lab building the infrastructure for the agentic era","2026-11-14 17:49:08",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add KalarisLabs\u002Fresearch-agent-skills --skill cover-letter-to-editor",{"tool":47,"command":48},"bunx","bunx skills add KalarisLabs\u002Fresearch-agent-skills --skill cover-letter-to-editor",{"tool":50,"command":51},"pnpm","pnpm dlx skills add KalarisLabs\u002Fresearch-agent-skills --skill cover-letter-to-editor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fcover-letter-to-editor\u002FSKILL.md",true,[],[56,63,70,77,84,91],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M74Z8MGT305R11SNY5G28QH5","plos","Prepare manuscripts for PLOS journals (PLOS ONE, PLOS Biology, PLOS Computational Biology, PLOS Genetics, PLOS Medicine, PLOS Pathogens, PLOS Neglected Tropical Diseases, PLOS Global Public Health and others), covering structure, abstract and author summary, Vancouver-style references, the mandatory data availability policy, ethics and financial disclosure statements, figure requirements (PACE), the PLOS LaTeX template, reporting guidelines and PLOS ONE's publication criteria. Use when targeting any PLOS journal or checking compliance with PLOS policies.","https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fplos\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M74Z8CCN9APXYHNQ95V1EBGT","pkpd-modeling","Pharmacokinetic and pharmacodynamic modelling and simulation - non-compartmental analysis, compartmental and population PK, PK\u002FPD and exposure-response, TMDD, PBPK orientation, bioequivalence, allometric scaling and first-in-human dose, drug interaction prediction, and Bayesian therapeutic drug monitoring. Use when analysing concentration-time data, deriving exposure metrics, fitting PK or PD models, or evaluating dosing regimens. Triggers include \"pharmacokinetics\", \"pharmacodynamics\", \"PK\u002FPD\", \"NCA\", \"non-compartmental\", \"AUC\", \"Cmax\", \"lambda z\", \"half-life\", \"clearance\", \"volume of distribution\", \"compartmental model\", \"population PK\", \"popPK\", \"NONMEM\", \"nlmixr2\", \"Pharmpy\", \"Monolix\", \"exposure-response\", \"Emax\", \"EC50\", \"indirect response\", \"effect compartment\", \"TMDD\", \"PBPK\", \"bioequivalence\", \"RSABE\", \"ABEL\", \"allometric scaling\", \"first-in-human\", \"MABEL\", \"drug-drug interaction\", \"DDI\", \"ICH M12\", \"concentration-QTc\", \"therapeutic drug monitoring\", \"MIPD\", and \"dosing regimen\".","https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fpkpd-modeling\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M74Z86YHJJ1FM3X87BHN76KZ","pinecone","Guides use of Pinecone, a managed serverless vector database, through its Python client and the LangChain and LlamaIndex integrations. Covers creating indexes, upserting and querying vectors, metadata filtering, namespaces, hybrid dense and sparse search, index management, and deleting vectors. Use when building a production RAG system on a hosted vector store, adding semantic search or recommendations without running infrastructure, isolating per-user or per-tenant data with namespaces, combining dense and sparse vectors in one query, or filtering results by metadata. Do not use for self-hosted or local stores (Chroma, Weaviate) or offline similarity search (FAISS).","https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fpinecone\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M74Z80T6E89SAJ8MYDD0767Q","pi-agent","Build with and use Pi, the minimal terminal coding harness. Use for installing Pi, configuring providers\u002Fmodels\u002Fsettings\u002Fenvironment variables, creating Pi skills\u002Fextensions\u002Fpackages\u002Fthemes\u002Fprompt templates, embedding Pi through the SDK, integrating over RPC or JSON event streams, parsing sessions, running local models through the llama.cpp router, developing custom Pi providers and TUI components, or using ecosystem packages such as pi-subagents (delegation\u002Forchestration), pi-mcp-adapter (MCP servers), pi-interview (interactive forms), and pi-web-access (web search, fetching, video understanding).","https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fpi-agent\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M74Z7WF1Y8Q3VFAQPPPRAFMV","phoenix-observability","Open-source AI observability platform for LLM tracing, evaluation, and monitoring. Use when debugging LLM applications with detailed traces, running evaluations on datasets, or monitoring production AI systems with real-time insights.","https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fphoenix-observability\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M74Z7HNEH1A2AVYR3G1X2QV6","peft-fine-tuning","Fine-tunes LLMs with Hugging Face PEFT, using LoRA, QLoRA, IA3, AdaLoRA, prefix tuning, and prompt tuning so that under 1% of parameters are trained. Covers rank, alpha, and target module selection, loading and merging adapters, multi-adapter serving, and integration with TRL SFTTrainer, Axolotl, and vLLM. Use when fine-tuning 7B-70B models on limited GPU memory, when running QLoRA on a single 24GB GPU, when choosing LoRA rank and alpha, when merging or swapping adapters on one base model, or when debugging CUDA OOM or an adapter that does not apply. Not for full fine-tuning of small models under 1B parameters or cases needing all weights updated.","https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fpeft-fine-tuning\u002FSKILL.md",[],[]]