[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CT0SDTEWJHHWX9YAXP5XMS":3,"skill-same:01M7CT0SDTEWJHHWX9YAXP5XMS":46},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7CT0SDTEWJHHWX9YAXP5XMS","application-form-filler",null,"Fill out job application form fields with context-aware, tailored answers drawn from the candidate's CV and the job description","Henrique1601\u002FSkiilsToIAs","Henrique1601","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F92006691?v=4","01M7CRXVT0GVXVK80JT1GR687S","Henrique Bezerra Dos Santos","01M7CRXVTN5Y8TMWJ1MDSKCQ1T",0,"MIT","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fcareer\u002Fapplication-form-filler\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: application-form-filler\ndescription: Fill out job application form fields with context-aware, tailored answers drawn from the candidate's CV and the job description\n---\n\n# Application Form Filler\n\n## When to Use This Skill\n\nUse this skill when the user wants to:\n- Answer specific questions on a job application form\n- Fill out text fields on Greenhouse, Lever, Ashby, Workday, or any ATS\n- Write responses to \"tell us about yourself\" or \"why do you want to work here\" prompts\n- Get clean, copy-pasteable answers to application questions\n- Mentions: \"fill this out\", \"what do I write here\", \"answer this question\", \"application form\", \"form field\"\n\n## Core Principle\n\nApplication form answers should be direct and specific — not a cover letter crammed into a text box. Each field has a purpose. Answer that purpose clearly, then stop.\n\n**The answer should feel like:** A real person typed it, not a template was filled in.\n\n## Before Answering\n\nAlways read:\n1. **The job description** — mirror its language and priorities\n2. **The candidate's CV\u002Fprofile** — pull real projects, roles, and metrics\n3. **The specific question** — answer exactly what was asked, not what you wish was asked\n\nIf the user hasn't provided a CV or JD, ask for them before writing.\n\n## Question Types and How to Handle Each\n\n---\n\n### Type 1: Experience\u002FBackground Questions\n\n**Examples:**\n- \"How many years of experience do you have with [technology]?\"\n- \"Describe your experience with [domain]\"\n- \"What backend frameworks have you used?\"\n\n**Format:**\n```\n[Technology\u002Fskill] — [X years]. [One sentence on what you used it for, with a\nspecific project or context]. [Optional: secondary tools in the same category].\n```\n\n**Rules:**\n- Lead with the most used\u002Frelevant technology\n- Give years honestly — don't inflate\n- Anchor every claim to a real project or role\n- For \"describe experience\" questions: 2-4 sentences max, one project per sentence\n- If experience is indirect (adjacent domain), say so and pivot to what is relevant\n\n---\n\n### Type 2: Why This Company \u002F What Interests You\n\n**Examples:**\n- \"Why do you want to work at [Company]?\"\n- \"What interests you about this role?\"\n- \"Why are you a good fit?\"\n\n**Format:**\n```\n[Specific thing about the company\u002Frole that's genuinely interesting — not generic].\n[How that connects to something the candidate has actually worked on].\n[Optional: one line on why this domain, not just this company].\n```\n\n**Rules:**\n- Must be specific to this company — no boilerplate\n- Research the company before answering if needed\n- Connect to real work, not aspirations\n- Keep it under 150 words for a form field\n- Don't repeat the JD back to them\n\n---\n\n### Type 3: Portfolio \u002F Work Samples\n\n**Examples:**\n- \"Include any other samples of work you're proud of\"\n- \"Link to relevant projects or repositories\"\n- \"Describe a project you've built end-to-end\"\n\n**Format:**\nList projects with one-line descriptions and links. Lead with the most relevant.\n\n```\n[Project Name] ([live URL] | [github URL]) — [one line: what it is and one\nproof point]. [Stack if relevant].\n```\n\n**Rules:**\n- Only include projects relevant to the role\n- Always include links (live demo > GitHub > nothing)\n- If the project has paying users or measurable usage, say so — once\n- Don't pad with irrelevant projects to look prolific\n\n---\n\n### Type 4: Technical Skill Questions\n\n**Examples:**\n- \"Which frontend frameworks have you used most extensively?\"\n- \"Rate your proficiency in Python\"\n- \"Describe your experience with cloud infrastructure\"\n\n**Format:**\nFor open-text fields:\n```\n[Primary skill] — [X years]. [Specific use: what you built with it, in what context].\n[Secondary skill] — [X years]. [Same].\n[Note any relevant gaps honestly].\n```\n\nFor rating\u002Fdropdown fields: pick the honest level — don't optimize for the highest rating if it's not accurate.\n\n**Rules:**\n- Years + context beats years alone\n- Acknowledge gaps rather than hiding them\n- If asked to rate, rate honestly — inflated ratings create problems in technical interviews\n- For stacks you've used but not recently, note it\n\n---\n\n### Type 5: Open-Ended \u002F \"Tell Us About Yourself\"\n\n**Examples:**\n- \"Tell us about yourself\"\n- \"Describe your professional background\"\n- \"What are you looking for in your next role?\"\n\n**Format:**\n```\nCurrent role + what you do there (1 sentence).\nRelevant prior experience, briefly (1 sentence).\nWhat you're looking for \u002F why this role (1-2 sentences — specific to the company).\nOptional: one project or side work that's relevant (1 sentence).\n```\n\n**Rules:**\n- Start with current role, not education\n- Keep to 100-200 words for most form fields\n- End on the forward-looking note (what you want, not where you've been)\n- No trait statements (\"I'm passionate about...\") — just facts and projects\n\n---\n\n### Type 6: Situational \u002F Behavioral Questions\n\n**Examples:**\n- \"Describe a time you solved a complex technical problem\"\n- \"Tell us about a project you led end-to-end\"\n- \"How do you handle working across multiple teams?\"\n\n**Format:** Condensed STAR (no labels, just flow)\n\n```\n[Context in one sentence]. [What you specifically did — 2 sentences]. [Outcome\nwith a metric if possible — 1 sentence].\n```\n\n**Rules:**\n- Be specific — name the project, the tech, the team size\n- Don't generalize (\"I always approach problems by...\")\n- Keep to 150-250 words\n- First-person, active voice throughout\n- End with the result, not the lesson learned (save that for interviews)\n\n---\n\n### Type 7: Opinion \u002F Vision Questions\n\n**Examples:**\n- \"Which technologies do you think are most important for the future?\"\n- \"What would you learn if you had unlimited time?\"\n- \"Where do you see AI\u002F[domain] in 5 years?\"\n\n**Format:**\nAnswer with a genuine opinion. Pick one or two things and explain the reasoning briefly.\n\n**Rules:**\n- Have an actual point of view — vague answers are forgettable\n- Ground opinions in domain knowledge or real experience\n- Keep to 100-150 words\n- Don't hedge everything — commit to a view, acknowledge it's one perspective\n\n---\n\n## Output Format\n\nAlways wrap the answer in a plain code block so it's clean to copy-paste:\n\n```\n[Answer text here]\n```\n\nIf providing multiple answers (one per field), use separate code blocks with a label above each:\n\n**Years of React experience:**\n```\n4 years. Used it across Screenr (agentic hiring SaaS), a Tauri-based POS\nsystem, and several client projects. Also used Next.js where SSR was needed.\n```\n\n**Describe your backend experience:**\n```\n...\n```\n\n## Length Calibration\n\n| Field type | Target length |\n|------------|---------------|\n| Single-line text | 1 sentence |\n| Short answer | 2-4 sentences |\n| Long answer \u002F textarea | 100-250 words |\n| \"Describe your experience\" | 150-300 words |\n| \"Tell us about yourself\" | 100-200 words |\n| Portfolio \u002F links section | List format, no prose |\n\nWhen in doubt, shorter is better. Recruiters skim form answers. The goal is to be clear and memorable, not comprehensive.\n\n## Common Mistakes to Avoid\n\n**Repeating the JD:**\n❌ \"I am interested in this role because you are looking for someone to build scalable backend systems...\"\n✅ \"What caught my attention was the real-time constraint — healthcare data at milliseconds latency is a different class of problem than most backend work.\"\n\n**Generic trait claims:**\n❌ \"I am a fast learner who thrives in collaborative environments\"\n✅ [Just describe the actual work — the traits come through]\n\n**Over-qualifying:**\n❌ \"While I may not have exactly 5 years, I believe my experience...\"\n✅ \"The role mentions 5 years — I'm at 3, but the systems I've shipped are production-facing.\"\n\n**Listing without context:**\n❌ \"React, Vue, Angular, Next.js, TypeScript, Node.js...\"\n✅ \"React is my primary frontend framework — 4 years across Screenr and several client projects. Vue and Angular for about 3 years each, mostly dashboards and admin tooling.\"\n\n**Padding to fill space:**\n❌ Adding projects or experience that aren't relevant just to look prolific\n✅ Include only what's relevant to this specific role\n","# Application Form Filler\n\n## When to Use This Skill\n\nUse this skill when the user wants to:\n- Answer specific questions on a job application form\n- Fill out text fields on Greenhouse, Lever, Ashby, Workday, or any ATS\n- Write responses to \"tell us about yourself\" or \"why do you want to work here\" prompts\n- Get clean, copy-pasteable answers to application questions\n- Mentions: \"fill this out\", \"what do I write here\", \"answer this question\", \"application form\", \"form field\"\n\n## Core Principle\n\nApplication form answers should be direct and specific — not a cover letter crammed into a text box. Each field has a purpose. Answer that purpose clearly, then stop.\n\n**The answer should feel like:** A real person typed it, not a template was filled in.\n\n## Before Answering\n\nAlways read:\n1. **The job description** — mirror its language and priorities\n2. **The candidate's CV\u002Fprofile** — pull real projects, roles, and metrics\n3. **The specific question** — answer exactly what was asked, not what you wish was asked\n\nIf the user hasn't provided a CV or JD, ask for them before writing.\n\n## Question Types and How to Handle Each\n\n---\n\n### Type 1: Experience\u002FBackground Questions\n\n**Examples:**\n- \"How many years of experience do you have with [technology]?\"\n- \"Describe your experience with [domain]\"\n- \"What backend frameworks have you used?\"\n\n**Format:**\n```\n[Technology\u002Fskill] — [X years]. [One sentence on what you used it for, with a\nspecific project or context]. [Optional: secondary tools in the same category].\n```\n\n**Rules:**\n- Lead with the most used\u002Frelevant technology\n- Give years honestly — don't inflate\n- Anchor every claim to a real project or role\n- For \"describe experience\" questions: 2-4 sentences max, one project per sentence\n- If experience is indirect (adjacent domain), say so and pivot to what is relevant\n\n---\n\n### Type 2: Why This Company \u002F What Interests You\n\n**Examples:**\n- \"Why do you want to work at [Company]?\"\n- \"What interests you about this role?\"\n- \"Why are you a good fit?\"\n\n**Format:**\n```\n[Specific thing about the company\u002Frole that's genuinely interesting — not generic].\n[How that connects to something the candidate has actually worked on].\n[Optional: one line on why this domain, not just this company].\n```\n\n**Rules:**\n- Must be specific to this company — no boilerplate\n- Research the company before answering if needed\n- Connect to real work, not aspirations\n- Keep it under 150 words for a form field\n- Don't repeat the JD back to them\n\n---\n\n### Type 3: Portfolio \u002F Work Samples\n\n**Examples:**\n- \"Include any other samples of work you're proud of\"\n- \"Link to relevant projects or repositories\"\n- \"Describe a project you've built end-to-end\"\n\n**Format:**\nList projects with one-line descriptions and links. Lead with the most relevant.\n\n```\n[Project Name] ([live URL] | [github URL]) — [one line: what it is and one\nproof point]. [Stack if relevant].\n```\n\n**Rules:**\n- Only include projects relevant to the role\n- Always include links (live demo > GitHub > nothing)\n- If the project has paying users or measurable usage, say so — once\n- Don't pad with irrelevant projects to look prolific\n\n---\n\n### Type 4: Technical Skill Questions\n\n**Examples:**\n- \"Which frontend frameworks have you used most extensively?\"\n- \"Rate your proficiency in Python\"\n- \"Describe your experience with cloud infrastructure\"\n\n**Format:**\nFor open-text fields:\n```\n[Primary skill] — [X years]. [Specific use: what you built with it, in what context].\n[Secondary skill] — [X years]. [Same].\n[Note any relevant gaps honestly].\n```\n\nFor rating\u002Fdropdown fields: pick the honest level — don't optimize for the highest rating if it's not accurate.\n\n**Rules:**\n- Years + context beats years alone\n- Acknowledge gaps rather than hiding them\n- If asked to rate, rate honestly — inflated ratings create problems in technical interviews\n- For stacks you've used but not recently, note it\n\n---\n\n### Type 5: Open-Ended \u002F \"Tell Us About Yourself\"\n\n**Examples:**\n- \"Tell us about yourself\"\n- \"Describe your professional background\"\n- \"What are you looking for in your next role?\"\n\n**Format:**\n```\nCurrent role + what you do there (1 sentence).\nRelevant prior experience, briefly (1 sentence).\nWhat you're looking for \u002F why this role (1-2 sentences — specific to the company).\nOptional: one project or side work that's relevant (1 sentence).\n```\n\n**Rules:**\n- Start with current role, not education\n- Keep to 100-200 words for most form fields\n- End on the forward-looking note (what you want, not where you've been)\n- No trait statements (\"I'm passionate about...\") — just facts and projects\n\n---\n\n### Type 6: Situational \u002F Behavioral Questions\n\n**Examples:**\n- \"Describe a time you solved a complex technical problem\"\n- \"Tell us about a project you led end-to-end\"\n- \"How do you handle working across multiple teams?\"\n\n**Format:** Condensed STAR (no labels, just flow)\n\n```\n[Context in one sentence]. [What you specifically did — 2 sentences]. [Outcome\nwith a metric if possible — 1 sentence].\n```\n\n**Rules:**\n- Be specific — name the project, the tech, the team size\n- Don't generalize (\"I always approach problems by...\")\n- Keep to 150-250 words\n- First-person, active voice throughout\n- End with the result, not the lesson learned (save that for interviews)\n\n---\n\n### Type 7: Opinion \u002F Vision Questions\n\n**Examples:**\n- \"Which technologies do you think are most important for the future?\"\n- \"What would you learn if you had unlimited time?\"\n- \"Where do you see AI\u002F[domain] in 5 years?\"\n\n**Format:**\nAnswer with a genuine opinion. Pick one or two things and explain the reasoning briefly.\n\n**Rules:**\n- Have an actual point of view — vague answers are forgettable\n- Ground opinions in domain knowledge or real experience\n- Keep to 100-150 words\n- Don't hedge everything — commit to a view, acknowledge it's one perspective\n\n---\n\n## Output Format\n\nAlways wrap the answer in a plain code block so it's clean to copy-paste:\n\n```\n[Answer text here]\n```\n\nIf providing multiple answers (one per field), use separate code blocks with a label above each:\n\n**Years of React experience:**\n```\n4 years. Used it across Screenr (agentic hiring SaaS), a Tauri-based POS\nsystem, and several client projects. Also used Next.js where SSR was needed.\n```\n\n**Describe your backend experience:**\n```\n...\n```\n\n## Length Calibration\n\n| Field type | Target length |\n|------------|---------------|\n| Single-line text | 1 sentence |\n| Short answer | 2-4 sentences |\n| Long answer \u002F textarea | 100-250 words |\n| \"Describe your experience\" | 150-300 words |\n| \"Tell us about yourself\" | 100-200 words |\n| Portfolio \u002F links section | List format, no prose |\n\nWhen in doubt, shorter is better. Recruiters skim form answers. The goal is to be clear and memorable, not comprehensive.\n\n## Common Mistakes to Avoid\n\n**Repeating the JD:**\n❌ \"I am interested in this role because you are looking for someone to build scalable backend systems...\"\n✅ \"What caught my attention was the real-time constraint — healthcare data at milliseconds latency is a different class of problem than most backend work.\"\n\n**Generic trait claims:**\n❌ \"I am a fast learner who thrives in collaborative environments\"\n✅ [Just describe the actual work — the traits come through]\n\n**Over-qualifying:**\n❌ \"While I may not have exactly 5 years, I believe my experience...\"\n✅ \"The role mentions 5 years — I'm at 3, but the systems I've shipped are production-facing.\"\n\n**Listing without context:**\n❌ \"React, Vue, Angular, Next.js, TypeScript, Node.js...\"\n✅ \"React is my primary frontend framework — 4 years across Screenr and several client projects. Vue and Angular for about 3 years each, mostly dashboards and admin tooling.\"\n\n**Padding to fill space:**\n❌ Adding projects or experience that aren't relevant just to look prolific\n✅ Include only what's relevant to this specific role\n",{"name":5,"description":7},"main","a73152352c0612252131e5cf84e91312a6cf17dc","career\u002Fapplication-form-filler","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs","https:\u002F\u002Fgithub.com\u002FHenrique1601","https:\u002F\u002Fbezerraportifolio.netlify.app\u002F","Full Stack Developer | React, Next.js, TypeScript, Node.js & IA | Construindo produtos digitais e soluções SaaS","2026-11-15 02:56:04",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Henrique1601\u002FSkiilsToIAs --skill application-form-filler",{"tool":38,"command":39},"bunx","bunx skills add Henrique1601\u002FSkiilsToIAs --skill application-form-filler",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Henrique1601\u002FSkiilsToIAs --skill application-form-filler","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fcareer\u002Fapplication-form-filler\u002FSKILL.md",true,[],[47,54,61,69,76,83],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7E2ANBW9V6AVX5JXNCEAWF8","rag-architect-agent","Agente Arquiteto de RAG, Embeddings & Busca Vetorial. Especialista em design e implementação de pipelines de Retrieval-Augmented Generation de alta fidelidade: chunking semântico, modelagem pgvector no PostgreSQL (Neon\u002FSupabase), busca híbrida (cosseno + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fcustom-agents\u002Frag-architect-agent\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7E29KKF8R02ZRGYE2MJM67G","rag-architecture-patterns","Padrões arquiteturais e implementação de pipelines RAG (Retrieval-Augmented Generation) de alta fidelidade para qualquer projeto ou sistema. Cobre chunking semântico, embeddings, busca híbrida (pgvector + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fai-agents\u002Frag-architecture-patterns\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":65,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7CWRA8E3BJ7CPY8N8EG28J1","skill-repair","Use this to fix and re-install agent skills that have failed installation.\nThis skill provides the necessary context and permissions to surgically update\nthe `manifest.json` after a fix has been applied.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fskill-repair\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7CWR66FZP8FA47WVZ4Z2EXC","security-scan","Scan your Claude Code configuration (.claude\u002F directory) for security vulnerabilities, misconfigurations, and injection risks using AgentShield. Checks CLAUDE.md, settings.json, MCP servers, hooks, and agent definitions.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-scan\u002FSKILL.md",[],[],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7CWR0QPY58QPTR1P759TFNG","security-review","Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment\u002Fsensitive features. Provides comprehensive security checklist and patterns.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-review\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7CWQXCE40XWT4FZ3VWZFGDP","security-bounty-hunter","Hunt for exploitable, bounty-worthy security issues in repositories. Focuses on remotely reachable vulnerabilities that qualify for real reports instead of noisy local-only findings.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-bounty-hunter\u002FSKILL.md",[],[]]