[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MAS18F8FGA7J2WR5G30DGM":3,"skill-same:01M6MAS18F8FGA7J2WR5G30DGM":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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6MAS18F8FGA7J2WR5G30DGM","plos",null,"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.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1559,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fplos\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"pathogens","when","formats","targeting","availability","biology","journal","formatting","computational","computational biology","public health","genetics","structure","references","ethics","template","access","open","data","reporting","2026-11-10 10:12:30",false,"---\nname: plos\ndescription: 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.\nlicense: MIT\ncompatibility: No runtime dependencies. Word or the PLOS LaTeX template.\nmetadata:\n  version: \"1.0\"\n  category: journal-formats\n  maintainer: Kalaris Labs\n  author: Kalaris Labs (Sayan Chowdhury)\n  tags: PLOS, PLOS ONE, open access, data availability, Vancouver, journal formatting\n---\n\n# PLOS Journals\n\n## Workflow\n\n1. Identify the exact journal and article type, open its current author guidelines, and fill in the limits table below. Never rely on remembered limits.\n2. Check whether a format-free first submission is allowed. If it is, spend effort on content and mandatory statements rather than layout.\n3. Restructure the manuscript into the venue's front matter and sections (see below).\n4. Prepare the required statements, figures and supplementary files.\n5. Run the checklist, then assemble the submission package: manuscript, source files, figures, declarations and cover letter.\n\n## Verify first (mandatory)\n\nEach PLOS journal has submission guidelines (e.g. https:\u002F\u002Fjournals.plos.org\u002Fplosone\u002Fs\u002Fsubmission-guidelines)\nand policy pages (data availability, ethics, competing interests). PLOS LaTeX instructions and template:\nhttps:\u002F\u002Fjournals.plos.org\u002Fplosone\u002Fs\u002Flatex. Confirm:\n\n| Item | Requirement (fill in) |\n|---|---|\n| Abstract length \u002F structure (PLOS ONE commonly up to 300 words) | |\n| Author summary (PLOS Biology, Comp Bio, Genetics, Pathogens, NTDs) | |\n| Article type specifics (e.g. PLOS Medicine structured abstract) | |\n| Figure file formats and size | |\n\n## PLOS ONE publication criteria\n\nPLOS ONE evaluates **scientific rigor, not perceived impact**: original research, sound methods,\nconclusions supported by data, adequate reporting, ethical standards, intelligible English, and\ndata availability. Write the cover letter around soundness, not novelty.\n\n## Structure\n\nTitle (plus a short title), authors and affiliations, Abstract, (Author summary where required),\nIntroduction, Materials and methods, Results, Discussion, Conclusions (optional), Acknowledgments,\nReferences, Supporting information captions. Methods may come before or after Results depending on the journal.\n\n## Mandatory policies\n\n- **Data availability**: all data underlying the findings must be fully available without restriction\n  at publication, in the paper, supporting information, or a public repository, with a Data\n  Availability Statement. Restrictions (e.g. patient privacy) must be explained with an access route.\n  See `reproducibility-statement`.\n- **Ethics statement** in Methods: approving committee names and approval numbers, consent type, and\n  animal welfare details, as applicable.\n- **Financial disclosure** and **competing interests**, entered in the submission system and reflected in the manuscript.\n- **Reporting guidelines**: CONSORT, STROBE, PRISMA, ARRIVE and others, submitted as supporting information checklists where relevant.\n- Trial registration for clinical trials. Protocols uploaded as supporting information.\n- Code: encouraged or required depending on the journal (PLOS Computational Biology has a code policy).\n\n## References\n\n**Vancouver** style: numbered in order of citation, in square brackets in the text `[1]`, placed\nbefore punctuation. Use the PLOS CSL style or `plos2015.bst` from the LaTeX template. Include DOIs.\nPreprints can be cited. Unpublished data and personal communications go in the text, not the list.\n\n## Figures and supporting information\n\n- Upload figures as separate TIFF or EPS files meeting the resolution\u002Fsize rules. Check them with PLOS's\n  **PACE** tool, which fixes many format problems automatically. Figure legends go in the manuscript after the paragraph that first cites them.\n- Supporting information files (S1 Fig, S1 Table, S1 Text, ...) are uploaded separately with captions at the end of the manuscript.\n- LaTeX submissions: PLOS requires a PDF plus source (single `.tex` with references included, or `.bbl`) at acceptance. Follow the template's rules on packages.\n\n## Related skills\n\n`abstract-and-title` (author summary), `reproducibility-statement`, `systematic-review-prisma`,\n`statistical-analysis`, `venue-templates` (bundled PLOS ONE scaffold), `cover-letter-to-editor`.\n","# PLOS Journals\n\n## Workflow\n\n1. Identify the exact journal and article type, open its current author guidelines, and fill in the limits table below. Never rely on remembered limits.\n2. Check whether a format-free first submission is allowed. If it is, spend effort on content and mandatory statements rather than layout.\n3. Restructure the manuscript into the venue's front matter and sections (see below).\n4. Prepare the required statements, figures and supplementary files.\n5. Run the checklist, then assemble the submission package: manuscript, source files, figures, declarations and cover letter.\n\n## Verify first (mandatory)\n\nEach PLOS journal has submission guidelines (e.g. https:\u002F\u002Fjournals.plos.org\u002Fplosone\u002Fs\u002Fsubmission-guidelines)\nand policy pages (data availability, ethics, competing interests). PLOS LaTeX instructions and template:\nhttps:\u002F\u002Fjournals.plos.org\u002Fplosone\u002Fs\u002Flatex. Confirm:\n\n| Item | Requirement (fill in) |\n|---|---|\n| Abstract length \u002F structure (PLOS ONE commonly up to 300 words) | |\n| Author summary (PLOS Biology, Comp Bio, Genetics, Pathogens, NTDs) | |\n| Article type specifics (e.g. PLOS Medicine structured abstract) | |\n| Figure file formats and size | |\n\n## PLOS ONE publication criteria\n\nPLOS ONE evaluates **scientific rigor, not perceived impact**: original research, sound methods,\nconclusions supported by data, adequate reporting, ethical standards, intelligible English, and\ndata availability. Write the cover letter around soundness, not novelty.\n\n## Structure\n\nTitle (plus a short title), authors and affiliations, Abstract, (Author summary where required),\nIntroduction, Materials and methods, Results, Discussion, Conclusions (optional), Acknowledgments,\nReferences, Supporting information captions. Methods may come before or after Results depending on the journal.\n\n## Mandatory policies\n\n- **Data availability**: all data underlying the findings must be fully available without restriction\n  at publication, in the paper, supporting information, or a public repository, with a Data\n  Availability Statement. Restrictions (e.g. patient privacy) must be explained with an access route.\n  See `reproducibility-statement`.\n- **Ethics statement** in Methods: approving committee names and approval numbers, consent type, and\n  animal welfare details, as applicable.\n- **Financial disclosure** and **competing interests**, entered in the submission system and reflected in the manuscript.\n- **Reporting guidelines**: CONSORT, STROBE, PRISMA, ARRIVE and others, submitted as supporting information checklists where relevant.\n- Trial registration for clinical trials. Protocols uploaded as supporting information.\n- Code: encouraged or required depending on the journal (PLOS Computational Biology has a code policy).\n\n## References\n\n**Vancouver** style: numbered in order of citation, in square brackets in the text `[1]`, placed\nbefore punctuation. Use the PLOS CSL style or `plos2015.bst` from the LaTeX template. Include DOIs.\nPreprints can be cited. Unpublished data and personal communications go in the text, not the list.\n\n## Figures and supporting information\n\n- Upload figures as separate TIFF or EPS files meeting the resolution\u002Fsize rules. Check them with PLOS's\n  **PACE** tool, which fixes many format problems automatically. Figure legends go in the manuscript after the paragraph that first cites them.\n- Supporting information files (S1 Fig, S1 Table, S1 Text, ...) are uploaded separately with captions at the end of the manuscript.\n- LaTeX submissions: PLOS requires a PDF plus source (single `.tex` with references included, or `.bbl`) at acceptance. Follow the template's rules on packages.\n\n## Related skills\n\n`abstract-and-title` (author summary), `reproducibility-statement`, `systematic-review-prisma`,\n`statistical-analysis`, `venue-templates` (bundled PLOS ONE scaffold), `cover-letter-to-editor`.\n",{"name":5,"license":15,"metadata":44,"description":7,"compatibility":50},{"tags":45,"author":46,"version":47,"category":48,"maintainer":49},"PLOS, PLOS ONE, open access, data availability, Vancouver, journal formatting","Kalaris Labs (Sayan Chowdhury)","1.0","journal-formats","Kalaris Labs","No runtime dependencies. Word or the PLOS LaTeX template.","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fplos",474,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-11 14:40:14",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill plos",{"tool":67,"command":68},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill plos",{"tool":70,"command":71},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill plos","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fplos\u002FSKILL.md",true,[],[76,85,92,99,125,150],{"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":80,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":84},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":84},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":84},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":39},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[106,107,108,109,110,111,112,113,114,115,116,20,117,118,119,120,121,122,123,124],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","you","done","reviewer","io","change","cli","merge","past",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":39},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[132,133,134,120,135,136,137,138,139,140,141,142,143,144,111,145,146,147,148,149],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":167,"publishedAt":39},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[156,161,164],{"categoryNo":157,"categoryName":158,"taxonomyType":159,"taxonomyTypeDesc":160},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":162,"categoryName":163,"taxonomyType":159,"taxonomyTypeDesc":160},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":165,"categoryName":166,"taxonomyType":159,"taxonomyTypeDesc":160},"01JBSEEDCAT000000000000010","后端与接口",[152,168,169,170,171,172,173,146,174,112,175,176,177,178,20,179,180,181,182,183],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]