[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DP2BM4ZFVG51SJRBSYXGFK":3,"skill-same:01M7DP2BM4ZFVG51SJRBSYXGFK":51},{"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":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M7DP2BM4ZFVG51SJRBSYXGFK","postman-newman-automation",null,"Generate Newman CLI commands, configuration files, Jenkins pipeline scripts, and shell automation for running Postman collections in CI\u002FCD or local environments. Use this skill whenever the user wants to run Postman collections from the command line, automate API tests, integrate...","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\u002Fpostman-newman-automation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: postman-newman-automation\ndescription: Generate Newman CLI commands, configuration files, Jenkins pipeline scripts, and shell automation for running Postman collections in CI\u002FCD or local environments. Use this skill whenever the user wants to run Postman collections from the command line, automate API tests, integrate...\nrisk: unknown\nsource: https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Fapi-skill\u002Fpostman\u002Fpostman-to-newman\nsource_repo: LambdaTest\u002Fagent-skills\nsource_type: community\ndate_added: 2026-07-01\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Fblob\u002Fmain\u002FLICENSE\n---\n\n# Postman Newman Automation\n## When to Use\n\nUse this skill when you need generate Newman CLI commands, configuration files, Jenkins pipeline scripts, and shell automation for running Postman collections in CI\u002FCD or local environments. Use this skill whenever the user wants to run Postman collections from the command line, automate API tests, integrate...\n\n\nGenerates **Newman CLI** commands, **shell scripts**, and **Jenkins pipeline** configs\nfor running Postman collections in automated environments.\n\n---\n\n## Newman Basics\n\nNewman is Postman's CLI runner. Install with:\n```bash\nnpm install -g newman\n# Optional HTML reporter:\nnpm install -g newman-reporter-htmlextra\n```\n\n### Core Command Structure\n```bash\nnewman run \u003Ccollection> \\\n  --environment \u003Cenv-file> \\\n  --globals \u003Cglobals-file> \\\n  --iteration-count \u003Cn> \\\n  --iteration-data \u003Ccsv-or-json> \\\n  --reporters \u003Creporter-list> \\\n  --reporter-htmlextra-export \u003Coutput.html> \\\n  --reporter-junit-export \u003Cresults.xml> \\\n  --timeout-request \u003Cms> \\\n  --delay-request \u003Cms> \\\n  --bail \\\n  --color on\n```\n\n---\n\n## Step 1 — Gather Requirements\n\nAsk or infer from context:\n\n| Parameter | Question |\n|---|---|\n| Collection source | File path, URL, or Postman API UID? |\n| Environment | File path or inline variables? |\n| Reporter(s) | CLI only, HTML report, JUnit XML? |\n| Fail behavior | Stop on first failure (`--bail`) or run all? |\n| Iterations | Single run or data-driven (CSV\u002FJSON)? |\n| Target | Local shell, Jenkins, or both? |\n\n---\n\n## Step 2 — Generate Newman Command\n\n### Basic run (local)\n```bash\nnewman run collection.json \\\n  --environment environment.json \\\n  --reporters cli,htmlextra \\\n  --reporter-htmlextra-export reports\u002Freport.html \\\n  --bail\n```\n\n### Run from Postman API (by UID)\n```bash\nnewman run \"https:\u002F\u002Fapi.getpostman.com\u002Fcollections\u002F\u003CUID>?apikey={{POSTMAN_API_KEY}}\" \\\n  --environment environment.json \\\n  --reporters cli,junit \\\n  --reporter-junit-export results\u002Fjunit.xml\n```\n\n### Data-driven run (CSV)\n```bash\nnewman run collection.json \\\n  --iteration-data test-data.csv \\\n  --iteration-count 5 \\\n  --reporters cli,htmlextra \\\n  --reporter-htmlextra-export reports\u002Fdata-driven-report.html\n```\n\n### With environment variable overrides (no file needed)\n```bash\nnewman run collection.json \\\n  --env-var \"base_url=https:\u002F\u002Fstaging.api.example.com\" \\\n  --env-var \"token=abc123\" \\\n  --reporters cli\n```\n\n---\n\n## Step 3 — Shell Script\n\nGenerate a reusable shell script:\n\n```bash\n#!\u002Fbin\u002Fbash\nset -e\n\n# Configuration\nCOLLECTION=\".\u002Fcollection.json\"\nENVIRONMENT=\".\u002Fenvironment.json\"\nREPORT_DIR=\".\u002Freports\"\nTIMESTAMP=$(date +\"%Y%m%d_%H%M%S\")\n\n# Ensure report directory exists\nmkdir -p \"$REPORT_DIR\"\n\necho \"Running Newman collection: $COLLECTION\"\n\nnewman run \"$COLLECTION\" \\\n  --environment \"$ENVIRONMENT\" \\\n  --reporters cli,htmlextra,junit \\\n  --reporter-htmlextra-export \"$REPORT_DIR\u002Freport_$TIMESTAMP.html\" \\\n  --reporter-junit-export \"$REPORT_DIR\u002Fjunit_$TIMESTAMP.xml\" \\\n  --timeout-request 10000 \\\n  --bail\n\nEXIT_CODE=$?\n\nif [ $EXIT_CODE -eq 0 ]; then\n  echo \"✅ All tests passed.\"\nelse\n  echo \"❌ Tests failed. Check report: $REPORT_DIR\u002Freport_$TIMESTAMP.html\"\n  exit $EXIT_CODE\nfi\n```\n\n---\n\n## Step 4 — Jenkins Pipeline\n\n### Declarative Jenkinsfile (preferred)\n\n```groovy\npipeline {\n  agent any\n\n  environment {\n    POSTMAN_ENV = credentials('postman-environment-file') \u002F\u002F Jenkins credential ID\n  }\n\n  stages {\n    stage('Install Newman') {\n      steps {\n        sh 'npm install -g newman newman-reporter-htmlextra'\n      }\n    }\n\n    stage('Run API Tests') {\n      steps {\n        sh \"\"\"\n          newman run collection.json \\\\\n            --environment ${POSTMAN_ENV} \\\\\n            --reporters cli,htmlextra,junit \\\\\n            --reporter-htmlextra-export reports\u002Freport.html \\\\\n            --reporter-junit-export reports\u002Fjunit.xml \\\\\n            --timeout-request 10000 \\\\\n            --bail\n        \"\"\"\n      }\n    }\n  }\n\n  post {\n    always {\n      \u002F\u002F Archive HTML report\n      publishHTML(target: [\n        allowMissing: false,\n        alwaysLinkToLastBuild: true,\n        keepAll: true,\n        reportDir: 'reports',\n        reportFiles: 'report.html',\n        reportName: 'Newman API Test Report'\n      ])\n      \u002F\u002F Archive JUnit results\n      junit 'reports\u002Fjunit.xml'\n    }\n    failure {\n      echo 'API tests failed! Check the Newman report.'\n    }\n  }\n}\n```\n\n### Scripted Jenkinsfile (if declarative not available)\n\n```groovy\nnode {\n  stage('Install Newman') {\n    sh 'npm install -g newman newman-reporter-htmlextra'\n  }\n\n  stage('Run API Tests') {\n    try {\n      sh \"\"\"\n        newman run collection.json \\\\\n          --environment environment.json \\\\\n          --reporters cli,junit \\\\\n          --reporter-junit-export reports\u002Fjunit.xml \\\\\n          --bail\n      \"\"\"\n    } catch (err) {\n      currentBuild.result = 'FAILURE'\n      throw err\n    } finally {\n      junit 'reports\u002Fjunit.xml'\n    }\n  }\n}\n```\n\n### Jenkins with environment variables (no credentials file)\n```groovy\nenvironment {\n  BASE_URL = 'https:\u002F\u002Fapi.example.com'\n  API_TOKEN = credentials('api-token-secret')\n}\n\nsteps {\n  sh \"\"\"\n    newman run collection.json \\\\\n      --env-var \"base_url=${BASE_URL}\" \\\\\n      --env-var \"token=${API_TOKEN}\" \\\\\n      --reporters cli,junit \\\\\n      --reporter-junit-export results\u002Fjunit.xml\n  \"\"\"\n}\n```\n\n---\n\n## Step 5 — Reporter Reference\n\n| Reporter | Install | Flag | Output |\n|---|---|---|---|\n| `cli` | built-in | `--reporters cli` | Terminal output |\n| `junit` | built-in | `--reporters junit` | JUnit XML (for Jenkins) |\n| `htmlextra` | `npm i -g newman-reporter-htmlextra` | `--reporters htmlextra` | Rich HTML report |\n| `json` | built-in | `--reporters json` | Raw JSON results |\n\nMultiple reporters: `--reporters cli,htmlextra,junit`\n\n---\n\n## Step 6 — Output\n\nProvide based on what the user needs:\n\n1. **Newman command** — ready to paste in terminal\n2. **Shell script** (`run-tests.sh`) — with exit code handling\n3. **Jenkinsfile** — declarative or scripted based on context\n4. **Setup notes** — Node.js version requirement (≥14), npm install commands\n5. **Report locations** — where output files will be written\n\n---\n\n## Common Flags Quick Reference\n\n| Flag | Purpose |\n|---|---|\n| `--bail` | Stop run on first test failure |\n| `--timeout-request 5000` | Per-request timeout in ms |\n| `--delay-request 200` | Delay between requests in ms |\n| `--iteration-count 3` | Run collection N times |\n| `--folder \"Folder Name\"` | Run only a specific folder |\n| `--env-var \"k=v\"` | Inline environment variable |\n| `--suppress-exit-code` | Always exit 0 (don't fail CI) |\n| `--verbose` | Show full request\u002Fresponse details |\n| `--color off` | Disable color (useful for logs) |\n\n---\n\n## After Completing the Newman Commands\n\nOnce the CLI command output is delivered, ask the user:\n\n\"Would you like me to generate API documentation for this design? (yes\u002Fno)\"\n\nIf the user says **yes**:\n- Check if the API Documentation skill is available in the installed skills list\n- If the skill **is available**:\n  - Read and follow the instructions in the API Documentation skill\n  - Use the API design output above as the input\n  - Deliver the documentation as plain text output\n- If the skill **is NOT available**:\n  - Inform the user: \"It looks like the API Documentation skill isn't installed.\n    You can install it and re-run.\n\nIf the user says **no**:\n- End the task here\n\n---\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n","# Postman Newman Automation\n## When to Use\n\nUse this skill when you need generate Newman CLI commands, configuration files, Jenkins pipeline scripts, and shell automation for running Postman collections in CI\u002FCD or local environments. Use this skill whenever the user wants to run Postman collections from the command line, automate API tests, integrate...\n\n\nGenerates **Newman CLI** commands, **shell scripts**, and **Jenkins pipeline** configs\nfor running Postman collections in automated environments.\n\n---\n\n## Newman Basics\n\nNewman is Postman's CLI runner. Install with:\n```bash\nnpm install -g newman\n# Optional HTML reporter:\nnpm install -g newman-reporter-htmlextra\n```\n\n### Core Command Structure\n```bash\nnewman run \u003Ccollection> \\\n  --environment \u003Cenv-file> \\\n  --globals \u003Cglobals-file> \\\n  --iteration-count \u003Cn> \\\n  --iteration-data \u003Ccsv-or-json> \\\n  --reporters \u003Creporter-list> \\\n  --reporter-htmlextra-export \u003Coutput.html> \\\n  --reporter-junit-export \u003Cresults.xml> \\\n  --timeout-request \u003Cms> \\\n  --delay-request \u003Cms> \\\n  --bail \\\n  --color on\n```\n\n---\n\n## Step 1 — Gather Requirements\n\nAsk or infer from context:\n\n| Parameter | Question |\n|---|---|\n| Collection source | File path, URL, or Postman API UID? |\n| Environment | File path or inline variables? |\n| Reporter(s) | CLI only, HTML report, JUnit XML? |\n| Fail behavior | Stop on first failure (`--bail`) or run all? |\n| Iterations | Single run or data-driven (CSV\u002FJSON)? |\n| Target | Local shell, Jenkins, or both? |\n\n---\n\n## Step 2 — Generate Newman Command\n\n### Basic run (local)\n```bash\nnewman run collection.json \\\n  --environment environment.json \\\n  --reporters cli,htmlextra \\\n  --reporter-htmlextra-export reports\u002Freport.html \\\n  --bail\n```\n\n### Run from Postman API (by UID)\n```bash\nnewman run \"https:\u002F\u002Fapi.getpostman.com\u002Fcollections\u002F\u003CUID>?apikey={{POSTMAN_API_KEY}}\" \\\n  --environment environment.json \\\n  --reporters cli,junit \\\n  --reporter-junit-export results\u002Fjunit.xml\n```\n\n### Data-driven run (CSV)\n```bash\nnewman run collection.json \\\n  --iteration-data test-data.csv \\\n  --iteration-count 5 \\\n  --reporters cli,htmlextra \\\n  --reporter-htmlextra-export reports\u002Fdata-driven-report.html\n```\n\n### With environment variable overrides (no file needed)\n```bash\nnewman run collection.json \\\n  --env-var \"base_url=https:\u002F\u002Fstaging.api.example.com\" \\\n  --env-var \"token=abc123\" \\\n  --reporters cli\n```\n\n---\n\n## Step 3 — Shell Script\n\nGenerate a reusable shell script:\n\n```bash\n#!\u002Fbin\u002Fbash\nset -e\n\n# Configuration\nCOLLECTION=\".\u002Fcollection.json\"\nENVIRONMENT=\".\u002Fenvironment.json\"\nREPORT_DIR=\".\u002Freports\"\nTIMESTAMP=$(date +\"%Y%m%d_%H%M%S\")\n\n# Ensure report directory exists\nmkdir -p \"$REPORT_DIR\"\n\necho \"Running Newman collection: $COLLECTION\"\n\nnewman run \"$COLLECTION\" \\\n  --environment \"$ENVIRONMENT\" \\\n  --reporters cli,htmlextra,junit \\\n  --reporter-htmlextra-export \"$REPORT_DIR\u002Freport_$TIMESTAMP.html\" \\\n  --reporter-junit-export \"$REPORT_DIR\u002Fjunit_$TIMESTAMP.xml\" \\\n  --timeout-request 10000 \\\n  --bail\n\nEXIT_CODE=$?\n\nif [ $EXIT_CODE -eq 0 ]; then\n  echo \"✅ All tests passed.\"\nelse\n  echo \"❌ Tests failed. Check report: $REPORT_DIR\u002Freport_$TIMESTAMP.html\"\n  exit $EXIT_CODE\nfi\n```\n\n---\n\n## Step 4 — Jenkins Pipeline\n\n### Declarative Jenkinsfile (preferred)\n\n```groovy\npipeline {\n  agent any\n\n  environment {\n    POSTMAN_ENV = credentials('postman-environment-file') \u002F\u002F Jenkins credential ID\n  }\n\n  stages {\n    stage('Install Newman') {\n      steps {\n        sh 'npm install -g newman newman-reporter-htmlextra'\n      }\n    }\n\n    stage('Run API Tests') {\n      steps {\n        sh \"\"\"\n          newman run collection.json \\\\\n            --environment ${POSTMAN_ENV} \\\\\n            --reporters cli,htmlextra,junit \\\\\n            --reporter-htmlextra-export reports\u002Freport.html \\\\\n            --reporter-junit-export reports\u002Fjunit.xml \\\\\n            --timeout-request 10000 \\\\\n            --bail\n        \"\"\"\n      }\n    }\n  }\n\n  post {\n    always {\n      \u002F\u002F Archive HTML report\n      publishHTML(target: [\n        allowMissing: false,\n        alwaysLinkToLastBuild: true,\n        keepAll: true,\n        reportDir: 'reports',\n        reportFiles: 'report.html',\n        reportName: 'Newman API Test Report'\n      ])\n      \u002F\u002F Archive JUnit results\n      junit 'reports\u002Fjunit.xml'\n    }\n    failure {\n      echo 'API tests failed! Check the Newman report.'\n    }\n  }\n}\n```\n\n### Scripted Jenkinsfile (if declarative not available)\n\n```groovy\nnode {\n  stage('Install Newman') {\n    sh 'npm install -g newman newman-reporter-htmlextra'\n  }\n\n  stage('Run API Tests') {\n    try {\n      sh \"\"\"\n        newman run collection.json \\\\\n          --environment environment.json \\\\\n          --reporters cli,junit \\\\\n          --reporter-junit-export reports\u002Fjunit.xml \\\\\n          --bail\n      \"\"\"\n    } catch (err) {\n      currentBuild.result = 'FAILURE'\n      throw err\n    } finally {\n      junit 'reports\u002Fjunit.xml'\n    }\n  }\n}\n```\n\n### Jenkins with environment variables (no credentials file)\n```groovy\nenvironment {\n  BASE_URL = 'https:\u002F\u002Fapi.example.com'\n  API_TOKEN = credentials('api-token-secret')\n}\n\nsteps {\n  sh \"\"\"\n    newman run collection.json \\\\\n      --env-var \"base_url=${BASE_URL}\" \\\\\n      --env-var \"token=${API_TOKEN}\" \\\\\n      --reporters cli,junit \\\\\n      --reporter-junit-export results\u002Fjunit.xml\n  \"\"\"\n}\n```\n\n---\n\n## Step 5 — Reporter Reference\n\n| Reporter | Install | Flag | Output |\n|---|---|---|---|\n| `cli` | built-in | `--reporters cli` | Terminal output |\n| `junit` | built-in | `--reporters junit` | JUnit XML (for Jenkins) |\n| `htmlextra` | `npm i -g newman-reporter-htmlextra` | `--reporters htmlextra` | Rich HTML report |\n| `json` | built-in | `--reporters json` | Raw JSON results |\n\nMultiple reporters: `--reporters cli,htmlextra,junit`\n\n---\n\n## Step 6 — Output\n\nProvide based on what the user needs:\n\n1. **Newman command** — ready to paste in terminal\n2. **Shell script** (`run-tests.sh`) — with exit code handling\n3. **Jenkinsfile** — declarative or scripted based on context\n4. **Setup notes** — Node.js version requirement (≥14), npm install commands\n5. **Report locations** — where output files will be written\n\n---\n\n## Common Flags Quick Reference\n\n| Flag | Purpose |\n|---|---|\n| `--bail` | Stop run on first test failure |\n| `--timeout-request 5000` | Per-request timeout in ms |\n| `--delay-request 200` | Delay between requests in ms |\n| `--iteration-count 3` | Run collection N times |\n| `--folder \"Folder Name\"` | Run only a specific folder |\n| `--env-var \"k=v\"` | Inline environment variable |\n| `--suppress-exit-code` | Always exit 0 (don't fail CI) |\n| `--verbose` | Show full request\u002Fresponse details |\n| `--color off` | Disable color (useful for logs) |\n\n---\n\n## After Completing the Newman Commands\n\nOnce the CLI command output is delivered, ask the user:\n\n\"Would you like me to generate API documentation for this design? (yes\u002Fno)\"\n\nIf the user says **yes**:\n- Check if the API Documentation skill is available in the installed skills list\n- If the skill **is available**:\n  - Read and follow the instructions in the API Documentation skill\n  - Use the API design output above as the input\n  - Deliver the documentation as plain text output\n- If the skill **is NOT available**:\n  - Inform the user: \"It looks like the API Documentation skill isn't installed.\n    You can install it and re-run.\n\nIf the user says **no**:\n- End the task here\n\n---\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n",{"name":5,"risk":24,"source":25,"license":15,"date_added":26,"description":7,"source_repo":27,"source_type":28,"license_source":29},"unknown","https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Ftree\u002Fmain\u002Fapi-skill\u002Fpostman\u002Fpostman-to-newman",1782864000000,"LambdaTest\u002Fagent-skills","community","https:\u002F\u002Fgithub.com\u002FLambdaTest\u002Fagent-skills\u002Fblob\u002Fmain\u002FLICENSE","main","b1e4ffadb4f933bbbcaa03a83f8b9929171ac28b",".agents\u002Fskills\u002Fpostman-newman-automation",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":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill postman-newman-automation",{"tool":43,"command":44},"bunx","bunx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill postman-newman-automation",{"tool":46,"command":47},"pnpm","pnpm dlx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill postman-newman-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpostman-newman-automation\u002FSKILL.md",true,[],[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"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":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"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":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"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":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"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":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"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",[],[]]