opencode-skills-collection 4.1.14 → 4.1.16

package/bundled-skills/page-cro/SKILL.md

@@ -11,112 +11,13 @@ Your goal is to **diagnose why a page is or is not converting**, assess readines
 You do **not** guarantee conversion lifts.
 You do **not** recommend changes without explaining *why they matter*.
 ---
-## Phase 0: Page Conversion Readiness & Impact Index (Required)
+## Phase 0: Evidence and constraints
 
-Before giving CRO advice, calculate the **Page Conversion Readiness & Impact Index**.
-
-### Purpose
-
-This index answers:
-
-> **Is this page structurally capable of converting, and where are the biggest constraints?**
-
-It prevents:
-
-* cosmetic CRO
-* premature A/B testing
-* optimizing the wrong thing
-
----
-
-## 🔢 Page Conversion Readiness & Impact Index
-
-### Total Score: **0–100**
-
-This is a **diagnostic score**, not a success metric.
-
----
-
-### Scoring Categories & Weights
-
-| Category                    | Weight  |
-| --------------------------- | ------- |
-| Value Proposition Clarity   | 25      |
-| Conversion Goal Focus       | 20      |
-| Traffic–Message Match       | 15      |
-| Trust & Credibility Signals | 15      |
-| Friction & UX Barriers      | 15      |
-| Objection Handling          | 10      |
-| **Total**                   | **100** |
-
----
-
-### Category Definitions
-
-#### 1. Value Proposition Clarity (0–25)
-
-* Visitor understands what this is and why it matters in ≤5 seconds
-* Primary benefit is specific and differentiated
-* Language reflects user intent, not internal jargon
-
----
-
-#### 2. Conversion Goal Focus (0–20)
-
-* One clear primary conversion action
-* CTA hierarchy is intentional
-* Commitment level matches page stage
-
----
-
-#### 3. Traffic–Message Match (0–15)
-
-* Page aligns with visitor intent (organic, paid, email, referral)
-* Headline and hero match upstream messaging
-* No bait-and-switch dynamics
-
----
-
-#### 4. Trust & Credibility Signals (0–15)
-
-* Social proof exists and is relevant
-* Claims are substantiated
-* Risk is reduced at decision points
-
----
-
-#### 5. Friction & UX Barriers (0–15)
-
-* Page loads quickly and works on mobile
-* No unnecessary form fields or steps
-* Navigation and next steps are clear
-
----
-
-#### 6. Objection Handling (0–10)
-
-* Likely objections are anticipated
-* Page addresses “Will this work for me?”
-* Uncertainty is reduced, not ignored
-
----
-
-### Conversion Readiness Bands (Required)
-
-| Score  | Verdict                  | Interpretation                                 |
-| ------ | ------------------------ | ---------------------------------------------- |
-| 85–100 | **High Readiness**       | Page is structurally sound; test optimizations |
-| 70–84  | **Moderate Readiness**   | Fix key issues before testing                  |
-| 55–69  | **Low Readiness**        | Foundational problems limit conversions        |
-| <55    | **Not Conversion-Ready** | CRO will not work yet                          |
-
-If score < 70, **testing is not recommended**.
-
----
+Establish the page goal, audience, acquisition source, observed baseline and available data before diagnosis. Record missing evidence as unknown. Use value proposition, goal focus, message match, trust, friction and objection handling as qualitative prompts, not a calibrated 0–100 score. No invented threshold determines whether a page can convert or whether testing is allowed.
 
 ## Phase 1: Context & Goal Alignment
 
-(Proceed only after scoring)
+(Use confirmed context; ask only for missing inputs that affect the recommendation.)
 
 ### 1. Page Type
 
@@ -235,7 +136,7 @@ Analyze in **impact order**, not arbitrarily.
 
 All recommendations must map to:
 
-* a **scoring category**
+* a **diagnostic category**
 * a **conversion constraint**
 * a **measurable hypothesis**
 
@@ -245,8 +146,8 @@ All recommendations must map to:
 
 ### Conversion Readiness Summary
 
-* Overall Score: XX / 100
-* Verdict: High / Moderate / Low / Not Ready
+* Observed baseline and evidence gaps
+* Constraint, supporting observation and confidence
 * Key limiting factors
 
 ---
@@ -308,10 +209,9 @@ Each with rationale tied to user intent.
 
 ## Experiment Guardrails
 
-Do **not** recommend A/B testing when:
+Choose experimentation based on sample size, detectable effect, duration and guardrail metrics. Resolve these gaps before committing to a test:
 
 * Traffic is too low
-* Page score < 70
 * Value proposition is unclear
 * Conversion goal is ambiguous
 
@@ -337,10 +237,14 @@ Fix fundamentals first.
 * **copywriting** – If messaging needs a full rewrite
 * **ab-test-setup** – For test execution and instrumentation
 
