[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EGFDXQ01YRK1Y94PJYRSXB":3,"skill-same:01M6EGFDXQ01YRK1Y94PJYRSXB":66},{"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":23,"publishedAt":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M6EGFDXQ01YRK1Y94PJYRSXB","ln-521-test-researcher",null,"Researches real-world problems, competitor solutions, and customer complaints before test planning. Posts findings as Linear comment for ln-522 and ln-523.","levalencia\u002Fagent-god-mode","levalencia","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6962857?v=4","01M6EB0FZZ4BPQPC4HET4QY6NM","Luis Valencia ","01M6EB0G4HWHPWW0H9X7QKSAHP",3,"MIT","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-521-test-researcher\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[24,25,26,27,28,29,30,31],"test","researcher","ln 521 test researcher","customer","planning","linear","world","as","2026-11-10 10:12:30",false,"---\nname: ln-521-test-researcher\ndescription: \"Researches real-world problems, competitor solutions, and customer complaints before test planning. Posts findings as Linear comment for ln-522 and ln-523.\"\nlicense: MIT\n---\n\n> **Paths:** File paths (`shared\u002F`, `references\u002F`, `..\u002Fln-*`) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root.\n\n## Inputs\n\n| Input | Required | Source | Description |\n|-------|----------|--------|-------------|\n| `storyId` | Yes | args, git branch, kanban, user | Story to process |\n\n**Resolution:** Story Resolution Chain.\n**Status filter:** To Review\n\n# Test Researcher\n\nResearches real-world problems and edge cases before test planning to ensure tests cover actual user pain points, not just AC.\n\n## Purpose & Scope\n- Research common problems for the feature domain using Web Search, MCP Ref, Context7.\n- Analyze how competitors solve the same problem.\n- Find customer complaints and pain points from forums, StackOverflow, Reddit.\n- Post structured findings as Linear comment for downstream skills (ln-522, ln-523).\n- No test creation or status changes.\n\n## When to Use\n\nThis skill should be used when:\n- **Invoked by ln-520-test-planner** at start of test planning pipeline\n- Story has non-trivial functionality (external APIs, file formats, authentication)\n- Need to discover edge cases beyond AC\n\n**Skip research when:**\n- Story is trivial (simple CRUD, no external dependencies)\n- Research comment already exists on Story\n- User explicitly requests to skip\n\n## Workflow\n\n### Phase 1: Discovery\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Finput_resolution_pattern.md`\n\n1. **Resolve storyId:** Run Story Resolution Chain per guide (status filter: [To Review]).\n\n2. Auto-discover Team ID from `docs\u002Ftasks\u002Fkanban_board.md`\n\n### Phase 2: Extract Feature Domain\n\n1) Fetch Story from Linear\n2) Parse Story goal and AC to identify:\n   - What technology\u002FAPI\u002Fformat is involved?\n   - What is the user's goal? (e.g., \"translate XLIFF files\", \"authenticate via OAuth\")\n3) Extract keywords for research queries\n\n### Phase 3: Research Common Problems\n\nUse available tools to find real-world problems:\n\n1) **Web Search:**\n   - \"[feature] common problems\"\n   - \"[format] edge cases\"\n   - \"[API] gotchas\"\n   - \"[technology] known issues\"\n\n2) **MCP Ref:**\n   - `ref_search_documentation(\"[feature] error handling best practices\")`\n   - `ref_search_documentation(\"[format] validation rules\")`\n\n3) **Context7:**\n   - Query relevant library docs for known issues\n   - Check API documentation for limitations\n\n### Phase 4: Research Competitor Solutions\n\n1) **Web Search:**\n   - \"[competitor] [feature] how it works\"\n   - \"[feature] comparison\"\n   - \"[product type] best practices\"\n\n2) **Analysis:**\n   - How do market leaders handle this functionality?\n   - What UX patterns do they use?\n   - What error handling approaches are common?\n\n### Phase 5: Research Customer Complaints\n\n1) **Web Search:**\n   - \"[feature] complaints\"\n   - \"[product type] user problems\"\n   - \"[format] issues reddit\"\n   - \"[format] issues stackoverflow\"\n\n2) **Analysis:**\n   - What do users actually struggle with?\n   - What are common frustrations?\n   - What gaps exist between user expectations and typical implementations?\n\n### Phase 6: Compile and Post Findings\n\n1) **Compile findings** into categories:\n   - **Input validation issues** (malformed data, encoding, size limits)\n   - **Edge cases** (empty input, special characters, Unicode)\n   - **Error handling** (timeouts, rate limits, partial failures)\n   - **Security concerns** (injection, authentication bypass)\n   - **Competitor advantages** (features we should match or exceed)\n   - **Customer pain points** (problems users actually complain about)\n\n2) **Post Linear comment** on Story with research summary:\n\n```markdown\n## Test Research: {Feature}\n\n### Sources Consulted\n- [Source 1](url)\n- [Source 2](url)\n\n### Common Problems Found\n1. **Problem 1:** Description + test case suggestion\n2. **Problem 2:** Description + test case suggestion\n\n### Competitor Analysis\n- **Competitor A:** How they handle this + what we can learn\n- **Competitor B:** Their approach + gaps we can exploit\n\n### Customer Pain Points\n- **Complaint 1:** What users struggle with + test to prevent\n- **Complaint 2:** Common frustration + how to verify we solve it\n\n### Recommended Test Coverage\n- [ ] Test case for problem 1\n- [ ] Test case for competitor parity\n- [ ] Test case for customer pain point\n\n---\n_This research informs both manual tests (ln-522) and automated tests (ln-523)._\n```\n\n## Critical Rules\n\n- **No test creation:** Only research and documentation.\n- **No status changes:** Only Linear comment.\n- **Source attribution:** Always include URLs for sources consulted.\n- **Actionable findings:** Each problem should suggest a test case.\n- **Skip trivial Stories:** Don't research \"Add button to page\".\n\n## Definition of Done\n\n- [ ] Feature domain extracted from Story (technology\u002FAPI\u002Fformat identified)\n- [ ] Common problems researched (Web Search + MCP Ref + Context7)\n- [ ] Competitor solutions analyzed (at least 1-2 competitors)\n- [ ] Customer complaints found (forums, StackOverflow, Reddit)\n- [ ] Findings compiled into categories\n- [ ] Linear comment posted with \"## Test Research: {Feature}\" header\n- [ ] At least 3 recommended test cases suggested\n\n**Output:** Linear comment with research findings for ln-522 and ln-523 to use.\n\n## Reference Files\n\n- Research methodology: Web Search, MCP Ref, Context7 tools\n- Comment format: Structured markdown with sources\n- Downstream consumers: ln-522-manual-tester, ln-523-auto-test-planner\n- **MANDATORY READ:** `shared\u002Freferences\u002Fresearch_tool_fallback.md`\n\n---\n\n**Version:** 1.0.0\n**Last Updated:** 2026-01-15\n","> **Paths:** File paths (`shared\u002F`, `references\u002F`, `..\u002Fln-*`) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root.\n\n## Inputs\n\n| Input | Required | Source | Description |\n|-------|----------|--------|-------------|\n| `storyId` | Yes | args, git branch, kanban, user | Story to process |\n\n**Resolution:** Story Resolution Chain.\n**Status filter:** To Review\n\n# Test Researcher\n\nResearches real-world problems and edge cases before test planning to ensure tests cover actual user pain points, not just AC.\n\n## Purpose & Scope\n- Research common problems for the feature domain using Web Search, MCP Ref, Context7.\n- Analyze how competitors solve the same problem.\n- Find customer complaints and pain points from forums, StackOverflow, Reddit.\n- Post structured findings as Linear comment for downstream skills (ln-522, ln-523).\n- No test creation or status changes.\n\n## When to Use\n\nThis skill should be used when:\n- **Invoked by ln-520-test-planner** at start of test planning pipeline\n- Story has non-trivial functionality (external APIs, file formats, authentication)\n- Need to discover edge cases beyond AC\n\n**Skip research when:**\n- Story is trivial (simple CRUD, no external dependencies)\n- Research comment already exists on Story\n- User explicitly requests to skip\n\n## Workflow\n\n### Phase 1: Discovery\n\n**MANDATORY READ:** Load `shared\u002Freferences\u002Finput_resolution_pattern.md`\n\n1. **Resolve storyId:** Run Story Resolution Chain per guide (status filter: [To Review]).\n\n2. Auto-discover Team ID from `docs\u002Ftasks\u002Fkanban_board.md`\n\n### Phase 2: Extract Feature Domain\n\n1) Fetch Story from Linear\n2) Parse Story goal and AC to identify:\n   - What technology\u002FAPI\u002Fformat is involved?\n   - What is the user's goal? (e.g., \"translate XLIFF files\", \"authenticate via OAuth\")\n3) Extract keywords for research queries\n\n### Phase 3: Research Common Problems\n\nUse available tools to find real-world problems:\n\n1) **Web Search:**\n   - \"[feature] common problems\"\n   - \"[format] edge cases\"\n   - \"[API] gotchas\"\n   - \"[technology] known issues\"\n\n2) **MCP Ref:**\n   - `ref_search_documentation(\"[feature] error handling best practices\")`\n   - `ref_search_documentation(\"[format] validation rules\")`\n\n3) **Context7:**\n   - Query relevant library docs for known issues\n   - Check API documentation for limitations\n\n### Phase 4: Research Competitor Solutions\n\n1) **Web Search:**\n   - \"[competitor] [feature] how it works\"\n   - \"[feature] comparison\"\n   - \"[product type] best practices\"\n\n2) **Analysis:**\n   - How do market leaders handle this functionality?\n   - What UX patterns do they use?\n   - What error handling approaches are common?\n\n### Phase 5: Research Customer Complaints\n\n1) **Web Search:**\n   - \"[feature] complaints\"\n   - \"[product type] user problems\"\n   - \"[format] issues reddit\"\n   - \"[format] issues stackoverflow\"\n\n2) **Analysis:**\n   - What do users actually struggle with?\n   - What are common frustrations?\n   - What gaps exist between user expectations and typical implementations?\n\n### Phase 6: Compile and Post Findings\n\n1) **Compile findings** into categories:\n   - **Input validation issues** (malformed data, encoding, size limits)\n   - **Edge cases** (empty input, special characters, Unicode)\n   - **Error handling** (timeouts, rate limits, partial failures)\n   - **Security concerns** (injection, authentication bypass)\n   - **Competitor advantages** (features we should match or exceed)\n   - **Customer pain points** (problems users actually complain about)\n\n2) **Post Linear comment** on Story with research summary:\n\n```markdown\n## Test Research: {Feature}\n\n### Sources Consulted\n- [Source 1](url)\n- [Source 2](url)\n\n### Common Problems Found\n1. **Problem 1:** Description + test case suggestion\n2. **Problem 2:** Description + test case suggestion\n\n### Competitor Analysis\n- **Competitor A:** How they handle this + what we can learn\n- **Competitor B:** Their approach + gaps we can exploit\n\n### Customer Pain Points\n- **Complaint 1:** What users struggle with + test to prevent\n- **Complaint 2:** Common frustration + how to verify we solve it\n\n### Recommended Test Coverage\n- [ ] Test case for problem 1\n- [ ] Test case for competitor parity\n- [ ] Test case for customer pain point\n\n---\n_This research informs both manual tests (ln-522) and automated tests (ln-523)._\n```\n\n## Critical Rules\n\n- **No test creation:** Only research and documentation.\n- **No status changes:** Only Linear comment.\n- **Source attribution:** Always include URLs for sources consulted.\n- **Actionable findings:** Each problem should suggest a test case.\n- **Skip trivial Stories:** Don't research \"Add button to page\".\n\n## Definition of Done\n\n- [ ] Feature domain extracted from Story (technology\u002FAPI\u002Fformat identified)\n- [ ] Common problems researched (Web Search + MCP Ref + Context7)\n- [ ] Competitor solutions analyzed (at least 1-2 competitors)\n- [ ] Customer complaints found (forums, StackOverflow, Reddit)\n- [ ] Findings compiled into categories\n- [ ] Linear comment posted with \"## Test Research: {Feature}\" header\n- [ ] At least 3 recommended test cases suggested\n\n**Output:** Linear comment with research findings for ln-522 and ln-523 to use.\n\n## Reference Files\n\n- Research methodology: Web Search, MCP Ref, Context7 tools\n- Comment format: Structured markdown with sources\n- Downstream consumers: ln-522-manual-tester, ln-523-auto-test-planner\n- **MANDATORY READ:** `shared\u002Freferences\u002Fresearch_tool_fallback.md`\n\n---\n\n**Version:** 1.0.0\n**Last Updated:** 2026-01-15\n",{"name":5,"license":15,"description":7},"main","fa638b97a18ff6d9f26cf0eaf3dfa123531bcc87","organized-skills\u002Fln-521-test-researcher",1,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode","https:\u002F\u002Fgithub.com\u002Flevalencia","https:\u002F\u002Fmedium.com\u002F@luisevalencia","Microsoft MVP - Artificial Intelligence\r\nMachine Learning Enthusiast\r\n","2026-05-02 06:55:36",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add levalencia\u002Fagent-god-mode --skill ln-521-test-researcher",{"tool":52,"command":53},"bunx","bunx skills add levalencia\u002Fagent-god-mode --skill ln-521-test-researcher",{"tool":55,"command":56},"pnpm","pnpm dlx skills add levalencia\u002Fagent-god-mode --skill ln-521-test-researcher","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-521-test-researcher\u002FSKILL.md",true,[60],{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},"customize.toml","OTHER","其他",2696,"https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.roo\u002Fskills\u002Fbmad-cis-agent-storyteller\u002Fcustomize.toml",[67,89,125,152,176,204],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":32},"01M6EM8ES5M9J4S8N78NJST0YC","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\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fzarr-python\u002FSKILL.md",[],[74,75,76,77,78,79,80,81,82,83,84,85,86,87,88],"python","zarr python","storage","integration","s3","gcs","cloud","dask","parallel","pipelines","arrays","numpy","scientific computing","scale","scientific",{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":106,"publishedAt":32},"01M6EM8AR6ZFKZ9YVW8TTG850Z","zabbix","Zabbix monitoring system automation via API and Python. Use when: (1) Managing hosts, templates, items, triggers, or host groups, (2) Automating monitoring configuration, (3) Sending data via Zabbix trapper\u002Fsender, (4) Querying historical data or events, (5) Bulk operations on Zabbix objects, (6) Maintenance window management, (7) User\u002Fpermission management","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fzabbix-api-skill\u002FSKILL.md",[95,98,101],{"categoryNo":96,"categoryName":97,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":99,"categoryName":100,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[91,74,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124],"automation","window management","monitoring","data","templates","api","system","operations","use","maintenance","objects","permission","bulk operations","triggers","host","events","via","bulk",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":32},"01M6EM6Q9JG846ECQY9A210A26","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\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fx-twitter-growth\u002FSKILL.md",[],[132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147,148,149,150,151],"twitter","x twitter growth","growth","competitive intelligence","search","analyzing","plan","marketing","web search","competitors","analyze","write","optimize","social","intelligence","viral","growth engine","mechanics","grow","competitive",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":158,"publishedAt":32},"01M6EM3FQNPYNKPC4CV9TCVNGD","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\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fwhat-if-oracle\u002FSKILL.md",[],[159,160,24,28,161,162,163,164,165,166,167,168,115,169,170,171,172,173,174,175],"oracle","what if oracle","ux","futures","risk","analysis","explore","decision","branch","question","exploration","options","stress-test","strategies","trigger","case","multi",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":185,"publishedAt":32},"01M6EM08C06RGDYCJ86HAPK0FF","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fvercel-react-best-practices\u002FSKILL.md",[182],{"categoryNo":183,"categoryName":184,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[186,187,188,189,190,191,192,193,194,195,196,197,198,110,199,200,201,202,203,120],"react","vercel react best practices","best practices","react best practices","vercel","writing","performance","components","react components","guidelines","tasks","code","Optimization","Next.js","refactoring","performance optimization","next","pages",{"skillNo":205,"name":206,"nameZh":6,"description":207,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":208,"categories":209,"keywords":220,"publishedAt":32},"01M6EM00S13326QM08DTM94J6Z","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\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fvenue-templates\u002FSKILL.md",[210,213,216,217],{"categoryNo":211,"categoryName":212,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":214,"categoryName":215,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":99,"categoryName":100,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":218,"categoryName":219,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000036","内容创作者",[111,221,222,195,223,224,225,226,227,228,229,143,230,231,232,233,234,235,88,236],"venue templates","research","NeurIPS","ICML","LaTeX","science","Bash","access","read","edit","proposals","Academic","requirements","formatting","journal","chi"]