[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"creator:01M785FRNZ3XKFVNJM93V4SCDF":3,"creator-list:01M785FRNZ3XKFVNJM93V4SCDF:stars:1:":17},{"accountNo":4,"login":5,"displayName":5,"avatarUrl":6,"accountType":7,"accountTypeDesc":8,"profileDescription":9,"skillCount":10,"repoCount":11,"professionCount":12,"scenarioCount":12,"totalStars":13,"updatedAt":14,"htmlUrl":15,"blogUrl":9,"company":9,"location":9,"followersCount":16,"publicReposCount":16},"01M785FRNZ3XKFVNJM93V4SCDF","MhmdElGazzar","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F77445441?v=4","USER","个人作者",null,17,1,0,21,"2026-10-26 20:41:29","https:\u002F\u002Fgithub.com\u002FMhmdElGazzar",38,{"records":18,"total":10,"current":11,"size":142},[19,30,37,44,51,58,65,72,79,86,93,100,107,114,121,128,135],{"skillNo":20,"name":21,"nameZh":9,"description":22,"descriptionZh":9,"repositoryFullName":23,"ownerLogin":5,"ownerAvatarUrl":6,"ownerAccountNo":4,"ownerDisplayName":9,"repositoryNo":24,"starsCount":13,"licenseSpdxId":25,"licenseFileUrl":9,"sourceHtmlUrl":26,"categories":27,"keywords":28,"publishedAt":29},"01M785KAQ1FVFKCD8T8X6AP7TN","ui-check","Execute ui-check: steps in test specs — compare the live page currently open in the browser under test against a declared design baseline: a Figma frame (identifier only; file + token configured once per project) or a screenshot image, in exact mode (every visible detail) or reference mode (only enumerated details can fail). Triggers on spec steps starting with \"ui-check:\", or requests like \"check this page against the design\", \"compare with the Figma frame\", \"does the screen match the mockup\". Baselines are resolved by the bundled fetch_baseline.js runner — an unresolvable baseline is BLOCKED, never improvised; the comparison verdict itself is agent-vision judgment.","MhmdElGazzar\u002Fagentex","01M785FRPXBRK2F92DRZQYNX4F","MIT","https:\u002F\u002Fgithub.com\u002FMhmdElGazzar\u002Fagentex\u002Fblob\u002Fmain\u002Fskills\u002Fui-check\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":31,"name":32,"nameZh":9,"description":33,"descriptionZh":9,"repositoryFullName":23,"ownerLogin":5,"ownerAvatarUrl":6,"ownerAccountNo":4,"ownerDisplayName":9,"repositoryNo":24,"starsCount":13,"licenseSpdxId":25,"licenseFileUrl":9,"sourceHtmlUrl":34,"categories":35,"keywords":36,"publishedAt":29},"01M785K3RZA0R7ZJ4SCWWYME44","tracker-ops","Ad-hoc work-item operations on the configured tracker — Azure DevOps or Jira Cloud — behind one approval per write batch. Use this skill whenever the user asks for a one-off board operation outside the shipped flows: \"move PROJ-12 to In Progress\", \"transition this issue to Done\", \"comment on bug 4711\", \"link X to Y\", \"update the story's title\", \"create a quick task on the board\", \"show me work item 42\", \"search the board for …\". Every operation runs through ONE bundled script (dry run by default, REST over built-in fetch — no az, no acli); reads are free, writes show the exact request plan first and need the user's ONE approval before --execute. Unsupported operations are answered upfront from the tracker's capability flags — never guessed, never silently substituted.","https:\u002F\u002Fgithub.com\u002FMhmdElGazzar\u002Fagentex\u002Fblob\u002Fmain\u002Fskills\u002Ftracker-ops\u002FSKILL.md",[],[],{"skillNo":38,"name":39,"nameZh":9,"description":40,"descriptionZh":9,"repositoryFullName":23,"ownerLogin":5,"ownerAvatarUrl":6,"ownerAccountNo":4,"ownerDisplayName":9,"repositoryNo":24,"starsCount":13,"licenseSpdxId":25,"licenseFileUrl":9,"sourceHtmlUrl":41,"categories":42,"keywords":43,"publishedAt":29},"01M785JZ62NEMGQKZPSY3405AK","test-execution","Run test specs against an application and report defects, routing each step to its driver (browser via playwright-cli, API calls, database checks, knowledge-base questions, UI design checks). Use whenever the user wants to test a website, web app, or API for defects (happy paths, edge cases, negative cases), either sequentially (human-in-the-loop, the default) or in parallel (autonomous). Produces per-scenario evidence plus a consolidated defect report. Read this before starting any test run.","https:\u002F\u002Fgithub.com\u002FMhmdElGazzar\u002Fagentex\u002Fblob\u002Fmain\u002Fskills\u002Ftest-execution\u002FSKILL.md",[],[],{"skillNo":45,"name":46,"nameZh":9,"description":47,"descriptionZh":9,"repositoryFullName":23,"ownerLogin":5,"ownerAvatarUrl":6,"ownerAccountNo":4,"ownerDisplayName":9,"repositoryNo":24,"starsCount":13,"licenseSpdxId":25,"licenseFileUrl":9,"sourceHtmlUrl":48,"categories":49,"keywords":50,"publishedAt":29},"01M785JNVC8THWZXXP0EMR55B9","test-design","Designs test cases for User Stories on the configured tracker — Azure DevOps or Jira Cloud: analyze a story's acceptance criteria into test conditions, map them to test case titles, create the test artifacts (ADO Test Cases with structured steps, or the Jira issue type the user chooses — Jira has no native Test Case type) and link them to the parent story, behind ONE consolidated approval. Use this skill whenever the user wants to: - Analyze a user story and identify test conditions - Map AC scenarios to test case titles using a naming convention - Create test cases in ADO with proper steps, or design test cases for a Jira story - Review whether a story's ACs are fully covered by test cases Trigger on phrases like: \"create test cases for story\", \"design tests for\", \"design test cases for a Jira story\", \"what test cases do I need\", \"analyze story for testing\", \"map ACs to test conditions\", or any time a user story ID or Jira issue key is mentioned alongside test design\u002Fcoverage work.","https:\u002F\u002Fgithub.com\u002FMhmdElGazzar\u002Fagentex\u002Fblob\u002Fmain\u002Fskills\u002Ftest-design\u002FSKILL.md",[],[],{"skillNo":52,"name":53,"nameZh":9,"description":54,"descriptionZh":9,"repositoryFullName":23,"ownerLogin":5,"ownerAvatarUrl":6,"ownerAccountNo":4,"ownerDisplayName":9,"repositoryNo":24,"starsCount":13,"licenseSpdxId":25,"licenseFileUrl":9,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":29},"01M785JBHDWEQRSEG0NAMQ58YQ","task-estimation","Creates QA testing tasks with estimation on the configured tracker's User Stories — Azure DevOps or Jira Cloud. Reads the sprint, analyzes each story, then creates all [Testing] tasks (ADO Tasks or Jira sub-tasks) behind ONE consolidated approval, through bundled REST scripts (no Azure CLI, no acli). Use this skill whenever the user wants to:\n- Add QA tasks to sprint stories in Azure DevOps or Jira\n- Estimate testing hours for user stories\n- Create [Testing] tasks on ADO work items or [Testing] sub-tasks on Jira issues\n- Plan QA effort for a sprint\n- Break down stories into testing tasks with hours\nTrigger on phrases like: \"create tasks for stories\", \"add QA tasks\", \"estimate sprint\", \"estimate the Jira sprint\", \"create testing tasks\", \"create tasks for Jira sprint stories\", \"add sub-tasks to Jira stories\", \"plan QA for sprint\", \"add tasks to stories\", or any mention of sprint stories + estimation + testing.","https:\u002F\u002Fgithub.com\u002FMhmdElGazzar\u002Fagentex\u002Fblob\u002Fmain\u002Fskills\u002Ftask-estimation\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":9,"description":61,"descriptionZh":9,"repositoryFullName":23,"ownerLogin":5,"ownerAvatarUrl":6,"ownerAccountNo":4,"ownerDisplayName":9,"repositoryNo":24,"starsCount":13,"licenseSpdxId":25,"licenseFileUrl":9,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":29},"01M785J43EZ145QP0R7DGJ4ZXG","swagger-import","Generate an API catalog + suite of test cases (integration\u002Fapi_test_suites\u002F\u003Cservice>\u002F) from a Swagger 2.0 or OpenAPI 3.x JSON document. Use for \u002Fimport-swagger, or requests like \"import this swagger doc\", \"generate endpoint tests from this OpenAPI spec\", or the guided wizard (\u002Fimport-swagger --wizard) that collects real test data and previews basic checks (happy path, not found, no token, missing field) before one approval. Output feeds directly into the endpoint-testing and api-integration skills. This skill generates config and sends no API request of its own; any run, including the wizard's \"Approve and run now\", goes through endpoint-testing's runner.","https:\u002F\u002Fgithub.com\u002FMhmdElGazzar\u002Fagentex\u002Fblob\u002Fmain\u002Fskills\u002Fswagger-import\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":9,"description":68,"descriptionZh":9,"repositoryFullName":23,"ownerLogin":5,"ownerAvatarUrl":6,"ownerAccountNo":4,"ownerDisplayName":9,"repositoryNo":24,"starsCount":13,"licenseSpdxId":25,"licenseFileUrl":9,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":29},"01M785HZT41130PBW95PAVYK4P","optimize-login","Pay a web application's login cost once per session instead of once per test — drive the login live, reduce it to the smallest script that works, save the browser session, and reload that session into a fresh browser to continue. Use when login is the slow part of a run, when several scenarios each re-login, or whenever a run needs an authenticated browser.","https:\u002F\u002Fgithub.com\u002FMhmdElGazzar\u002Fagentex\u002Fblob\u002Fmain\u002Fskills\u002Foptimize-login\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":9,"description":75,"descriptionZh":9,"repositoryFullName":23,"ownerLogin":5,"ownerAvatarUrl":6,"ownerAccountNo":4,"ownerDisplayName":9,"repositoryNo":24,"starsCount":13,"licenseSpdxId":25,"licenseFileUrl":9,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":29},"01M785HS3AK90KDNCHGG785MRV","mobile-testing","Test a native mobile app (Android\u002FiOS) by driving it through Appium. Use whenever the user wants to test a mobile app for defects — happy paths, edge cases, and negative cases — either sequentially (human-in-the-loop, the default) or in parallel (autonomous, one session per available device\u002Femulator). Produces per-scenario screenshots and logs plus a consolidated defect report. Read this before starting any mobile testing run.","https:\u002F\u002Fgithub.com\u002FMhmdElGazzar\u002Fagentex\u002Fblob\u002Fmain\u002Fskills\u002Fmobile-testing\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":9,"description":82,"descriptionZh":9,"repositoryFullName":23,"ownerLogin":5,"ownerAvatarUrl":6,"ownerAccountNo":4,"ownerDisplayName":9,"repositoryNo":24,"starsCount":13,"licenseSpdxId":25,"licenseFileUrl":9,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":29},"01M785HJVYPWJWZ6V6KEM423JN","extent-report","Produce a standalone, self-contained extent-report.html — a dark-themed interactive dashboard (verdict banner, donut chart, per-status stat cards, expandable test-case cards with step-by-step detail). Use at the end of any playwright-cli test execution (one test case or a full parallel\u002Fsequential batch) once final scenario results are known, alongside report.md.","https:\u002F\u002Fgithub.com\u002FMhmdElGazzar\u002Fagentex\u002Fblob\u002Fmain\u002Fskills\u002Fextent-report\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":9,"description":89,"descriptionZh":9,"repositoryFullName":23,"ownerLogin":5,"ownerAvatarUrl":6,"ownerAccountNo":4,"ownerDisplayName":9,"repositoryNo":24,"starsCount":13,"licenseSpdxId":25,"licenseFileUrl":9,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":29},"01M785H9FCG6GFGR56YD4FMKZA","endpoint-testing","Run a standalone API test pass over the project's cataloged endpoints (\"api-tests\"), independent of any browser test spec. Use for \u002Ftest-endpoints, or requests like \"run the API tests\", \"test all endpoints\". Also opens the local API suite editor (\u002Ftest-endpoints --edit) to review, fix and re-run cases, one suite or one case at a time. Use before editing any *_suite.json by hand, and whenever asked to enable, un-skip or remove \"skip\" lines from write cases (POST\u002FPUT\u002FPATCH\u002FDELETE). Distinct from api-integration's `api:` step (a single cataloged call made mid-browser-test) — this skill runs the whole set of cases in one pass and returns a consolidated report. Execution is catalog+suite-only: only cases defined in integration\u002Fapi_test_suites\u002F**\u002F*_suite.json, referencing entries defined in the sibling *_api.json catalog, ever run.","https:\u002F\u002Fgithub.com\u002FMhmdElGazzar\u002Fagentex\u002Fblob\u002Fmain\u002Fskills\u002Fendpoint-testing\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":9,"description":96,"descriptionZh":9,"repositoryFullName":23,"ownerLogin":5,"ownerAvatarUrl":6,"ownerAccountNo":4,"ownerDisplayName":9,"repositoryNo":24,"starsCount":13,"licenseSpdxId":25,"licenseFileUrl":9,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":29},"01M785H3JPSQHAMMR86ZHA5ENX","define-flow","Define a test flow by doing it: an agent-led session that builds a spec step by step in a live browser — the agent proposes each step, executes it immediately, and the user asserts the real outcome before the next step is defined. Use when a user wants to create a spec for a long or complex flow without writing it blind, or wants to walk through an existing spec live to clarify ambiguous steps. Produces a normal natural-language spec file that runs unmodified via \u002Fexecute-test.","https:\u002F\u002Fgithub.com\u002FMhmdElGazzar\u002Fagentex\u002Fblob\u002Fmain\u002Fskills\u002Fdefine-flow\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":9,"description":103,"descriptionZh":9,"repositoryFullName":23,"ownerLogin":5,"ownerAvatarUrl":6,"ownerAccountNo":4,"ownerDisplayName":9,"repositoryNo":24,"starsCount":13,"licenseSpdxId":25,"licenseFileUrl":9,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":29},"01M785GWVZ164G93Q33ZNJWTWP","db-integration","Execute user-defined database queries during test runs, from the project's integration\u002F catalog (SQL Server via sqlcmd). Use whenever a test step needs a DB check: verify a row was created\u002Fupdated by a UI action, check column values, or seed test data. Triggers on spec steps starting with \"db:\", or requests like \"check the database\", \"verify the row\", \"query the table\". The agent executes ONLY queries the user has defined in integration\u002F*_db.json — it never composes its own SQL.","https:\u002F\u002Fgithub.com\u002FMhmdElGazzar\u002Fagentex\u002Fblob\u002Fmain\u002Fskills\u002Fdb-integration\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":9,"description":110,"descriptionZh":9,"repositoryFullName":23,"ownerLogin":5,"ownerAvatarUrl":6,"ownerAccountNo":4,"ownerDisplayName":9,"repositoryNo":24,"starsCount":13,"licenseSpdxId":25,"licenseFileUrl":9,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":29},"01M785GJV9XEC029E8KZM02FQE","bug-report-azure","After a completed test\u002Fregression run where one or more defects were found, file them as tracker Bugs on the configured tracker — Azure DevOps or Jira Cloud (\"file these as Jira bugs\" works the same) — following a configurable bug template, through bundled Node scripts that talk to the tracker REST API directly (no Azure CLI, no acli needed). Product\u002Fteam-agnostic: org\u002Fsite, project, area path, template, assignees, and test plan resolve from config, never hardcoded. ONE gate per filing: all reads and validation run first with zero board writes, then a single consolidated screen (validated fields + the exact write plan) and one approval before anything is written. Severity\u002Fpriority recommended from the run's findings, screenshots validated in two passes, writes fail closed with an exact per-write ledger — the board never silently differs from what the user confirmed.","https:\u002F\u002Fgithub.com\u002FMhmdElGazzar\u002Fagentex\u002Fblob\u002Fmain\u002Fskills\u002Fbug-report-azure\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":9,"description":117,"descriptionZh":9,"repositoryFullName":23,"ownerLogin":5,"ownerAvatarUrl":6,"ownerAccountNo":4,"ownerDisplayName":9,"repositoryNo":24,"starsCount":13,"licenseSpdxId":25,"licenseFileUrl":9,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":29},"01M785GCQYQ5Z2QA7XVFS3KWN4","browser-driver","The browser driver for test-execution runs. It drives a real browser through playwright-cli for unprefixed (prose) spec steps and covers isolated sessions, screenshot and console evidence, login modes, and the failure signatures that decide retry versus defect. Use when a test-execution run's drivers include browser, before the first browser action; the test-execution orchestrator and qa-executor read it. Not a standalone entry point.","https:\u002F\u002Fgithub.com\u002FMhmdElGazzar\u002Fagentex\u002Fblob\u002Fmain\u002Fskills\u002Fbrowser-driver\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":9,"description":124,"descriptionZh":9,"repositoryFullName":23,"ownerLogin":5,"ownerAvatarUrl":6,"ownerAccountNo":4,"ownerDisplayName":9,"repositoryNo":24,"starsCount":13,"licenseSpdxId":25,"licenseFileUrl":9,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":29},"01M785G7JMNKS9AB0FKN8WCBMY","azure-integration","Interact with Azure resources from a QA\u002Ftest run via the Azure CLI (`az`) — login\u002Fauth, discovery, and reading App Service, Storage, Key Vault, and AKS resources. Use whenever a task needs to reach Azure (verify a deployment, tail app logs, read a blob\u002Fsecret, get AKS credentials) or when `az` is not installed. Read the reference before the first `az` command.","https:\u002F\u002Fgithub.com\u002FMhmdElGazzar\u002Fagentex\u002Fblob\u002Fmain\u002Fskills\u002Fazure-integration\u002FSKILL.md",[],[],{"skillNo":129,"name":130,"nameZh":9,"description":131,"descriptionZh":9,"repositoryFullName":23,"ownerLogin":5,"ownerAvatarUrl":6,"ownerAccountNo":4,"ownerDisplayName":9,"repositoryNo":24,"starsCount":13,"licenseSpdxId":25,"licenseFileUrl":9,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":29},"01M785G371KT1ZK37SNNJA2KQ0","ask-kb","Ask a project's knowledge base a natural-language question during a test run, via the KB Ask API, and read the answer as advisory context. Triggers on spec steps starting with \"kb:\", or requests like \"ask the KB\", \"what does the knowledge base say\", \"how does \u003Cflow> work\". Explicit only — the agent never calls the KB on its own initiative. Answers inform testing\u002Fnavigation but are NEVER used as PASS\u002FFAIL evidence.","https:\u002F\u002Fgithub.com\u002FMhmdElGazzar\u002Fagentex\u002Fblob\u002Fmain\u002Fskills\u002Fask-kb\u002FSKILL.md",[],[],{"skillNo":136,"name":137,"nameZh":9,"description":138,"descriptionZh":9,"repositoryFullName":23,"ownerLogin":5,"ownerAvatarUrl":6,"ownerAccountNo":4,"ownerDisplayName":9,"repositoryNo":24,"starsCount":13,"licenseSpdxId":25,"licenseFileUrl":9,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":29},"01M785FX8M46MX1RDZH98N7C65","api-integration","Execute user-defined API calls during test runs, from the project's integration\u002F catalog. Use whenever a test step needs an HTTP call: verify via API that a UI action persisted, check an endpoint's response, or seed test data through a service. Triggers on spec steps starting with \"api:\", or requests like \"verify via API\", \"call the endpoint\", \"check the response\". The agent executes ONLY requests the user has defined in a *_api.json catalog (searched recursively under integration\u002F) — it never composes its own HTTP requests.","https:\u002F\u002Fgithub.com\u002FMhmdElGazzar\u002Fagentex\u002Fblob\u002Fmain\u002Fskills\u002Fapi-integration\u002FSKILL.md",[],[],18]