القائمة
Use when the user asks to browse, inspect, click, snapshot, or extract evidence from a web page.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/modiqo/skillspec --skill browser-research-proseيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Multiplex SkillSpec post-install setup: inspect skill/repo shape with doctor, map multi-skill and plugin-shaped repositories before fanout import, assess a skill or plugin's security boundary — what it could reach if executed, ranked by risk (critical/high/medium/low), with a clickable-evidence tree — and gate or install it safely before it lands on disk, import existing SKILL.md skills from local folders or public URIs, inspect installed status, install compiled workspaces with entry/support visibility planning, install/update/enable/disable router mode, optionally install/update/enable/disable/delete durable-executor, create specs from observed durable execution workspaces, revise SkillSpec YAML, and prove value before install or release. Use for skillspec, /skillspec, skillspec setup, post install setup, assess skill security, is this skill safe, what can this skill reach, scan a skill or plugin, security analysis of a skill, boundary check, gate a skill or plugin install, check a skill before installing,
A skill whose guidance shows example code. Use for testing documentation-example qualification.
Summarize a document using the house style.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | browser-research-prose |
| description | Use when the user asks to browse, inspect, click, snapshot, or extract evidence from a web page. |
Use this skill when the user asks you to browse a website, open a page, click through an interface, inspect page content, take a snapshot, extract evidence from a page, or verify what a page currently shows.
For browser tasks, use browser automation. Do not answer from native search when the user asked you to observe a page. Native search can be used only to discover the likely URL when the user did not provide one, and it must not be presented as page evidence.
If the user provides a URL, open that URL in the browser and inspect the page directly. If the user names a page but does not provide a URL, ask for the URL unless there is a clear, low-risk discovery path. If discovery is needed, search only long enough to identify the target URL, then switch to browser automation and verify the page itself.
Do not use curl, static HTML fetches, or search snippets as substitutes for browser evidence when the task depends on rendered page state, navigation, logged-in state, screenshots, dynamic content, or visible UI.
Before taking action, make sure a browser session is available and that network access is allowed. If a login, credential, or private workspace is needed, stop and ask before proceeding.
When the work is done, report what page was opened, what evidence was observed, which route was used, and any limitations. If there was URL discovery before browser inspection, say so clearly.
Good behavior examples:
This skill relies on the agent following the prose carefully. There is no separate validation command, scenario test, dependency preflight, or trace contract in this prose-only version.