[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6QDXAR3DXRJ6VVCKGVK4MRH":3,"skill-same:01M6QDXAR3DXRJ6VVCKGVK4MRH":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},"01M6QDXAR3DXRJ6VVCKGVK4MRH","abstract-and-title",null,"Write and sharpen research paper titles, abstracts (structured and unstructured), keywords, highlights, significance statements, graphical-abstract text and lay summaries. Use when drafting or revising an abstract to a word limit, turning results into a one-sentence contribution, choosing between candidate titles, writing Cell\u002FElsevier highlights, a PNAS significance statement or a plain-language summary, or optimizing discoverability (keywords, search terms).","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-abstract-and-title\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],"abstract and title","title","contribution","candidate","summaries","unstructured","limit","plain-language","scientific","discoverability","writing","runtime","use","write","text","Word","sharpen","scientific writing","search","research","2026-11-10 10:12:30",false,"---\nname: abstract-and-title\ndescription: Write and sharpen research paper titles, abstracts (structured and unstructured), keywords, highlights, significance statements, graphical-abstract text and lay summaries. Use when drafting or revising an abstract to a word limit, turning results into a one-sentence contribution, choosing between candidate titles, writing Cell\u002FElsevier highlights, a PNAS significance statement or a plain-language summary, or optimizing discoverability (keywords, search terms).\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: abstract, title, keywords, highlights, significance statement, lay summary, scientific writing\n---\n\n# Titles, Abstracts and Summary Text\n\nMost readers, editors and reviewers decide from the title and abstract alone.\nThey are also what search engines and indexing services see. Write them last,\nfrom the finished results, and revise them more than any other part of the paper.\n\n## Inputs to collect first\n\n- The single main finding, with its key number (effect size, accuracy, p-value\u002FCI, sample size).\n- The target venue's limits: abstract word count, structured vs. unstructured, title length,\n  keyword count, highlights\u002Fsignificance requirements. **Look these up in the venue's current\n  author guidelines** (the `venue-templates` skill and journal-format skills help). Never assume.\n- Who reads it: specialists (field venue) or broad scientists (Nature, Science, PNAS).\n\n## Abstract: the five-move structure\n\nUnstructured abstracts still follow these moves. Structured ones label them.\n\n| Move | Share | Content |\n|---|---|---|\n| Context | 1 sentence | The broader problem, in terms the venue's readers care about |\n| Gap | 1 sentence | What is unknown, unsolved or wrong. Make the gap concrete |\n| Approach | 1-2 sentences | What you did: design, data, method, with the essential scale (n, datasets) |\n| Results | 2-3 sentences | The main findings **with numbers**. Lead with the most important |\n| Implication | 1 sentence | What changes because of this, bounded by what the evidence supports |\n\nStructured formats: IMRaD (Background\u002FMethods\u002FResults\u002FConclusions) for most clinical\njournals. CONSORT-for-abstracts for RCTs. PRISMA 2020 for Abstracts for systematic reviews.\nSome journals (e.g. BMJ) use their own headings, so match the journal exactly.\n\n**Rules:**\n- Numbers beat adjectives: \"reduced error by 23% (95% CI 18-28%)\" not \"substantially reduced error\".\n- No citations, undefined abbreviations, or claims not in the paper. Define an abbreviation only if used ≥2 times.\n- Past tense for what you did and found; present tense for established facts and implications.\n- Keep it self-contained: a reader should understand it without the paper.\n- Hit the limit without padding. If over, cut context before results.\n\n## Titles\n\nGenerate 5-10 candidates across types, then pick against the criteria:\n\n- **Declarative** (states the finding): \"Metformin reduces hepatic glucose output via complex IV inhibition\".\n  Common in biology\u002Fmedicine and broad journals.\n- **Descriptive** (states the topic\u002Fmethod): \"A graph neural network for retrosynthesis planning\".\n  Common in CS\u002Fengineering.\n- **Question**: use sparingly, only when the answer is genuinely surprising.\n\nCriteria: accurate (no overclaiming), specific (organism, method, population), contains\nthe 2-3 terms people search for, within the venue's length limit, no abbreviations\nexcept universal ones (DNA, MRI), no puns that hide the content. Check that no existing\npaper already has a near-identical title.\n\n## Keywords\n\nChoose terms **not already in the title** to widen discoverability: synonyms, the broader\nfield, method names, organism\u002Fpopulation. Prefer controlled vocabulary where the venue\nuses it (MeSH for biomedicine, ACM CCS concepts, IEEE Taxonomy, JEL codes, PACS\u002FPhySH).\n\n## Venue-specific extras\n\n| Element | Typical form (verify per venue) |\n|---|---|\n| Highlights (Cell Press, Elsevier) | 3-5 bullets, each up to ~85 characters including spaces, results-focused |\n| eTOC blurb \u002F In Brief (Cell Press) | Short third-person paragraph for non-specialists |\n| Significance statement (PNAS) | Plain-language paragraph on why the work matters to a broad audience |\n| Author summary (PLOS) | Non-technical summary for a general reader |\n| Lay \u002F plain-language summary | Health and life-science journals, funders: no jargon, ~reading age 12-14 |\n| Graphical abstract | One image read left-to-right or top-to-bottom: problem → approach → key result |\n| Teaser \u002F tweet-length | One sentence with the key number, for press and social media |\n\n## Revision checklist\n\n1. Does the first sentence establish why this matters to *this venue's* readers?\n2. Is the gap stated explicitly, not implied?\n3. Does every result sentence contain a number or concrete outcome?\n4. Is every claim supported in the main text, at the same strength?\n5. Word count within the limit (count it, don't estimate)?\n6. Would a researcher from an adjacent field understand it?\n7. Do title, abstract, highlights and conclusions tell the *same* story with the same numbers?\n\n## Related skills\n\n`scientific-writing`, `ml-paper-writing`, `cover-letter-to-editor`, `venue-templates`,\njournal-format skills (`nature-portfolio`, `cell-press`, `plos`, ...), `scientific-slides`.\n","# Titles, Abstracts and Summary Text\n\nMost readers, editors and reviewers decide from the title and abstract alone.\nThey are also what search engines and indexing services see. Write them last,\nfrom the finished results, and revise them more than any other part of the paper.\n\n## Inputs to collect first\n\n- The single main finding, with its key number (effect size, accuracy, p-value\u002FCI, sample size).\n- The target venue's limits: abstract word count, structured vs. unstructured, title length,\n  keyword count, highlights\u002Fsignificance requirements. **Look these up in the venue's current\n  author guidelines** (the `venue-templates` skill and journal-format skills help). Never assume.\n- Who reads it: specialists (field venue) or broad scientists (Nature, Science, PNAS).\n\n## Abstract: the five-move structure\n\nUnstructured abstracts still follow these moves. Structured ones label them.\n\n| Move | Share | Content |\n|---|---|---|\n| Context | 1 sentence | The broader problem, in terms the venue's readers care about |\n| Gap | 1 sentence | What is unknown, unsolved or wrong. Make the gap concrete |\n| Approach | 1-2 sentences | What you did: design, data, method, with the essential scale (n, datasets) |\n| Results | 2-3 sentences | The main findings **with numbers**. Lead with the most important |\n| Implication | 1 sentence | What changes because of this, bounded by what the evidence supports |\n\nStructured formats: IMRaD (Background\u002FMethods\u002FResults\u002FConclusions) for most clinical\njournals. CONSORT-for-abstracts for RCTs. PRISMA 2020 for Abstracts for systematic reviews.\nSome journals (e.g. BMJ) use their own headings, so match the journal exactly.\n\n**Rules:**\n- Numbers beat adjectives: \"reduced error by 23% (95% CI 18-28%)\" not \"substantially reduced error\".\n- No citations, undefined abbreviations, or claims not in the paper. Define an abbreviation only if used ≥2 times.\n- Past tense for what you did and found; present tense for established facts and implications.\n- Keep it self-contained: a reader should understand it without the paper.\n- Hit the limit without padding. If over, cut context before results.\n\n## Titles\n\nGenerate 5-10 candidates across types, then pick against the criteria:\n\n- **Declarative** (states the finding): \"Metformin reduces hepatic glucose output via complex IV inhibition\".\n  Common in biology\u002Fmedicine and broad journals.\n- **Descriptive** (states the topic\u002Fmethod): \"A graph neural network for retrosynthesis planning\".\n  Common in CS\u002Fengineering.\n- **Question**: use sparingly, only when the answer is genuinely surprising.\n\nCriteria: accurate (no overclaiming), specific (organism, method, population), contains\nthe 2-3 terms people search for, within the venue's length limit, no abbreviations\nexcept universal ones (DNA, MRI), no puns that hide the content. Check that no existing\npaper already has a near-identical title.\n\n## Keywords\n\nChoose terms **not already in the title** to widen discoverability: synonyms, the broader\nfield, method names, organism\u002Fpopulation. Prefer controlled vocabulary where the venue\nuses it (MeSH for biomedicine, ACM CCS concepts, IEEE Taxonomy, JEL codes, PACS\u002FPhySH).\n\n## Venue-specific extras\n\n| Element | Typical form (verify per venue) |\n|---|---|\n| Highlights (Cell Press, Elsevier) | 3-5 bullets, each up to ~85 characters including spaces, results-focused |\n| eTOC blurb \u002F In Brief (Cell Press) | Short third-person paragraph for non-specialists |\n| Significance statement (PNAS) | Plain-language paragraph on why the work matters to a broad audience |\n| Author summary (PLOS) | Non-technical summary for a general reader |\n| Lay \u002F plain-language summary | Health and life-science journals, funders: no jargon, ~reading age 12-14 |\n| Graphical abstract | One image read left-to-right or top-to-bottom: problem → approach → key result |\n| Teaser \u002F tweet-length | One sentence with the key number, for press and social media |\n\n## Revision checklist\n\n1. Does the first sentence establish why this matters to *this venue's* readers?\n2. Is the gap stated explicitly, not implied?\n3. Does every result sentence contain a number or concrete outcome?\n4. Is every claim supported in the main text, at the same strength?\n5. Word count within the limit (count it, don't estimate)?\n6. Would a researcher from an adjacent field understand it?\n7. Do title, abstract, highlights and conclusions tell the *same* story with the same numbers?\n\n## Related skills\n\n`scientific-writing`, `ml-paper-writing`, `cover-letter-to-editor`, `venue-templates`,\njournal-format skills (`nature-portfolio`, `cell-press`, `plos`, ...), `scientific-slides`.\n",{"name":5,"license":15,"metadata":57,"description":7,"compatibility":63},{"tags":58,"author":59,"version":60,"category":61,"maintainer":62},"abstract, title, keywords, highlights, significance statement, lay summary, scientific writing","Kalaris Labs (Sayan Chowdhury)","1.0","research-writing","Kalaris Labs","No runtime dependencies.","main","0da4485785ee599388900be50db1635489d53056",".agents\u002Fskills\u002Fkal-abstract-and-title","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 abstract-and-title",{"tool":79,"command":80},"bunx","bunx skills add Tashima-Tarsh\u002FDisha6.6 --skill abstract-and-title",{"tool":82,"command":83},"pnpm","pnpm dlx skills add Tashima-Tarsh\u002FDisha6.6 --skill abstract-and-title","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fkal-abstract-and-title\u002FSKILL.md",true,[],[88,117,139,166,191,215],{"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,50,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116],"youtube full","youtube","full","transcript","monitoring","data","Video","Audio","list","files","do","get","age","trigger","URL","for","browsing","request","youtube transcripts",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"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",[],[124,125,126,51,50,127,128,129,130,131,132,133,45,134,44,135,136,137,138,113],"twitter","x twitter growth","growth","content","engineering","plan","web search","competitors","analyze","engine","strategy","platform","grow","posting","competitive",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":148,"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",[145],{"categoryNo":146,"categoryName":147,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[149,45,150,151,152,153,154,155,44,156,157,64,158,159,160,161,162,163,164,165],"write a skill","github","create","https","productivity","matt pocock","direct","example","build","new skill","structure","new agent","resources","with","tree","progressive disclosure","author",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":172,"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",[],[173,174,175,176,177,178,179,180,181,44,182,108,183,184,185,186,187,188,189,190],"wrap up","up","wrap","gemini","deployment","run","file","hardening","closeout","stop","upgrade","founder","close","companion","you","tables","directions","phase",{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":195,"categories":196,"keywords":198,"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",[197],{"categoryNo":146,"categoryName":147,"taxonomyType":21,"taxonomyTypeDesc":22},[199,200,201,202,203,151,178,204,205,206,207,208,45,209,107,210,211,212,213,214],"workflow","workflow builder","builder","design","workflows","code","orchestrate","pipeline","loop","multi-agent","context","across","fresh","scripts","judge","claude code workflow",{"skillNo":216,"name":217,"nameZh":6,"description":218,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":219,"categories":220,"keywords":221,"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",[],[222,223,224,225,226,227,228,229,230,207,231,232,233,234,235,236,109,237,238,190],"review","weekly review","weekly","deterministic scripts","reflect","feeds","inventory","open","team","projects","project-management","scanner","conversation","back","project","sprint","cadence"]