[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6QE7YGSB2WPPJ1XXS4JSZ3C":3,"skill-same:01M6QE7YGSB2WPPJ1XXS4JSZ3C":87},{"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":31,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":64,"commitSha":65,"skillDirectory":66,"forksCount":14,"repositoryHtmlUrl":67,"repositoryHomepageUrl":68,"ownerHtmlUrl":69,"ownerBlogUrl":70,"ownerDescription":71,"updatedAt":72,"install":73,"resources":86},"01M6QE7YGSB2WPPJ1XXS4JSZ3C","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.","Tashima-Tarsh\u002FDisha6.6","Tashima-Tarsh","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F269906498?v=4","01M6PBH98X03XERH0HFT4PFB1P","NITISH KUMAR","01M6PBH9DA0M6KM3Z12P848F0K",0,"MIT","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fkal-cover-letter-to-editor\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"editor","cover letter to editor","letter","cover","cover letter","submission","writing","editorial","for","past","fellowship","manuscript","pitch","as","journal","runtime","get","conflicts","write","reviewer","2026-11-10 10:12:30",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":57,"description":7,"compatibility":63},{"tags":58,"author":59,"version":60,"category":61,"maintainer":62},"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","0da4485785ee599388900be50db1635489d53056",".agents\u002Fskills\u002Fkal-cover-letter-to-editor","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6","https:\u002F\u002Fdisha6.6.thenitishkr.in\u002F","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh","www.thenitishkr","thenitishkr | AI • Cyber-security • Research\r\n","2026-11-08 03:33:25",{"source":8,"skillName":5,"commands":74,"prompt":84,"zipAvailable":85},[75,78,81],{"tool":76,"command":77},"npx","npx skills add Tashima-Tarsh\u002FDisha6.6 --skill cover-letter-to-editor",{"tool":79,"command":80},"bunx","bunx skills add Tashima-Tarsh\u002FDisha6.6 --skill cover-letter-to-editor",{"tool":82,"command":83},"pnpm","pnpm dlx skills add Tashima-Tarsh\u002FDisha6.6 --skill cover-letter-to-editor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fkal-cover-letter-to-editor\u002FSKILL.md",true,[],[88,116,140,167,192,216],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":97,"publishedAt":52},"01M6QRD07D4TGNDK6VJ4EHF8BV","youtube-full","Use when the user needs YouTube transcripts, video search, channel browsing, playlist extraction, or content monitoring. Trigger phrases: 'get the transcript for', 'search YouTube for', 'what are the latest videos on', 'list this playlist', 'monitor this channel', or any request involving a YouTube URL, video ID, or @handle. Do NOT use for downloading video or audio files, YouTube engagement data (likes, comments), or private\u002Fage-restricted videos.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fyoutube-full\u002FSKILL.md",[94],{"categoryNo":95,"categoryName":96,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",[98,99,100,101,102,103,104,105,106,107,108,109,48,110,111,112,40,113,114,115],"youtube full","youtube","full","transcript","search","monitoring","data","Video","Audio","list","files","do","age","trigger","URL","browsing","request","youtube transcripts",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":52},"01M6QRCJ3112VYPA97YG7KGMC2","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[123,124,125,126,102,127,128,129,130,131,132,133,50,134,135,136,137,138,139,40],"twitter","x twitter growth","growth","research","content","engineering","plan","web search","competitors","analyze","engine","strategy","use","platform","grow","posting","competitive",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":149,"publishedAt":52},"01M6QRBN3EHQNJY42RERP7A149","write-a-skill","Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, build, or author a new skill.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrite-a-skill\u002FSKILL.md",[146],{"categoryNo":147,"categoryName":148,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[150,50,151,152,153,154,155,156,135,157,158,64,159,160,161,162,163,164,165,166],"write a skill","github","create","https","productivity","matt pocock","direct","example","build","new skill","structure","new agent","resources","with","tree","progressive disclosure","author",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":173,"publishedAt":52},"01M6QRB6G8P33PNGAF9Y69EJ9T","wrap-up","Close out a launched Claude Managed Agent — recap every primitive the founder now owns, regenerate the single-file overview page, and suggest the next 1-2 upgrades. Use when the user says \"wrap up\", \"close this out\", \"what do I own now\", \"give me the summary\", \"recap the agent\", or when the orchestrator routes phase=wrap-up. primitives_inventory.py tables everything owned (agent, environment, session, memory, outcome, deployment); overview_page.py regenerates a self-contained .\u002Fmy-agent\u002Fagent-overview.html; upgrade_suggester.py ranks the next moves from recorded deferrals plus standing hardening steps. Companion to run-without-you; the last stop before phase=done.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrap-up\u002FSKILL.md",[],[174,175,176,177,178,179,180,181,182,135,183,109,184,185,186,187,188,189,190,191],"wrap up","up","wrap","gemini","deployment","run","file","hardening","closeout","stop","upgrade","founder","close","companion","you","tables","directions","phase",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":196,"categories":197,"keywords":199,"publishedAt":52},"01M6QRA5AYC1RBFZ39GTWGS3N8","workflow-builder","Design and write deterministic multi-agent workflow scripts (.js files in .claude\u002Fworkflows\u002F) for Claude Code's Workflow tool. Use when a user wants to build, create, author, scaffold, or run a custom Claude Code workflow, orchestrate sub-agents (fan-out, pipeline, loop, judge-panel), or automate a repeatable multi-step task across fresh-context agents.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fworkflow-builder\u002FSKILL.md",[198],{"categoryNo":147,"categoryName":148,"taxonomyType":21,"taxonomyTypeDesc":22},[200,201,202,203,204,152,179,205,206,207,208,209,50,210,108,211,212,213,214,215],"workflow","workflow builder","builder","design","workflows","code","orchestrate","pipeline","loop","multi-agent","context","across","fresh","scripts","judge","claude code workflow",{"skillNo":217,"name":218,"nameZh":6,"description":219,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":220,"categories":221,"keywords":222,"publishedAt":52},"01M6QR7QMCZESKQA0ERW1E657M","weekly-review","Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says \"\u002Fcs:weekly-review\". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweekly-review\u002FSKILL.md",[],[223,224,225,226,227,228,229,230,231,208,232,233,234,235,236,237,48,238,239,191],"review","weekly review","weekly","deterministic scripts","reflect","feeds","inventory","open","team","projects","project-management","scanner","conversation","back","project","sprint","cadence"]