القائمة
Trigger native web search. Use when you need quick internet research with concise summaries and full source URLs.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | native-web-search |
| description | Trigger native web search. Use when you need quick internet research with concise summaries and full source URLs. |
Use this skill to run a fast model with native web search enabled and get a concise research summary with explicit full URLs.
search.mjsRun from this skill directory:
node search.mjs "<what to search>" --purpose "<why you need this>"
Examples:
node search.mjs "latest python release" --purpose "update dependency notes"
node search.mjs "vite 7 breaking changes" --purpose "prepare migration checklist"
Optional flags:
--provider openai-codex|anthropic--model <model-id>--timeout <ms>--jsonThe script instructs the model to:
https://...) for each key findingPI_AI_MODULE_PATH to @mariozechner/pi-ai's dist/index.js path.PI_AI_OAUTH_MODULE_PATH to @mariozechner/pi-ai's dist/oauth.js path.access token from ~/.pi/agent/auth.json.Top-level session orchestration rules — subagent routing, context hygiene, and implementation discipline. Not intended for subagents.
Wrike connector skill for managing Agile work items (Epics, Stories, Tasks, sub-tasks, comments, and attachments) via the Wrike REST API v4. Use this skill whenever an agent needs to read or write Wrike workspace data.
Post-merge integrity check skill for SugarCRM projects. Use whenever an agent needs to compare two branches after a version-upgrade merge, detect lost or damaged custom code (identified by CUSTOM_MARKERS), and generate git patches for CRITICAL/HIGH findings.
Browser automation skill for testing SugarCRM Enterprise (v12-25). Use for simulating user interactions: clicking buttons, filling forms, navigating modules, creating records, and verifying functionality. Requires Playwright and Chromium browser installed.
Interactive browser automation via Chrome DevTools Protocol. Use when you need to interact with web pages, test frontends, or when user interaction with a visible browser is required.
Delta integration for viewing diffs in the terminal. Use when showing file differences to the user with syntax highlighting via delta.