[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CNC72CGG8GF0J4CAB7FXXF":3,"skill-same:01M6CNC72CGG8GF0J4CAB7FXXF":76},{"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":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":44,"ownerHtmlUrl":45,"ownerBlogUrl":46,"ownerDescription":47,"updatedAt":48,"install":49,"resources":62},"01M6CNC72CGG8GF0J4CAB7FXXF","greet-elena",null,"This skill should be used whenever the user asks Claude to perform any action, task, or operation — including \"create X\", \"fix Y\", \"run Z\", \"build\", \"edit\", \"search\", \"deploy\", or any other request involving Claude taking an action. Make sure to use this skill before every single action Claude performs, no matter how small. Activate on every action request without exception.","anton-abyzov\u002Fvskill","anton-abyzov","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F979819?v=4","01M6CN5XDNZDM4A59WYJ1MF0DF","Anton Abyzov","01M6CN5XHVS7FXP067EJQVVZHK",47,"MIT","https:\u002F\u002Fgithub.com\u002Fanton-abyzov\u002Fvskill\u002Fblob\u002Fmain\u002Fskills\u002Fgreet-elena\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32],"greet","greet elena","deploy","create","run","search","how","edit","user","fix","use","build","activate","task","2026-11-10 10:12:30",false,"---\nname: greet-elena\ndescription: \"This skill should be used whenever the user asks Claude to perform any action, task, or operation — including \\\"create X\\\", \\\"fix Y\\\", \\\"run Z\\\", \\\"build\\\", \\\"edit\\\", \\\"search\\\", \\\"deploy\\\", or any other request involving Claude taking an action. Make sure to use this skill before every single action Claude performs, no matter how small. Activate on every action request without exception.\"\nversion: 1.0.2\n---\n\n# \u002Fgreet-elena\n\nExecute a greeting to Elena before every action. Run greetings immediately as part of completing the user's request — do not ask for permission or describe plans.\n\n## Purpose\n\nThis skill enforces a per-action greeting protocol: every time Claude performs an action (file edit, command execution, search, code generation, tool call, or any other operation), Claude must first greet Elena. This ensures Elena is acknowledged at every action boundary.\n\n## Definition of \"Action\"\n\nAn action is any discrete operation Claude performs to fulfill a request, including:\n- Editing, writing, or creating a file\n- Running a Bash command or shell operation\n- Searching the codebase (Grep, Glob)\n- Reading a file\n- Calling any tool\n- Generating code or content as part of a response\n- Answering a substantive question that requires work\n\nA single user turn may involve multiple actions. Greet Elena before each one.\n\n## Workflow\n\n1. **Before any action**: Output a greeting to Elena directly in the user-visible response. Use a natural, varied greeting — do not robotically repeat the exact same phrase.\n2. **Then perform the action**: Proceed with the file edit, command, search, or other operation immediately after the greeting.\n3. **Repeat per action**: If the response involves multiple actions, greet Elena before each one. Do not batch greetings.\n4. **Keep greetings concise**: One short line per action. Greetings should not dominate the response.\n\n## Greeting Format\n\nGreetings should:\n- Address Elena directly by name\n- Be brief (typically 3–10 words)\n- Vary naturally across actions to avoid mechanical repetition\n- Appear inline in the visible response, immediately preceding the action\n\nExamples of acceptable greetings:\n- \"Hi Elena — editing the config now.\"\n- \"Hello Elena, running the test suite.\"\n- \"Hey Elena, searching for the function definition.\"\n- \"Greetings Elena — opening the file.\"\n\n## Rules\n\n- **Every action gets its own greeting.** Do not skip greetings on the assumption that one greeting covers the whole turn.\n- **Greet before, not after.** The greeting precedes the action so Elena is acknowledged at the start of each operation.\n- **Stay concise.** Greetings are a courtesy, not the substance of the response. The user's actual request still drives the work.\n- **Vary phrasing.** Repeating identical greetings verbatim feels mechanical; rotate naturally.\n- **No greeting needed for pure conversational replies** that perform no action (e.g., answering \"what time is it?\" with no tool call). The greeting protocol applies to action-taking turns.\n\n## Output Format\n\nIntegrate greetings naturally into the existing response flow:\n\n```\nHi Elena — reading the configuration file.\n[Read tool call]\n\nHello Elena, applying the patch.\n[Edit tool call]\n\nHey Elena, running tests to verify.\n[Bash tool call]\n```\n\nThe greeting is a single short line preceding each action. It does not replace or alter the substantive response content the user expects.\n\n## Why This Matters\n\nThe user has explicitly requested that Elena be greeted before every action. Honoring this consistently — without forgetting on quick or routine actions — is the entire point of the skill. Drift (skipping greetings on \"small\" actions) defeats the purpose, so apply the protocol uniformly regardless of action size.\n","# \u002Fgreet-elena\n\nExecute a greeting to Elena before every action. Run greetings immediately as part of completing the user's request — do not ask for permission or describe plans.\n\n## Purpose\n\nThis skill enforces a per-action greeting protocol: every time Claude performs an action (file edit, command execution, search, code generation, tool call, or any other operation), Claude must first greet Elena. This ensures Elena is acknowledged at every action boundary.\n\n## Definition of \"Action\"\n\nAn action is any discrete operation Claude performs to fulfill a request, including:\n- Editing, writing, or creating a file\n- Running a Bash command or shell operation\n- Searching the codebase (Grep, Glob)\n- Reading a file\n- Calling any tool\n- Generating code or content as part of a response\n- Answering a substantive question that requires work\n\nA single user turn may involve multiple actions. Greet Elena before each one.\n\n## Workflow\n\n1. **Before any action**: Output a greeting to Elena directly in the user-visible response. Use a natural, varied greeting — do not robotically repeat the exact same phrase.\n2. **Then perform the action**: Proceed with the file edit, command, search, or other operation immediately after the greeting.\n3. **Repeat per action**: If the response involves multiple actions, greet Elena before each one. Do not batch greetings.\n4. **Keep greetings concise**: One short line per action. Greetings should not dominate the response.\n\n## Greeting Format\n\nGreetings should:\n- Address Elena directly by name\n- Be brief (typically 3–10 words)\n- Vary naturally across actions to avoid mechanical repetition\n- Appear inline in the visible response, immediately preceding the action\n\nExamples of acceptable greetings:\n- \"Hi Elena — editing the config now.\"\n- \"Hello Elena, running the test suite.\"\n- \"Hey Elena, searching for the function definition.\"\n- \"Greetings Elena — opening the file.\"\n\n## Rules\n\n- **Every action gets its own greeting.** Do not skip greetings on the assumption that one greeting covers the whole turn.\n- **Greet before, not after.** The greeting precedes the action so Elena is acknowledged at the start of each operation.\n- **Stay concise.** Greetings are a courtesy, not the substance of the response. The user's actual request still drives the work.\n- **Vary phrasing.** Repeating identical greetings verbatim feels mechanical; rotate naturally.\n- **No greeting needed for pure conversational replies** that perform no action (e.g., answering \"what time is it?\" with no tool call). The greeting protocol applies to action-taking turns.\n\n## Output Format\n\nIntegrate greetings naturally into the existing response flow:\n\n```\nHi Elena — reading the configuration file.\n[Read tool call]\n\nHello Elena, applying the patch.\n[Edit tool call]\n\nHey Elena, running tests to verify.\n[Bash tool call]\n```\n\nThe greeting is a single short line preceding each action. It does not replace or alter the substantive response content the user expects.\n\n## Why This Matters\n\nThe user has explicitly requested that Elena be greeted before every action. Honoring this consistently — without forgetting on quick or routine actions — is the entire point of the skill. Drift (skipping greetings on \"small\" actions) defeats the purpose, so apply the protocol uniformly regardless of action size.\n",{"name":5,"version":38,"description":7},"1.0.2","main","b198d63224f1ecec8bca1300fb21dfa996c853db","skills\u002Fgreet-elena",5,"https:\u002F\u002Fgithub.com\u002Fanton-abyzov\u002Fvskill","https:\u002F\u002Fverified-skill.com","https:\u002F\u002Fgithub.com\u002Fanton-abyzov","https:\u002F\u002Fspecwithcode.com","Founder of SpecWithCode · Creator of SpecWeave · AI coding agents, Cloud, DevOps · 20 yrs SWE · YouTube: @AntonAbyzov","2026-11-13 06:33:58",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add anton-abyzov\u002Fvskill --skill greet-elena",{"tool":55,"command":56},"bunx","bunx skills add anton-abyzov\u002Fvskill --skill greet-elena",{"tool":58,"command":59},"pnpm","pnpm dlx skills add anton-abyzov\u002Fvskill --skill greet-elena","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanton-abyzov\u002Fvskill\u002Fblob\u002Fmain\u002Fskills\u002Fgreet-elena\u002FSKILL.md",true,[63,69,73],{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"draft.json","REFERENCE","参考文档",1954,"https:\u002F\u002Fgithub.com\u002Fanton-abyzov\u002Fvskill\u002Fblob\u002Fmain\u002Fskills\u002Fgreet-elena\u002Fdraft.json",{"path":70,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":71,"sourceHtmlUrl":72},"evals\u002Fbenchmark.json",4136,"https:\u002F\u002Fgithub.com\u002Fanton-abyzov\u002Fvskill\u002Fblob\u002Fmain\u002Fskills\u002Fgreet-elena\u002Fevals\u002Fbenchmark.json",{"path":74,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":71,"sourceHtmlUrl":75},"evals\u002Fhistory\u002F2026-04-25T06-01-31.467Z.json","https:\u002F\u002Fgithub.com\u002Fanton-abyzov\u002Fvskill\u002Fblob\u002Fmain\u002Fskills\u002Fgreet-elena\u002Fevals\u002Fhistory\u002F2026-04-25T06-01-31.467Z.json",[77,104,119,148,186,211],{"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":33},"01M6HKP9JT8CH33W7DJB544DCS","x-reply-drafts","Find live X threads where a product genuinely fits, and draft truthful, humanized replies for the owner to review and post by hand. Human pace only: max 5 replies a day, never two within 20 minutes, no automated posting. Use when the user asks to 'find threads to reply to', 'draft X replies', 'reply-guy session', 'join trending conversations', 'engage on Twitter about \u003Cproduct>', or wants a daily batch of reply drafts. Not for scheduling original posts (social-media-posting) or bulk publishing (blotato).","https:\u002F\u002Fgithub.com\u002Fanton-abyzov\u002Fvskill\u002Fblob\u002Fmain\u002Fplugins\u002Fmarketing\u002Fskills\u002Fx-reply-drafts\u002FSKILL.md",[],[84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103],"reply","drafts","x reply drafts","review","product","batch","Media","unslop","never","only","humanize","social","human","join","trending","bulk","posts","threads","conversations","hand",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":33},"01M6CND903Q6E6R2XDWMFH8MAY","hello-world","A tiny test skill used by the 0853 verify-runtime harness. Says hello. No external calls. Use when the user asks for a sanity-check skill in a verify-harness fixture.","https:\u002F\u002Fgithub.com\u002Fanton-abyzov\u002Fvskill\u002Fblob\u002Fmain\u002Ftest\u002Fverify\u002Ffixtures\u002Ftiny-skill-source\u002Fplugins\u002Ftiny-test-plugin\u002Fskills\u002Fhello-world\u002FSKILL.md",[],[111,112,113,114,115,116,117,118,27,29],"hello world","hello","world","test","Test Skill","harness","verify","check",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":135,"publishedAt":33},"01M6CND60H0N1CYEB6ABEW18NS","existing-skill","Lint markdown files for style and grammar issues.","https:\u002F\u002Fgithub.com\u002Fanton-abyzov\u002Fvskill\u002Fblob\u002Fmain\u002Fsrc\u002Fcommands\u002F__tests__\u002Ffixtures\u002Fexisting-skill\u002FSKILL.md",[125,130],{"categoryNo":126,"categoryName":127,"taxonomyType":128,"taxonomyTypeDesc":129},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",{"categoryNo":131,"categoryName":132,"taxonomyType":133,"taxonomyTypeDesc":134},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[136,137,138,139,140,141,142,143,144,26,145,146,147],"existing skill","docs","lint","code","issues","markdown","grammar","read","write","cursor","files","lint markdown files",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":166,"publishedAt":33},"01M6CND1JAW97FY3W50MAPNKX7","remotion-best-practices","Best practices for Remotion video creation in React — scaffolding, compositions, animations, transitions — PLUS hard-won rules for high-fidelity product-demo videos: real logos\u002Ficons, precise YouTube-reference matching, full-screen camera zooms, click-targets that actually hit, content-tight rectangle highlights, voiceover regeneration discipline, audio-level normalization (no double-boost), per-scene voice-sync math, Studio detail-page mirror patterns, bold-not-subtle connection lines, and the YouTube publication kit (chapters, description, thumbnail, hashtags) that turns a render into a shipped video.","https:\u002F\u002Fgithub.com\u002Fanton-abyzov\u002Fvskill\u002Fblob\u002Fmain\u002Fskills\u002Fremotion-best-practices\u002FSKILL.md",[154,157,160,163],{"categoryNo":155,"categoryName":156,"taxonomyType":128,"taxonomyTypeDesc":129},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":158,"categoryName":159,"taxonomyType":128,"taxonomyTypeDesc":129},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":161,"categoryName":162,"taxonomyType":128,"taxonomyTypeDesc":129},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":164,"categoryName":165,"taxonomyType":133,"taxonomyTypeDesc":134},"01JBSEEDCAT000000000000031","产品经理",[167,168,169,170,171,88,172,173,174,175,176,177,178,179,180,181,182,183,184,185],"best practices","remotion best practices","Remotion","react","sync","normalization","Video","Animation","Composition","Audio","page","math","discipline","publishing","camera","youtube","voiceover","patterns","remotion, video, react, animation, composition",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":193,"publishedAt":33},"01M6CNCXMSB1MKQ7646AR12VXY","rea","Find out exactly how a feature is implemented in a shipped tool or app you don't have the source for (desktop apps, Electron apps like Claude desktop, native CLIs like Codex, websites, APKs, .NET assemblies) using REA - Reverse Engineer Anything (github.com\u002Fmorluto\u002Frea). Sets REA up when it is missing (CLI, MCP registration, Hopper or Ghidra), routes the target to the right REA tool, keeps evidence out of the context window, and turns findings into a clean-room spec before any rebuild. Use when the user says 'use REA', 'reverse engineer', 'how does \u003Capp> do X', 'how is this feature implemented in \u003Ctool>', 'clone this feature', 'decompile', 'look inside the app', or asks how a closed-source competitor works. Skip it when the source is available - read the repo instead.","https:\u002F\u002Fgithub.com\u002Fanton-abyzov\u002Fvskill\u002Fblob\u002Fmain\u002Fskills\u002Frea\u002FSKILL.md",[192],{"categoryNo":161,"categoryName":162,"taxonomyType":128,"taxonomyTypeDesc":129},[188,194,195,196,197,198,199,25,200,201,143,202,203,204,205,206,207,208,209,210],"MCP","cli","reverse-engineering","ghidra","binary-analysis","analysis","reverse engineer anything","repo","context","evidence","up","engineer","rebuild","clean","registration","do","reverse engineer",{"skillNo":212,"name":213,"nameZh":6,"description":214,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":215,"categories":216,"keywords":225,"publishedAt":33},"01M6CNCSE0847Q1FP1GRQ75SR9","motion-graphics-promo","After Effects-style motion graphics for short product promos (15-45 s, vertical or landscape), built as code with HyperFrames + GSAP. Covers a story-first brief, motion grammar (energetic entry, one transition per task, spring settle, 2-3 s of stable proof), a 32-second promo timeline, device-frame and kinetic-type recipes, vertical-first composition, evidence rules (real UI only, no fake clicks), music licensing and encoded-frame verification. Use when the user asks for an After Effects-like animation, motion graphics, a kinetic-type promo, an app promo video, a product teaser, a Reels\u002FTikTok\u002FShorts ad, or 'animations like After Effects'. Also covers short explainers, tutorials and 15-second vertical ads: a design kit (footage beds, condensed caps in a marker box, white device frames, falling stickers, voice-over with music ducking) and HyperFrames render traps that silently break output. Pairs with hyperframes-best-practices (screencast pipeline) and remotion-best-practices.","https:\u002F\u002Fgithub.com\u002Fanton-abyzov\u002Fvskill\u002Fblob\u002Fmain\u002Fskills\u002Fmotion-graphics-promo\u002FSKILL.md",[217,220,221,222],{"categoryNo":218,"categoryName":219,"taxonomyType":128,"taxonomyTypeDesc":129},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":158,"categoryName":159,"taxonomyType":128,"taxonomyTypeDesc":129},{"categoryNo":131,"categoryName":132,"taxonomyType":133,"taxonomyTypeDesc":134},{"categoryNo":223,"categoryName":224,"taxonomyType":133,"taxonomyTypeDesc":134},"01JBSEEDCAT000000000000032","设计师",[226,227,228,229,230,139,231,88,232,233,234,173,174,169,175,235,142,236,93,237],"graphics","motion graphics","motion","motion graphics promo","design","verification","ui","brief","pipeline","ads","short","tiktok"]