-```
-
 ## When to Use
-This skill is applicable to execute the workflow or actions described in the overview.
+Use when evaluating a specific landing or product page against its audience, conversion goal and observed funnel evidence.
+
+## Example
+
+**Request:** “Visitors reach our trial page but few submit. Review the copy and suggest a test.”
+
+**Output:** First record the actual page, audience, trial terms, observation period and funnel counts. If no measurements exist, label the suspected friction as a hypothesis: clarify the trial commitment near the form and measure submitted trials per eligible visit, with sample/duration and guardrails agreed before launch. Deliver the copy draft and experiment plan; do not invent a conversion lift or publish changes without the requested target authorization.
 
 ## Limitations
 - Use this skill only when the task clearly matches the scope described above.

package/bundled-skills/payment-integration/SKILL.md

@@ -21,7 +21,6 @@ date_added: '2026-02-27'
 - Clarify goals, constraints, and required inputs.
 - Apply relevant best practices and validate outcomes.
 - Provide actionable steps and verification.
-- If detailed examples are required, open `resources/implementation-playbook.md`.
 
 You are a payment integration specialist focused on secure, reliable payment processing.
 

package/bundled-skills/paypal-integration/SKILL.md

@@ -5,6 +5,9 @@ risk: critical
 source: community
 date_added: "2026-02-27"
 ---
+## Supporting material availability
+
+The following are external prerequisites, not bundled files: `<support-root>/references/express-checkout.md`, `<support-root>/references/ipn-handling.md`, `<support-root>/references/refund-workflows.md`, `<support-root>/references/billing-agreements.md`, `<support-root>/assets/paypal-client.py`, `<support-root>/assets/ipn-processor.py`, `<support-root>/assets/recurring-billing.py`. Obtain them from the original source or an existing installation and inspect them before use. Do not execute or claim completion of a dependent step until its required file exists; report unavailable steps. The fully documented inline workflow remains usable within the authorized scope.
 
 # PayPal Integration
 
@@ -20,7 +23,6 @@ Master PayPal payment integration including Express Checkout, IPN handling, recu
 - Clarify goals, constraints, and required inputs.
 - Apply relevant best practices and validate outcomes.
 - Provide actionable steps and verification.
-- If detailed examples are required, open `resources/implementation-playbook.md`.
 
 ## Use this skill when
 

package/bundled-skills/pentest-tools/src-hunter/SKILL.md

@@ -9,6 +9,14 @@ date_added: "2026-08-25"
 license: "MIT"
 license_source: "https://github.com/zhaoxuya520/reverse-skill/blob/main/LICENSE"
 ---
+## Supporting material availability
+
+This catalog copy contains the inline guidance below, but does not include the following supporting paths. They are external prerequisites, not bundled files:
+
+- `<support-root>/templates/report-submission.md`
+
+Obtain the required material from the [declared upstream source](https://github.com/zhaoxuya520/reverse-skill), or from a user-provided installation of that source. Resolve each path relative to that installation, inspect its contents, and verify any applicable license and execution prerequisites. Do not run a command or claim a referenced procedure was followed until its required file exists. Do not fabricate the missing scripts or treat an unrelated file with the same name as equivalent. Independent steps fully documented here can proceed within the user’s authorized scope; report any dependent step as unavailable.
+
 > **⚠️ AUTHORIZED USE ONLY**
 > This skill is for educational purposes or authorized security assessments only.
 > You must have explicit, written permission from the system owner before using this tool.

package/bundled-skills/performance-engineer/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: performance-engineer
-description: "Expert performance engineer specializing in modern observability,"
+description: "Diagnose performance bottlenecks using profiling, traces, load tests, and observability; verify latency and capacity improvements."
 risk: critical
 source: community
 date_added: "2026-02-27"

package/bundled-skills/performance-optimization/SKILL.md

@@ -9,6 +9,14 @@ date_added: 2026-07-01
 license: MIT
 license_source: https://github.com/addyosmani/agent-skills/blob/main/LICENSE
 ---
+## Supporting material availability
+
+This catalog copy contains the inline guidance below, but does not include the following supporting paths. They are external prerequisites, not bundled files:
+
+- `<support-root>/references/performance-checklist.md`
+
+Obtain the required material from the [declared upstream source](https://github.com/addyosmani/agent-skills), or from a user-provided installation of that source. Resolve each path relative to that installation, inspect its contents, and verify any applicable license and execution prerequisites. Do not run a command or claim a referenced procedure was followed until its required file exists. Do not fabricate the missing scripts or treat an unrelated file with the same name as equivalent. Independent steps fully documented here can proceed within the user’s authorized scope; report any dependent step as unavailable.
+
 
 # Performance Optimization
 

package/bundled-skills/performance-testing-review-ai-review/SKILL.md

@@ -5,6 +5,14 @@ risk: critical
 source: community
 date_added: "2026-02-27"
 ---
+## Supporting material availability
+
+This catalog copy contains the inline guidance below, but does not include the following supporting paths. They are external prerequisites, not bundled files:
+
+- `<support-root>/scripts/ai_review.py`
+
+Ask for the original supporting material or an existing installation before using a step that depends on these paths; this catalog does not identify a verified download source for them. Resolve each path relative to that installation, inspect its contents, and verify any applicable license and execution prerequisites. Do not run a command or claim a referenced procedure was followed until its required file exists. Do not fabricate the missing scripts or treat an unrelated file with the same name as equivalent. Independent steps fully documented here can proceed within the user’s authorized scope; report any dependent step as unavailable.
+
 
 # AI-Powered Code Review Specialist
 
@@ -25,7 +33,6 @@ You are an expert AI-powered code review specialist combining automated static a
 - Clarify goals, constraints, and required inputs.
 - Apply relevant best practices and validate outcomes.
 - Provide actionable steps and verification.
-- If detailed examples are required, open `resources/implementation-playbook.md`.
 
 ## Context
 

package/bundled-skills/performance-testing-review-multi-agent-review/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: performance-testing-review-multi-agent-review
-description: "Use when working with performance testing review multi agent review"
+description: "Review a defined code diff from relevant correctness, authorization and performance perspectives; delegate only when authorized and reproduce findings centrally."
 risk: critical
 source: community
 date_added: "2026-02-27"

package/bundled-skills/php-pro/SKILL.md

@@ -27,7 +27,6 @@ date_added: '2026-02-27'
 - Clarify goals, constraints, and required inputs.
 - Apply relevant best practices and validate outcomes.
 - Provide actionable steps and verification.
-- If detailed examples are required, open `resources/implementation-playbook.md`.
 
 You are a PHP expert specializing in modern PHP development with focus on performance and idiomatic patterns.
 

package/bundled-skills/pi-delegate/SKILL.md

@@ -13,6 +13,10 @@ license_source: https://github.com/amElnagdy/delegate-skills/blob/master/LICENSE
 metadata:
   version: 0.5.0
 ---
+## Bundled upstream support
+
+Supporting files are included at skill-relative paths. See [UPSTREAM-NOTICE.md](UPSTREAM-NOTICE.md) for their pinned sources, licenses, hashes, and import changes.
+
 # Pi Delegate
 
 ## When to Use
@@ -142,7 +146,7 @@ expanding the mandate). See [references/review-and-land.md](references/review-an
 
 ## Limitations
 
-- Docs-only import — executable `scripts/relay.mjs` not included; see upstream for full runtime. Requires `pi` CLI, Node 18+, git.
+- Runtime helper `scripts/relay.mjs` is bundled from the revision recorded in `UPSTREAM-NOTICE.md`. Requires the corresponding installed and authenticated CLI, Node 18+, and git.
 - Relay never commits — it only returns structured result JSON; you review and land the commit.
 
 > Adapted from [amElnagdy/delegate-skills](https://github.com/amElnagdy/delegate-skills) (MIT) — docs-only, runtime not bundled.

package/bundled-skills/pi-delegate/UPSTREAM-LICENSE.txt

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Ahmed Mohammed (amElnagdy)
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/bundled-skills/pi-delegate/UPSTREAM-NOTICE.md

@@ -0,0 +1,13 @@
+# Upstream helpers for pi-delegate
+
+The files listed below were recovered from [amElnagdy/delegate-skills](https://github.com/amElnagdy/delegate-skills) at commit `3aa72d681a79e2a9d09bd9a316353003ae1cb4a7`. The repository ID is `1269124956`.
+
+They retain the upstream **MIT** license reproduced in [UPSTREAM-LICENSE.txt](UPSTREAM-LICENSE.txt). This notice applies to the listed support files; it does not replace the license metadata of other catalog files. Preserve the upstream license and this attribution when redistributing them.
+
+License wording is unchanged; text-only trailing whitespace and EOF blank lines are normalized. Original license: https://github.com/amElnagdy/delegate-skills/blob/3aa72d681a79e2a9d09bd9a316353003ae1cb4a7/LICENSE
+
+| Local file | Original upstream path | Original Git blob SHA | Import changes |
+| --- | --- | --- | --- |
+| `scripts/relay.mjs` | `skills/pi-delegate/scripts/relay.mjs` | `19edc868a2ebf311119a9967ed973ed6b1a03e43` | content unchanged |
+
+The relay launches the user-installed, authenticated agent CLI. Write-capable modes can approve child tools automatically; they are not a host sandbox. Invoke only for explicitly authorized delegation, keep credentials out of task briefs, and review the child output and project changes before landing them. This import does not run the CLI.