[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DRZV8RS3CF8F6KPBVYS3G5":3,"skill-same:01M7DRZV8RS3CF8F6KPBVYS3G5":62},{"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":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":47,"install":48,"resources":61},"01M7DRZV8RS3CF8F6KPBVYS3G5","workorai",null,"WorkorAI talent-marketplace skill: candidates search jobs and manage applications; employers run the job lifecycle and get ranked candidate matches with white-box fit explanations.","Hazek-dc\u002FPresensiGuru_FaceNet_EMAR","Hazek-dc","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F75208960?v=4","01M7DEQV5B4YGS86A81DYH81DR","Hazek","01M7DEQV5XP4TM0C6NTHXCXCHR",1,"MIT","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fworkorai\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: workorai\ndescription: \"WorkorAI talent-marketplace skill: candidates search jobs and manage applications; employers run the job lifecycle and get ranked candidate matches with white-box fit explanations.\"\ncategory: productivity\nrisk: critical\nsource: community\nsource_repo: work0r-ai\u002Fagent-kit\nsource_type: community\ndate_added: \"2026-07-03\"\nauthor: work0r-ai\ntags: [job-search, hiring, recruiting, talent-marketplace, mcp]\ntools: [claude, cursor, gemini]\nlicense: \"MIT\"\nlicense_source: \"https:\u002F\u002Fgithub.com\u002Fwork0r-ai\u002Fagent-kit\u002Fblob\u002Fmain\u002Fskills\u002Fworkorai\u002FLICENSE.txt\"\n---\n\n# WorkorAI\n\n## Overview\n\nWorkorAI is a talent marketplace exposed to agents through an MCP server\n(streamable HTTP at https:\u002F\u002Fworkorai.com\u002Fmcp, listed on the official MCP\nRegistry as `io.github.work0r-ai\u002Fworkorai`). This skill routes requests by\nintent across the dual-role tool surface: 9 `candidate.*` tools (job search,\njob detail, applications, apply, invitations, saved jobs) and the\n`employer.*` tools (job lifecycle, candidate discovery, invitations,\napplicant review). Employer candidate discovery returns tiered rankings\n(best\u002Fgood\u002Fweak) with a white-box match explanation per candidate — fit\nscore, skills proven in interview, gaps, and a quotable rationale — instead\nof a black-box score.\n\n## When to Use This Skill\n\n- Use when a user asks to find a job, search vacancies, apply to a position,\n  or track their applications (\"find me a job\", \"ищу работу\").\n- Use when an employer wants to post, publish, update, close, or archive a\n  job on WorkorAI.\n- Use when an employer asks to find, rank, compare, or evaluate candidates,\n  or asks why a candidate matches a role.\n- Use when a user needs to set up or troubleshoot the WorkorAI MCP\n  connection and API key onboarding.\n\n## How It Works\n\n### Step 1: Connect the MCP server\n\nAdd the WorkorAI MCP server to your agent's MCP configuration. For Claude\nCode:\n\n```bash\nclaude mcp add --transport http workorai https:\u002F\u002Fworkorai.com\u002Fmcp\n```\n\nIf the user has no API key yet, call the `request_access` tool and follow\nthe onboarding it returns.\n\n### Step 2: Route by role and intent\n\nDetect whether the request is a candidate flow or an employer flow, then use\nthe matching tool group:\n\n- Candidate: `candidate.search_jobs`, `candidate.get_job`,\n  `candidate.apply_to_job`, `candidate.get_applications`,\n  `candidate.accept_invitation` \u002F `candidate.decline_invitation`,\n  `candidate.withdraw_application`, `candidate.set_saved_job`,\n  `candidate.get_saved_jobs`.\n- Employer: `employer.create_job` → `employer.publish_job` →\n  `employer.close_job` \u002F `employer.archive_job` for the lifecycle;\n  `employer.search_candidates_for_job` or\n  `employer.search_candidates_by_query` for discovery;\n  `employer.invite_candidate`, `employer.list_applicants`,\n  `employer.get_applicant_detail`, `employer.set_review_status` for\n  pipeline work.\n\n### Step 3: Explain matches with white-box data\n\nWhen presenting employer search results, keep the tier structure\n(best\u002Fgood\u002Fweak) and surface each candidate's `matchExplanation`: fit score,\ninterview-proven skills, gaps, and rationale. For deeper comparison, fetch\nper-candidate interview evidence with `employer.get_candidate_evidence` and\n`employer.get_applicant_transcript`.\n\n## Examples\n\n### Example 1: Candidate job search\n\n```\nUser: \"Find me remote TypeScript jobs and apply to the best one.\"\nAgent: candidate.search_jobs(query=\"TypeScript\", remote=true)\n       → present ranked results → candidate.get_job(id)\n       → confirm with the user → candidate.apply_to_job(id)\n```\n\n### Example 2: Employer candidate discovery\n\n```\nUser: \"Who are the best candidates for my Senior Backend role?\"\nAgent: employer.search_candidates_for_job(jobId)\n       → report Best tier with each candidate's fit score, proven\n         skills, and gaps → employer.invite_candidate on approval\n```\n\n## Best Practices\n\n- ✅ Confirm with the user before applying, inviting, or changing job\n  status — these are visible, stateful marketplace actions.\n- ✅ Quote the white-box match explanation when recommending a candidate,\n  so the employer sees why, not just a score.\n- ✅ Use `request_access` for key onboarding instead of asking users to\n  paste credentials into chat.\n- ❌ Don't fabricate fit scores or ranks — only report what the tools\n  return.\n- ❌ Don't apply to jobs or send invitations in bulk without explicit\n  user approval.\n\n## Limitations\n\n- Requires a WorkorAI account and API key; tools fail without a valid key.\n- This skill does not replace environment-specific validation, testing, or\n  expert review.\n- Stop and ask for clarification if required inputs, permissions, or safety\n  boundaries are missing.\n\n## Security & Safety Notes\n\n- All operations go through the remote WorkorAI MCP server over HTTPS; the\n  skill itself runs no shell commands.\n- Mutating tools (apply, withdraw, invite, publish, close, delete) should\n  be preceded by an explicit user confirmation.\n- Treat API keys as secrets: store them in MCP client configuration, never\n  in chat transcripts or committed files.\n\n## Additional Resources\n\n- [Source repository](https:\u002F\u002Fgithub.com\u002Fwork0r-ai\u002Fagent-kit) — full skill\n  with reference files and agents (npm: `@workorai\u002Fagent-kit`)\n- [WorkorAI MCP endpoint](https:\u002F\u002Fworkorai.com\u002Fmcp)\n","# WorkorAI\n\n## Overview\n\nWorkorAI is a talent marketplace exposed to agents through an MCP server\n(streamable HTTP at https:\u002F\u002Fworkorai.com\u002Fmcp, listed on the official MCP\nRegistry as `io.github.work0r-ai\u002Fworkorai`). This skill routes requests by\nintent across the dual-role tool surface: 9 `candidate.*` tools (job search,\njob detail, applications, apply, invitations, saved jobs) and the\n`employer.*` tools (job lifecycle, candidate discovery, invitations,\napplicant review). Employer candidate discovery returns tiered rankings\n(best\u002Fgood\u002Fweak) with a white-box match explanation per candidate — fit\nscore, skills proven in interview, gaps, and a quotable rationale — instead\nof a black-box score.\n\n## When to Use This Skill\n\n- Use when a user asks to find a job, search vacancies, apply to a position,\n  or track their applications (\"find me a job\", \"ищу работу\").\n- Use when an employer wants to post, publish, update, close, or archive a\n  job on WorkorAI.\n- Use when an employer asks to find, rank, compare, or evaluate candidates,\n  or asks why a candidate matches a role.\n- Use when a user needs to set up or troubleshoot the WorkorAI MCP\n  connection and API key onboarding.\n\n## How It Works\n\n### Step 1: Connect the MCP server\n\nAdd the WorkorAI MCP server to your agent's MCP configuration. For Claude\nCode:\n\n```bash\nclaude mcp add --transport http workorai https:\u002F\u002Fworkorai.com\u002Fmcp\n```\n\nIf the user has no API key yet, call the `request_access` tool and follow\nthe onboarding it returns.\n\n### Step 2: Route by role and intent\n\nDetect whether the request is a candidate flow or an employer flow, then use\nthe matching tool group:\n\n- Candidate: `candidate.search_jobs`, `candidate.get_job`,\n  `candidate.apply_to_job`, `candidate.get_applications`,\n  `candidate.accept_invitation` \u002F `candidate.decline_invitation`,\n  `candidate.withdraw_application`, `candidate.set_saved_job`,\n  `candidate.get_saved_jobs`.\n- Employer: `employer.create_job` → `employer.publish_job` →\n  `employer.close_job` \u002F `employer.archive_job` for the lifecycle;\n  `employer.search_candidates_for_job` or\n  `employer.search_candidates_by_query` for discovery;\n  `employer.invite_candidate`, `employer.list_applicants`,\n  `employer.get_applicant_detail`, `employer.set_review_status` for\n  pipeline work.\n\n### Step 3: Explain matches with white-box data\n\nWhen presenting employer search results, keep the tier structure\n(best\u002Fgood\u002Fweak) and surface each candidate's `matchExplanation`: fit score,\ninterview-proven skills, gaps, and rationale. For deeper comparison, fetch\nper-candidate interview evidence with `employer.get_candidate_evidence` and\n`employer.get_applicant_transcript`.\n\n## Examples\n\n### Example 1: Candidate job search\n\n```\nUser: \"Find me remote TypeScript jobs and apply to the best one.\"\nAgent: candidate.search_jobs(query=\"TypeScript\", remote=true)\n       → present ranked results → candidate.get_job(id)\n       → confirm with the user → candidate.apply_to_job(id)\n```\n\n### Example 2: Employer candidate discovery\n\n```\nUser: \"Who are the best candidates for my Senior Backend role?\"\nAgent: employer.search_candidates_for_job(jobId)\n       → report Best tier with each candidate's fit score, proven\n         skills, and gaps → employer.invite_candidate on approval\n```\n\n## Best Practices\n\n- ✅ Confirm with the user before applying, inviting, or changing job\n  status — these are visible, stateful marketplace actions.\n- ✅ Quote the white-box match explanation when recommending a candidate,\n  so the employer sees why, not just a score.\n- ✅ Use `request_access` for key onboarding instead of asking users to\n  paste credentials into chat.\n- ❌ Don't fabricate fit scores or ranks — only report what the tools\n  return.\n- ❌ Don't apply to jobs or send invitations in bulk without explicit\n  user approval.\n\n## Limitations\n\n- Requires a WorkorAI account and API key; tools fail without a valid key.\n- This skill does not replace environment-specific validation, testing, or\n  expert review.\n- Stop and ask for clarification if required inputs, permissions, or safety\n  boundaries are missing.\n\n## Security & Safety Notes\n\n- All operations go through the remote WorkorAI MCP server over HTTPS; the\n  skill itself runs no shell commands.\n- Mutating tools (apply, withdraw, invite, publish, close, delete) should\n  be preceded by an explicit user confirmation.\n- Treat API keys as secrets: store them in MCP client configuration, never\n  in chat transcripts or committed files.\n\n## Additional Resources\n\n- [Source repository](https:\u002F\u002Fgithub.com\u002Fwork0r-ai\u002Fagent-kit) — full skill\n  with reference files and agents (npm: `@workorai\u002Fagent-kit`)\n- [WorkorAI MCP endpoint](https:\u002F\u002Fworkorai.com\u002Fmcp)\n",{"name":5,"risk":24,"tags":25,"tools":31,"author":35,"source":36,"license":15,"category":37,"date_added":38,"description":7,"source_repo":39,"source_type":36,"license_source":40},"critical",[26,27,28,29,30],"job-search","hiring","recruiting","talent-marketplace","mcp",[32,33,34],"claude","cursor","gemini","work0r-ai","community","productivity","2026-07-03","work0r-ai\u002Fagent-kit","https:\u002F\u002Fgithub.com\u002Fwork0r-ai\u002Fagent-kit\u002Fblob\u002Fmain\u002Fskills\u002Fworkorai\u002FLICENSE.txt","main","b1e4ffadb4f933bbbcaa03a83f8b9929171ac28b",".agents\u002Fskills\u002Fworkorai",0,"https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR","https:\u002F\u002Fgithub.com\u002FHazek-dc","2026-10-22 08:36:44",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill workorai",{"tool":54,"command":55},"bunx","bunx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill workorai",{"tool":57,"command":58},"pnpm","pnpm dlx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill workorai","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fworkorai\u002FSKILL.md",true,[],[63,70,77,84,91,98],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7DS6GGYRZAYD33PFPS8Z2T3","testing-best-practices","Laravel test design and review. Use when selecting coverage, naming or structuring tests, choosing assertions or test data, isolating dependencies, testing HTTP or security boundaries, improving suite performance, or reviewing test value. Use framework guidance or search-docs for Pest and PHPUnit syntax.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Ftesting-best-practices\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7DS6BC3AW7HTPRHE2TTVKWM","tailwindcss-development","Always invoke when the user's message includes 'tailwind' in any form. Also invoke for: building responsive grid layouts (multi-column card grids, product grids), flex\u002Fgrid page structures (dashboards with sidebars, fixed topbars, mobile-toggle navs), styling UI components (cards, tables, navbars, pricing sections, forms, inputs, badges), adding dark mode variants, fixing spacing or typography, and Tailwind v3\u002Fv4 work. The core use case: writing or fixing Tailwind utility classes in HTML templates (Blade, JSX, Vue). Skip for backend PHP logic, database queries, API routes, JavaScript with no HTML\u002FCSS component, CSS file audits, build tool configuration, and vanilla CSS.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Ftailwindcss-development\u002FSKILL.md",[],[],{"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":19},"01M7DS66GE6B11MYJDVC74HXM4","laravel-best-practices","Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization and security patterns, validation, error handling, queue and job configuration, route definitions, and architectural decisions. Also use for Laravel code reviews and refactoring existing Laravel code to follow best practices. Covers any task involving Laravel backend PHP code patterns.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Flaravel-best-practices\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7DS5ZW717DMS6P1E90AQCKV","infer-conventions","Use this skill to analyze how a Laravel application is actually written and record its conventions as shared rules. Trigger when the user wants to detect, infer, document, or standardize project conventions or coding style, set up or grow `.ai\u002Frules`, resolve mixed or conflicting patterns (e.g. \"are we using Form Requests or inline validation?\"), or onboard agents and teammates to \"how we do things here\". Covers: a systematic sweep of ~49 Laravel convention dimensions (validation, models, architecture, testing, frontend, database, console), open-ended house-pattern discovery, conflict reporting, and recording rules scoped to the right paths via the Boost `record-rule` MCP tool. Only run this skill when the user explicitly asks for it; never start a sweep as part of another task. Do not use for one-off code review, enforcing formatting a linter already handles, or editing `.ai\u002Frules` files by hand.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Finfer-conventions\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7DS5W12RGCVJTFQJ1N0GB8E","inertia-react-development","Develops Inertia.js v2 React client-side applications. Activates when creating React pages, forms, or navigation; using \u003CLink>, \u003CForm>, useForm, or router; working with deferred props, prefetching, or polling; or when user mentions React with Inertia, React pages, React forms, or React navigation.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Finertia-react-development\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M7DS5PVDPMPCWSK2RXPDC9BB","deploying-to-cloud","Deploys and manages Laravel applications on Laravel Cloud using the `cloud` CLI. Use when the user wants to deploy an app, ship to Cloud, create or manage applications, environments, databases, caches, object storage, queues, domains, instances, background processes, secrets, compute, scheduled tasks, or Laravel Cloud infrastructure; or check billing, usage, or spend. Triggers on deployment, shipping, Cloud management, environment setup, database provisioning, billing or usage queries, the `cloud` CLI, and Laravel Cloud deployment troubleshooting.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Fdeploying-to-cloud\u002FSKILL.md",[],[]]