[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78Z294ERFS0HM8MCTFWMSF1":3,"skill-same:01M78Z294ERFS0HM8MCTFWMSF1":56},{"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":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":39,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M78Z294ERFS0HM8MCTFWMSF1","cursor-custom-prompts",null,"Create effective custom prompts for Cursor AI using project rules, prompt engineering patterns, and\nreusable templates. Triggers on \"cursor prompts\", \"prompt engineering cursor\", \"better cursor prompts\",\n\"cursor instructions\", \"cursor prompt templates\".","jukeyman\u002Fjukeyman-skills","jukeyman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142960420?v=4","01M78FR4Y3DHMMCBCC0GXXNB3F","RICK JEFFERSON","01M78FR4Z8RVQRAD31Y5J7V6EB",1,"MIT","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--cursor-pack--cursor-custom-prompts\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"cursor-custom-prompts\"\ndescription: |\n  Create effective custom prompts for Cursor AI using project rules, prompt engineering patterns, and\n  reusable templates. Triggers on \"cursor prompts\", \"prompt engineering cursor\", \"better cursor prompts\",\n  \"cursor instructions\", \"cursor prompt templates\".\nallowed-tools: \"Read, Write, Edit, Bash(cmd:*)\"\nversion: 1.0.0\nlicense: MIT\nauthor: \"Jeremy Longshore \u003Cjeremy@intentsolutions.io>\"\ncompatible-with: claude-code, codex, openclaw\ntags: [saas, cursor, cursor-custom]\n---\n# Cursor Custom Prompts\n\nCreate effective prompts for Cursor AI. Covers prompt engineering fundamentals, reusable templates stored in project rules, and advanced techniques for consistent, high-quality code generation.\n\n## Prompt Anatomy\n\nA well-structured Cursor prompt has four parts:\n\n```\n1. CONTEXT   → @-mentions pointing to relevant code\n2. TASK      → What you want done (specific, actionable)\n3. CONSTRAINTS → Rules, patterns, limitations\n4. FORMAT    → How the output should look\n```\n\n### Example: All Four Parts\n\n```\n@src\u002Fapi\u002Fusers\u002Froute.ts @src\u002Ftypes\u002Fuser.ts         ← CONTEXT\n\nCreate a new API endpoint for updating user profiles. ← TASK\n\nConstraints:                                         ← CONSTRAINTS\n- Follow the same pattern as the users route\n- Use Zod for input validation\n- Return 400 for invalid input, 404 for missing user\n- Only allow updating: name, email, avatarUrl\n\nReturn the endpoint code and the Zod schema as       ← FORMAT\nseparate code blocks.\n```\n\n## Prompt Templates\n\n### Template: Feature Implementation\n\n```\n@[existing-similar-feature] @[relevant-types]\n\nImplement [feature name] following the pattern in [reference file].\n\nRequirements:\n- [requirement 1]\n- [requirement 2]\n- [requirement 3]\n\nConstraints:\n- Same error handling pattern as [reference]\n- Same file structure as [reference]\n- Include TypeScript types for all public interfaces\n```\n\n### Template: Bug Fix\n\n```\n@[buggy-file] @Lint Errors\n\nBug: [describe the incorrect behavior]\nExpected: [describe correct behavior]\nSteps to reproduce: [1, 2, 3]\n\nThe error message is: [paste error]\n\nFind the root cause and suggest a fix. Do not change\nthe public API surface.\n```\n\n### Template: Code Review\n\n```\n@[file-to-review]\n\nReview this code for:\n1. Logic errors or edge cases\n2. Security vulnerabilities (injection, XSS, auth bypass)\n3. Performance issues (N+1 queries, unnecessary re-renders)\n4. TypeScript type safety (any casts, missing generics)\n5. Naming and readability\n\nList issues as: [severity] [line\u002Farea] [description] [suggestion]\n```\n\n### Template: Test Generation\n\n```\n@[source-file] @[existing-test-file]\n\nGenerate tests for [function\u002Fclass name] covering:\n- Happy path with valid inputs\n- Edge cases: empty input, null, undefined, max values\n- Error cases: invalid input, missing required fields\n- Async behavior: success and failure scenarios\n\nFollow the same test structure as [existing-test-file].\nUse [vitest\u002Fjest\u002Fpytest] assertions.\n```\n\n### Template: Refactoring\n\n```\n@[file-to-refactor]\n\nRefactor this code to [goal]:\n- [specific change 1]\n- [specific change 2]\n\nDo NOT change:\n- The public API (function signatures, return types)\n- The test behavior (existing tests must still pass)\n- External imports\n```\n\n## Storing Prompts as Project Rules\n\nConvert frequently used prompts into `.cursor\u002Frules\u002F` for automatic injection:\n\n```yaml\n# .cursor\u002Frules\u002Fcode-generation.mdc\n---\ndescription: \"Standards for AI-generated code\"\nglobs: \"\"\nalwaysApply: true\n---\nWhen generating code, always:\n1. Add JSDoc comments on all exported functions\n2. Include error handling (never let functions throw unhandled)\n3. Use named exports (never default exports)\n4. Add `import type` for type-only imports\n5. Prefer const arrow functions for pure utilities\n6. Use discriminated unions over boolean flags\n\nWhen generating TypeScript:\n- Strict mode: no `any`, no `as` casts without justification\n- Prefer `unknown` over `any` for unknown types\n- Use `satisfies` operator for type narrowing\n- Infer types where TypeScript can; annotate where it cannot\n```\n\n```yaml\n# .cursor\u002Frules\u002Ftest-patterns.mdc\n---\ndescription: \"Test generation standards\"\nglobs: \"**\u002F*.test.ts,**\u002F*.spec.ts\"\nalwaysApply: false\n---\nWhen generating tests:\n- Use describe\u002Fit blocks with readable descriptions\n- Arrange\u002FAct\u002FAssert pattern (AAA)\n- One assertion per test (prefer multiple focused tests)\n- Mock external dependencies, not internal utilities\n- Use factory functions for test data (not inline objects)\n- Name test files: {module}.test.ts colocated with source\n```\n\n## Advanced Prompting Techniques\n\n### Chain of Thought\n\nForce the AI to reason before generating:\n\n```\n@src\u002Fservices\u002Fbilling.service.ts\n\nI need to add proration logic for subscription upgrades.\n\nBefore writing code, first:\n1. List the variables involved (current plan, new plan, billing cycle)\n2. Show the proration formula with a concrete example\n3. Identify edge cases (upgrade on last day, downgrade, free trial)\n\nThen implement based on your analysis.\n```\n\n### Few-Shot Examples\n\nProvide examples of what you want:\n\n```\nConvert these function signatures to the Result pattern:\n\nExample input:\n  async function getUser(id: string): Promise\u003CUser>\n\nExample output:\n  async function getUser(id: string): Promise\u003CResult\u003CUser, NotFoundError>>\n\nNow convert these:\n- async function createOrder(input: CreateOrderInput): Promise\u003COrder>\n- async function deleteAccount(userId: string): Promise\u003Cvoid>\n- async function sendEmail(to: string, body: string): Promise\u003Cboolean>\n```\n\n### Negative Constraints\n\nTell the AI what NOT to do:\n\n```\nCreate a React form component for user registration.\n\nDO NOT:\n- Use class components\n- Use any CSS-in-JS library\n- Add client-side validation (server validates)\n- Use controlled inputs for every field (use react-hook-form)\n- Import anything not already in package.json\n```\n\n### Iterative Refinement\n\nBuild up complexity in steps:\n\n```\nTurn 1: \"Create a basic Express route for GET \u002Fapi\u002Fproducts\"\nTurn 2: \"Add pagination with page and limit query params\"\nTurn 3: \"Add filtering by category and price range\"\nTurn 4: \"Add sorting by any field with asc\u002Fdesc direction\"\nTurn 5: \"Add input validation and comprehensive error responses\"\n```\n\nEach turn adds one layer. The AI maintains context from previous turns.\n\n## Common Prompt Anti-Patterns\n\n| Anti-Pattern | Problem | Better Approach |\n|-------------|---------|-----------------|\n| \"Make it better\" | Too vague | \"Add error handling for network failures\" |\n| \"Rewrite everything\" | Scope too large | \"Refactor the validation logic in lines 40-80\" |\n| No context files | AI guesses patterns | Always add @Files references |\n| Wall of text prompt | AI misses key points | Use numbered lists and headers |\n| \"Do what you think is best\" | AI makes assumptions | Specify requirements explicitly |\n\n## Enterprise Considerations\n\n- **Prompt libraries**: Maintain a team-shared library of effective prompts in a wiki or docs\u002F directory\n- **Standardization**: Use `.cursor\u002Frules\u002F` to encode team prompt standards so all developers get consistent behavior\n- **Security**: Never include real credentials, PII, or regulated data in prompts\n- **Reproducibility**: Document effective prompts alongside their output for knowledge sharing\n\n## Resources\n\n- [Cursor Rules Documentation](https:\u002F\u002Fdocs.cursor.com\u002Fcontext\u002Frules)\n- [@ Symbols Overview](https:\u002F\u002Fdocs.cursor.com\u002Fcontext\u002F@-symbols\u002Foverview)\n- [Prompt Engineering Guide](https:\u002F\u002Fplatform.openai.com\u002Fdocs\u002Fguides\u002Fprompt-engineering)\n","# Cursor Custom Prompts\n\nCreate effective prompts for Cursor AI. Covers prompt engineering fundamentals, reusable templates stored in project rules, and advanced techniques for consistent, high-quality code generation.\n\n## Prompt Anatomy\n\nA well-structured Cursor prompt has four parts:\n\n```\n1. CONTEXT   → @-mentions pointing to relevant code\n2. TASK      → What you want done (specific, actionable)\n3. CONSTRAINTS → Rules, patterns, limitations\n4. FORMAT    → How the output should look\n```\n\n### Example: All Four Parts\n\n```\n@src\u002Fapi\u002Fusers\u002Froute.ts @src\u002Ftypes\u002Fuser.ts         ← CONTEXT\n\nCreate a new API endpoint for updating user profiles. ← TASK\n\nConstraints:                                         ← CONSTRAINTS\n- Follow the same pattern as the users route\n- Use Zod for input validation\n- Return 400 for invalid input, 404 for missing user\n- Only allow updating: name, email, avatarUrl\n\nReturn the endpoint code and the Zod schema as       ← FORMAT\nseparate code blocks.\n```\n\n## Prompt Templates\n\n### Template: Feature Implementation\n\n```\n@[existing-similar-feature] @[relevant-types]\n\nImplement [feature name] following the pattern in [reference file].\n\nRequirements:\n- [requirement 1]\n- [requirement 2]\n- [requirement 3]\n\nConstraints:\n- Same error handling pattern as [reference]\n- Same file structure as [reference]\n- Include TypeScript types for all public interfaces\n```\n\n### Template: Bug Fix\n\n```\n@[buggy-file] @Lint Errors\n\nBug: [describe the incorrect behavior]\nExpected: [describe correct behavior]\nSteps to reproduce: [1, 2, 3]\n\nThe error message is: [paste error]\n\nFind the root cause and suggest a fix. Do not change\nthe public API surface.\n```\n\n### Template: Code Review\n\n```\n@[file-to-review]\n\nReview this code for:\n1. Logic errors or edge cases\n2. Security vulnerabilities (injection, XSS, auth bypass)\n3. Performance issues (N+1 queries, unnecessary re-renders)\n4. TypeScript type safety (any casts, missing generics)\n5. Naming and readability\n\nList issues as: [severity] [line\u002Farea] [description] [suggestion]\n```\n\n### Template: Test Generation\n\n```\n@[source-file] @[existing-test-file]\n\nGenerate tests for [function\u002Fclass name] covering:\n- Happy path with valid inputs\n- Edge cases: empty input, null, undefined, max values\n- Error cases: invalid input, missing required fields\n- Async behavior: success and failure scenarios\n\nFollow the same test structure as [existing-test-file].\nUse [vitest\u002Fjest\u002Fpytest] assertions.\n```\n\n### Template: Refactoring\n\n```\n@[file-to-refactor]\n\nRefactor this code to [goal]:\n- [specific change 1]\n- [specific change 2]\n\nDo NOT change:\n- The public API (function signatures, return types)\n- The test behavior (existing tests must still pass)\n- External imports\n```\n\n## Storing Prompts as Project Rules\n\nConvert frequently used prompts into `.cursor\u002Frules\u002F` for automatic injection:\n\n```yaml\n# .cursor\u002Frules\u002Fcode-generation.mdc\n---\ndescription: \"Standards for AI-generated code\"\nglobs: \"\"\nalwaysApply: true\n---\nWhen generating code, always:\n1. Add JSDoc comments on all exported functions\n2. Include error handling (never let functions throw unhandled)\n3. Use named exports (never default exports)\n4. Add `import type` for type-only imports\n5. Prefer const arrow functions for pure utilities\n6. Use discriminated unions over boolean flags\n\nWhen generating TypeScript:\n- Strict mode: no `any`, no `as` casts without justification\n- Prefer `unknown` over `any` for unknown types\n- Use `satisfies` operator for type narrowing\n- Infer types where TypeScript can; annotate where it cannot\n```\n\n```yaml\n# .cursor\u002Frules\u002Ftest-patterns.mdc\n---\ndescription: \"Test generation standards\"\nglobs: \"**\u002F*.test.ts,**\u002F*.spec.ts\"\nalwaysApply: false\n---\nWhen generating tests:\n- Use describe\u002Fit blocks with readable descriptions\n- Arrange\u002FAct\u002FAssert pattern (AAA)\n- One assertion per test (prefer multiple focused tests)\n- Mock external dependencies, not internal utilities\n- Use factory functions for test data (not inline objects)\n- Name test files: {module}.test.ts colocated with source\n```\n\n## Advanced Prompting Techniques\n\n### Chain of Thought\n\nForce the AI to reason before generating:\n\n```\n@src\u002Fservices\u002Fbilling.service.ts\n\nI need to add proration logic for subscription upgrades.\n\nBefore writing code, first:\n1. List the variables involved (current plan, new plan, billing cycle)\n2. Show the proration formula with a concrete example\n3. Identify edge cases (upgrade on last day, downgrade, free trial)\n\nThen implement based on your analysis.\n```\n\n### Few-Shot Examples\n\nProvide examples of what you want:\n\n```\nConvert these function signatures to the Result pattern:\n\nExample input:\n  async function getUser(id: string): Promise\u003CUser>\n\nExample output:\n  async function getUser(id: string): Promise\u003CResult\u003CUser, NotFoundError>>\n\nNow convert these:\n- async function createOrder(input: CreateOrderInput): Promise\u003COrder>\n- async function deleteAccount(userId: string): Promise\u003Cvoid>\n- async function sendEmail(to: string, body: string): Promise\u003Cboolean>\n```\n\n### Negative Constraints\n\nTell the AI what NOT to do:\n\n```\nCreate a React form component for user registration.\n\nDO NOT:\n- Use class components\n- Use any CSS-in-JS library\n- Add client-side validation (server validates)\n- Use controlled inputs for every field (use react-hook-form)\n- Import anything not already in package.json\n```\n\n### Iterative Refinement\n\nBuild up complexity in steps:\n\n```\nTurn 1: \"Create a basic Express route for GET \u002Fapi\u002Fproducts\"\nTurn 2: \"Add pagination with page and limit query params\"\nTurn 3: \"Add filtering by category and price range\"\nTurn 4: \"Add sorting by any field with asc\u002Fdesc direction\"\nTurn 5: \"Add input validation and comprehensive error responses\"\n```\n\nEach turn adds one layer. The AI maintains context from previous turns.\n\n## Common Prompt Anti-Patterns\n\n| Anti-Pattern | Problem | Better Approach |\n|-------------|---------|-----------------|\n| \"Make it better\" | Too vague | \"Add error handling for network failures\" |\n| \"Rewrite everything\" | Scope too large | \"Refactor the validation logic in lines 40-80\" |\n| No context files | AI guesses patterns | Always add @Files references |\n| Wall of text prompt | AI misses key points | Use numbered lists and headers |\n| \"Do what you think is best\" | AI makes assumptions | Specify requirements explicitly |\n\n## Enterprise Considerations\n\n- **Prompt libraries**: Maintain a team-shared library of effective prompts in a wiki or docs\u002F directory\n- **Standardization**: Use `.cursor\u002Frules\u002F` to encode team prompt standards so all developers get consistent behavior\n- **Security**: Never include real credentials, PII, or regulated data in prompts\n- **Reproducibility**: Document effective prompts alongside their output for knowledge sharing\n\n## Resources\n\n- [Cursor Rules Documentation](https:\u002F\u002Fdocs.cursor.com\u002Fcontext\u002Frules)\n- [@ Symbols Overview](https:\u002F\u002Fdocs.cursor.com\u002Fcontext\u002F@-symbols\u002Foverview)\n- [Prompt Engineering Guide](https:\u002F\u002Fplatform.openai.com\u002Fdocs\u002Fguides\u002Fprompt-engineering)\n",{"name":5,"tags":24,"author":28,"license":15,"version":29,"description":30,"allowed-tools":31,"compatible-with":32},[25,26,27],"saas","cursor","cursor-custom","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Create effective custom prompts for Cursor AI using project rules, prompt engineering patterns, and\nreusable templates. Triggers on \"cursor prompts\", \"prompt engineering cursor\", \"better cursor prompts\",\n\"cursor instructions\", \"cursor prompt templates\".\n","Read, Write, Edit, Bash(cmd:*)","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--cursor-pack--cursor-custom-prompts",0,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills","https:\u002F\u002Fgithub.com\u002Fjukeyman","https:\u002F\u002FRJBUSINESSSOLUTIONS.ORG","Credit and Finance Expert | Developer\r\n\r\nI'm Rick Jefferson, a seasoned credit and finance expert with over a decade of experience in financial literacy,","2026-07-13 07:03:29",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill cursor-custom-prompts",{"tool":48,"command":49},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill cursor-custom-prompts",{"tool":51,"command":52},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill cursor-custom-prompts","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--cursor-pack--cursor-custom-prompts\u002FSKILL.md",true,[],[57,64,71,78,85,93],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M79ANS2SM329NEP5ZCX106RR","zustand-store-creator","Create zustand store creator operations. Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category. Use when working with zustand store creator functionality. Trigger with phrases like \"zustand store creator\", \"zustand creator\", \"zustand\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M79AMZKP4YDEZ7EHG1Y7PP74","zero-trust-config-helper","Configure with zero trust config helper operations. Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category. Use when configuring systems or services. Trigger with phrases like \"zero trust config helper\", \"zero helper\", \"zero\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M79AMJSBCEJQNBTYNAHYN5HM","zapier-integration-helper","Assist with zapier integration helper operations. Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like \"zapier integration helper\", \"zapier helper\", \"zapier\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M79AHJZGVMARS13VFQYRR1MP","yaml-config-validator","Validate yaml config validator operations. Auto-activating skill for DevOps Basics.\nTriggers on: yaml config validator, yaml config validator\nPart of the DevOps Basics skill category. Use when configuring systems or services. Trigger with phrases like \"yaml config validator\", \"yaml validator\", \"yaml\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyaml-config-validator\u002FSKILL.md",[],[],{"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":15,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M79AHGDZRN0020RDQSQDPAM8","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M79AHCYJ9FV9RMHQ24HDRN33","xss-vulnerability-scanner","Scan xss vulnerability scanner operations. Auto-activating skill for Security Fundamentals.\nTriggers on: xss vulnerability scanner, xss vulnerability scanner\nPart of the Security Fundamentals skill category. Use when working with xss vulnerability scanner functionality. Trigger with phrases like \"xss vulnerability scanner\", \"xss scanner\", \"xss\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxss-vulnerability-scanner\u002FSKILL.md",[],[]]