القائمة
Edit and improve articles by restructuring sections, improving clarity, and tightening prose. Use when user wants to edit, revise, or improve an article draft.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Search and query Grafana metrics (metrics.qlikcloud.io) to investigate a ticket - find the relevant dashboard, read its PromQL, run and adjust queries, and correlate with splunk/k8s. Backed by the metrics MCP tools, which borrow the Brave session cookie and auto-open login when stale. Use when asked to look into metrics, dashboards, or PromQL for a problem or ticket.
Drive the Qlik Cloud (QCDI / Talend Data Integration) UI via browser-repl (nbb + Playwright over an nREPL) to validate a ticket or flow on US Stage or an SDE, while a backend watcher tails k8s (SDE) and Splunk for correlated signals. Use when asked to verify/validate/reproduce a ticket in the Qlik UI, exercise connections or data tasks end to end, or watch backend behavior during a UI flow.
Spawn a conditional stream watcher as an ECA background task so the LLM sees matches only. Use instead of repeated MCP polling whenever the user asks to watch, monitor, or be alerted to a condition on a cluster, log tail, or any long-running producer.
Drive a live browser from a ClojureScript REPL - nbb + Playwright behind an nREPL, evaluated through the nrepl MCP. The powerhouse for verifying/testing web products, scraping, auth automation, bulk downloads, and UI prototyping. Gives liveness (browser + atoms persist across evals), token economy (targeted extracts and scoped aria instead of multi-KB snapshots), live network/console capture for backend correlation, the full Playwright API, and fire-and-poll for long ops. Use when you need to interactively drive or inspect a real browser at low token cost, or correlate UI actions with backend signals. Use jxa-browser only for a quick peek at the user's already-open everyday browser.
Capture investigation findings from a ticket or task into a structured spec optimized for LLM consumption. Also use to check for existing specs when investigating bugs that might relate to past work.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
| name | edit-article |
| description | Edit and improve articles by restructuring sections, improving clarity, and tightening prose. Use when user wants to edit, revise, or improve an article draft. |
Consider that information is a directed acyclic graph, and that pieces of information can depend on other pieces of information. Make sure that the order of the sections and their contents respects these dependencies.
Confirm the sections with the user.
2a. Rewrite the section to improve clarity, coherence, and flow. Use maximum 240 characters per paragraph.
