[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D371KTYERB0DFG67XE9PTC":3,"skill-same:01M7D371KTYERB0DFG67XE9PTC":54},{"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":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7D371KTYERB0DFG67XE9PTC","redash",null,"Query a Redash instance over its REST API , list data sources and saved queries, read a saved query's SQL, run it, or run ad-hoc read-only SQL and get the rows back. Use when the user asks about Redash, a Redash query\u002Fdashboard\u002Flink, \"run that query\", \"what does query 1234 return\", or wants numbers out of an analytics data source rather than the application DB.","rabihkodeih\u002Fagentic-workflow","rabihkodeih","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1883033?v=4","01M7D357MHZJG4N8PQV8R5TZ82","Rabih Kodeih","01M7D357NM3WD86XTZ93FV7DNK",0,"MIT","https:\u002F\u002Fgithub.com\u002Frabihkodeih\u002Fagentic-workflow\u002Fblob\u002Fmain\u002Fskills\u002Fredash\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: redash\ndescription: Query a Redash instance over its REST API , list data sources and saved queries, read a saved query's SQL, run it, or run ad-hoc read-only SQL and get the rows back. Use when the user asks about Redash, a Redash query\u002Fdashboard\u002Flink, \"run that query\", \"what does query 1234 return\", or wants numbers out of an analytics data source rather than the application DB.\n---\n\n# Redash, query over the API\n\n`scripts\u002Fredash.py` talks to the Redash REST API with a user API key. Python stdlib\nonly, no venv, no pip.\n\n```bash\nscripts\u002Fredash.py whoami                      # verify the key works\nscripts\u002Fredash.py datasources                 # -> ids you need for `query`\nscripts\u002Fredash.py queries \"lead routing\"      # search saved queries\nscripts\u002Fredash.py get 1234                    # show that query's SQL + parameters\nscripts\u002Fredash.py run 1234 --param dealer_id=42\nscripts\u002Fredash.py query 'SELECT count(*) FROM leads' -d 3\nscripts\u002Fredash.py query - -d 3 \u003C \u002Ftmp\u002Fbig.sql\nscripts\u002Fredash.py dashboard my-dashboard-slug # widget -> query id map\nscripts\u002Fredash.py raw \u002Fapi\u002Fusers              # any endpoint not wrapped above\n```\n\nShared flags on `run`\u002F`query`: `--format table|json|csv` (default `table`) ·\n`--limit N` printed rows (default 200) · `--width N` column truncation (default 48) ·\n`--timeout S` how long to wait for the job (default 180) · `--max-age S` accept a\ncached result younger than S seconds (default 0 = always execute fresh) ·\n`--param key=value` (repeatable; values that parse as JSON are sent as JSON).\n\n## Setup, one time, key never enters the transcript\n\nSet `REDASH_URL` to the instance's base URL (env, or `~\u002F.config\u002Fredash\u002Furl`). The user\ngets the key from `\u003CREDASH_URL>\u002Fusers\u002Fme` (Account → API Key) and stores it themselves:\n\n```bash\nsecurity add-generic-password -a \"$USER\" -s redash-api-key -w\n```\n\n(paste at the prompt, press enter). Resolution order is `$REDASH_API_KEY` → that\nkeychain item → `~\u002F.config\u002Fredash\u002Fapi.key`. **Never ask the user to paste the\nkey into chat, and never echo it.**\n\n## Data sources\n\nRun `datasources` once per session and keep the ids you use in the project's\n`domain-knowledge.md`, dated. Ids differ per instance and drift over time.\n\n## How it runs a query\n\nRedash executes asynchronously: the POST returns a job, and the script polls\n`\u002Fapi\u002Fjobs\u002F\u003Cid>` until status 3 (success), then fetches `\u002Fapi\u002Fquery_results\u002F\u003Cid>`. On\n`--timeout` it cancels the job rather than orphaning it. A saved query with\nparameters will fail server-side if a required `--param` is missing , run `get` first\nto see the parameter names.\n\n## Prefer a saved query over hand-written SQL\n\nSomeone has usually already written it. `queries \u003Csearch>` then `get \u003Cid>` is cheaper\nand less wrong than inventing SQL against a schema you have not read. When you do go\nad-hoc, `schema \u003Cdata_source_id> --grep \u003Cfragment>` first , guessing table names\nagainst an analytics warehouse wastes a round trip each time.\n\n## Read-only by default\n\n`query` refuses anything that isn't `SELECT` \u002F `WITH` \u002F `SHOW` \u002F `DESCRIBE` \u002F\n`EXPLAIN`, rejects `INTO OUTFILE`\u002F`DUMPFILE`, and allows one statement per call.\nString literals and comments are blanked before the check, so a `;` or a keyword\ninside quotes can't slip past. `--unsafe` skips the guard, only with an explicit\ninstruction from the user, since a Redash data source may well be pointed at a\nwritable production database.\n\nThe guard is covered offline (no key, no network): `python3 scripts\u002Ftest_guard.py`.\n\nVolume matters more than write risk day to day: `--limit` only trims what is\n*printed*, the warehouse still computes the full result. Put the `LIMIT` in the SQL\nfor exploratory work.\n\n## Failure modes\n\n| Symptom | Meaning |\n| --- | --- |\n| `NO API KEY` | Nothing in env\u002Fkeychain\u002Fkeyfile; do the Setup step above |\n| `AUTH: ... 403 ... error_code 1010 browser_signature_banned` | **Not** a key problem: Cloudflare in front of the host bans the default `Python-urllib` User-Agent before the key is read. The script already sends a browser UA; if Cloudflare tightens again, override with `$REDASH_USER_AGENT` |\n| `AUTH: Redash returned 401\u002F403` (no `cloudflare_error`) | Key revoked, or the user's Redash groups don't grant that data source\u002Fquery |\n| `Non-JSON reply` | An SSO\u002Fproxy login page came back instead of the API , the user needs to re-auth in the browser |\n| `QUERY FAILED: ...` | The data source rejected the SQL; the message is verbatim from the DB |\n| `TIMEOUT: ...` | Job cancelled after `--timeout`; narrow the query before raising it |\n","# Redash, query over the API\n\n`scripts\u002Fredash.py` talks to the Redash REST API with a user API key. Python stdlib\nonly, no venv, no pip.\n\n```bash\nscripts\u002Fredash.py whoami                      # verify the key works\nscripts\u002Fredash.py datasources                 # -> ids you need for `query`\nscripts\u002Fredash.py queries \"lead routing\"      # search saved queries\nscripts\u002Fredash.py get 1234                    # show that query's SQL + parameters\nscripts\u002Fredash.py run 1234 --param dealer_id=42\nscripts\u002Fredash.py query 'SELECT count(*) FROM leads' -d 3\nscripts\u002Fredash.py query - -d 3 \u003C \u002Ftmp\u002Fbig.sql\nscripts\u002Fredash.py dashboard my-dashboard-slug # widget -> query id map\nscripts\u002Fredash.py raw \u002Fapi\u002Fusers              # any endpoint not wrapped above\n```\n\nShared flags on `run`\u002F`query`: `--format table|json|csv` (default `table`) ·\n`--limit N` printed rows (default 200) · `--width N` column truncation (default 48) ·\n`--timeout S` how long to wait for the job (default 180) · `--max-age S` accept a\ncached result younger than S seconds (default 0 = always execute fresh) ·\n`--param key=value` (repeatable; values that parse as JSON are sent as JSON).\n\n## Setup, one time, key never enters the transcript\n\nSet `REDASH_URL` to the instance's base URL (env, or `~\u002F.config\u002Fredash\u002Furl`). The user\ngets the key from `\u003CREDASH_URL>\u002Fusers\u002Fme` (Account → API Key) and stores it themselves:\n\n```bash\nsecurity add-generic-password -a \"$USER\" -s redash-api-key -w\n```\n\n(paste at the prompt, press enter). Resolution order is `$REDASH_API_KEY` → that\nkeychain item → `~\u002F.config\u002Fredash\u002Fapi.key`. **Never ask the user to paste the\nkey into chat, and never echo it.**\n\n## Data sources\n\nRun `datasources` once per session and keep the ids you use in the project's\n`domain-knowledge.md`, dated. Ids differ per instance and drift over time.\n\n## How it runs a query\n\nRedash executes asynchronously: the POST returns a job, and the script polls\n`\u002Fapi\u002Fjobs\u002F\u003Cid>` until status 3 (success), then fetches `\u002Fapi\u002Fquery_results\u002F\u003Cid>`. On\n`--timeout` it cancels the job rather than orphaning it. A saved query with\nparameters will fail server-side if a required `--param` is missing , run `get` first\nto see the parameter names.\n\n## Prefer a saved query over hand-written SQL\n\nSomeone has usually already written it. `queries \u003Csearch>` then `get \u003Cid>` is cheaper\nand less wrong than inventing SQL against a schema you have not read. When you do go\nad-hoc, `schema \u003Cdata_source_id> --grep \u003Cfragment>` first , guessing table names\nagainst an analytics warehouse wastes a round trip each time.\n\n## Read-only by default\n\n`query` refuses anything that isn't `SELECT` \u002F `WITH` \u002F `SHOW` \u002F `DESCRIBE` \u002F\n`EXPLAIN`, rejects `INTO OUTFILE`\u002F`DUMPFILE`, and allows one statement per call.\nString literals and comments are blanked before the check, so a `;` or a keyword\ninside quotes can't slip past. `--unsafe` skips the guard, only with an explicit\ninstruction from the user, since a Redash data source may well be pointed at a\nwritable production database.\n\nThe guard is covered offline (no key, no network): `python3 scripts\u002Ftest_guard.py`.\n\nVolume matters more than write risk day to day: `--limit` only trims what is\n*printed*, the warehouse still computes the full result. Put the `LIMIT` in the SQL\nfor exploratory work.\n\n## Failure modes\n\n| Symptom | Meaning |\n| --- | --- |\n| `NO API KEY` | Nothing in env\u002Fkeychain\u002Fkeyfile; do the Setup step above |\n| `AUTH: ... 403 ... error_code 1010 browser_signature_banned` | **Not** a key problem: Cloudflare in front of the host bans the default `Python-urllib` User-Agent before the key is read. The script already sends a browser UA; if Cloudflare tightens again, override with `$REDASH_USER_AGENT` |\n| `AUTH: Redash returned 401\u002F403` (no `cloudflare_error`) | Key revoked, or the user's Redash groups don't grant that data source\u002Fquery |\n| `Non-JSON reply` | An SSO\u002Fproxy login page came back instead of the API , the user needs to re-auth in the browser |\n| `QUERY FAILED: ...` | The data source rejected the SQL; the message is verbatim from the DB |\n| `TIMEOUT: ...` | Job cancelled after `--timeout`; narrow the query before raising it |\n",{"name":5,"description":7},"main","7b05d4ac96431d4dca2179b70d4f124979d4c3a8","skills\u002Fredash","https:\u002F\u002Fgithub.com\u002Frabihkodeih\u002Fagentic-workflow","https:\u002F\u002Fgithub.com\u002Frabihkodeih","2026-09-20 04:17:12",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add rabihkodeih\u002Fagentic-workflow --skill redash",{"tool":36,"command":37},"bunx","bunx skills add rabihkodeih\u002Fagentic-workflow --skill redash",{"tool":39,"command":40},"pnpm","pnpm dlx skills add rabihkodeih\u002Fagentic-workflow --skill redash","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frabihkodeih\u002Fagentic-workflow\u002Fblob\u002Fmain\u002Fskills\u002Fredash\u002FSKILL.md",true,[44,50],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"scripts\u002Fredash.py","SCRIPT","脚本",17237,"https:\u002F\u002Fgithub.com\u002Frabihkodeih\u002Fagentic-workflow\u002Fblob\u002Fmain\u002Fskills\u002Fredash\u002Fscripts\u002Fredash.py",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"scripts\u002Ftest_guard.py",1297,"https:\u002F\u002Fgithub.com\u002Frabihkodeih\u002Fagentic-workflow\u002Fblob\u002Fmain\u002Fskills\u002Fredash\u002Fscripts\u002Ftest_guard.py",[55,62,69,76,82,88],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7D37HNRY0RGK352YT1SYQVH","yes-no","Answer the user's question with a yes or no, optionally followed by a short explanation when the model sees fit. Use when the user types \"\u002Fyes-no\", asks a yes\u002Fno question and wants a decisive answer, or says \"just yes or no\".","https:\u002F\u002Fgithub.com\u002Frabihkodeih\u002Fagentic-workflow\u002Fblob\u002Fmain\u002Fskills\u002Fyes-no\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7D37CDX8K153CYY4FVCGAT5","sonar-workflow","Fix SonarQube code quality issues for a pull request. Auto-fixes trivial issues (formatting, unused imports) and requests approval for complex issues (security, bugs). Integrates with commit-workflow and pr-workflow skills.","https:\u002F\u002Fgithub.com\u002Frabihkodeih\u002Fagentic-workflow\u002Fblob\u002Fmain\u002Fskills\u002Fsonar-workflow\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},"01M7D377REEE0MBH7SJ37JWR41","short-answer","Answer the user's question as concisely as possible, a direct, to-the-point response with no preamble, filler, or unnecessary elaboration. Use when the user types \"\u002Fshort-answer\", asks for a brief\u002Fshort\u002Fconcise\u002FTL;DR answer, or says \"just the answer\".","https:\u002F\u002Fgithub.com\u002Frabihkodeih\u002Fagentic-workflow\u002Fblob\u002Fmain\u002Fskills\u002Fshort-answer\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7D36Y5BF600Z6B470W1AFNZ","prod-db-postgres","https:\u002F\u002Fgithub.com\u002Frabihkodeih\u002Fagentic-workflow\u002Fblob\u002Fmain\u002Fskills\u002Fprod-db-postgres\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7D36VE5AEREF874PDV2SJSG","prod-db-mysql-bastion","https:\u002F\u002Fgithub.com\u002Frabihkodeih\u002Fagentic-workflow\u002Fblob\u002Fmain\u002Fskills\u002Fprod-db-mysql-bastion\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7D36NSNPJVP3BS20DRMZ953","pr-workflow","Use this skill when asked to create or update a pull request (PR). It ensures all PRs follow the repository's established templates and standards. Handles both new PR creation and updating existing PRs with new commits, title changes, or description updates.","https:\u002F\u002Fgithub.com\u002Frabihkodeih\u002Fagentic-workflow\u002Fblob\u002Fmain\u002Fskills\u002Fpr-workflow\u002FSKILL.md",[],[]]