opencode-skills-collection 4.1.15 → 4.1.17

package/bundled-skills/senior-fullstack/references/architecture_patterns.md

@@ -1,103 +1,7 @@
-# Architecture Patterns
+# Boundary and contract review
 
-## Overview
+Trace a concrete user action from interface to backend and persistence. Document input shape, identity, authorization, domain rule, database operation and response/error shape.
 
-This reference guide provides comprehensive information for senior fullstack.
+Keep authorization on the server. Validate untrusted input at the boundary, use parameterized queries, and prevent another tenant's IDs from granting access. Separate retryable reads from writes that need idempotency and duplicate detection.
 
-## Patterns and Practices
-
-### Pattern 1: Best Practice Implementation
-
-**Description:**
-Detailed explanation of the pattern.
-
-**When to Use:**
-- Scenario 1
-- Scenario 2
-- Scenario 3
-
-**Implementation:**
-```typescript
-// Example code implementation
-export class Example {
-  // Implementation details
-}
-```
-
-**Benefits:**
-- Benefit 1
-- Benefit 2
-- Benefit 3
-
-**Trade-offs:**
-- Consider 1
-- Consider 2
-- Consider 3
-
-### Pattern 2: Advanced Technique
-
-**Description:**
-Another important pattern for senior fullstack.
-
-**Implementation:**
-```typescript
-// Advanced example
-async function advancedExample() {
-  // Code here
-}
-```
-
-## Guidelines
-
-### Code Organization
-- Clear structure
-- Logical separation
-- Consistent naming
-- Proper documentation
-
-### Performance Considerations
-- Optimization strategies
-- Bottleneck identification
-- Monitoring approaches
-- Scaling techniques
-
-### Security Best Practices
-- Input validation
-- Authentication
-- Authorization
-- Data protection
-
-## Common Patterns
-
-### Pattern A
-Implementation details and examples.
-
-### Pattern B
-Implementation details and examples.
-
-### Pattern C
-Implementation details and examples.
-
-## Anti-Patterns to Avoid
-
-### Anti-Pattern 1
-What not to do and why.
-
-### Anti-Pattern 2
-What not to do and why.
-
-## Tools and Resources
-
-### Recommended Tools
-- Tool 1: Purpose
-- Tool 2: Purpose
-- Tool 3: Purpose
-
-### Further Reading
-- Resource 1
-- Resource 2
-- Resource 3
-
-## Conclusion
-
-Key takeaways for using this reference guide effectively.
+Review failure cases: unauthenticated caller, forbidden tenant, invalid input, missing record, provider timeout and partial completion. Define user-facing interface states and safe recovery before introducing background jobs or new infrastructure. Do not perform destructive migrations or provider transactions during an architecture review.

package/bundled-skills/senior-fullstack/references/development_workflows.md

@@ -1,103 +1,7 @@
-# Development Workflows
+# Implementation and verification workflow
 
-## Overview
+Start with an acceptance example and a narrow code change. Identify the affected API consumers and database constraints. Add or adjust meaningful tests for permissions, domain rules and integration failure handling.
 
-This reference guide provides comprehensive information for senior fullstack.
+Run the actual project commands and retain their outcomes. A skipped test, missing integration or unavailable environment is unknown, not a pass. Use fixtures for local provider behavior and distinguish them from a real authorized provider operation.
 
-## Patterns and Practices
-
-### Pattern 1: Best Practice Implementation
-
-**Description:**
-Detailed explanation of the pattern.
-
-**When to Use:**
-- Scenario 1
-- Scenario 2
-- Scenario 3
-
-**Implementation:**
-```typescript
-// Example code implementation
-export class Example {
-  // Implementation details
-}
-```
-
-**Benefits:**
-- Benefit 1
-- Benefit 2
-- Benefit 3
-
-**Trade-offs:**
-- Consider 1
-- Consider 2
-- Consider 3
-
-### Pattern 2: Advanced Technique
-
-**Description:**
-Another important pattern for senior fullstack.
-
-**Implementation:**
-```typescript
-// Advanced example
-async function advancedExample() {
-  // Code here
-}
-```
-
-## Guidelines
-
-### Code Organization
-- Clear structure
-- Logical separation
-- Consistent naming
-- Proper documentation
-
-### Performance Considerations
-- Optimization strategies
-- Bottleneck identification
-- Monitoring approaches
-- Scaling techniques
-
-### Security Best Practices
-- Input validation
-- Authentication
-- Authorization
-- Data protection
-
-## Common Patterns
-
-### Pattern A
-Implementation details and examples.
-
-### Pattern B
-Implementation details and examples.
-
-### Pattern C
-Implementation details and examples.
-
-## Anti-Patterns to Avoid
-
-### Anti-Pattern 1
-What not to do and why.
-
-### Anti-Pattern 2
-What not to do and why.
-
-## Tools and Resources
-
-### Recommended Tools
-- Tool 1: Purpose
-- Tool 2: Purpose
-- Tool 3: Purpose
-
-### Further Reading
-- Resource 1
-- Resource 2
-- Resource 3
-
-## Conclusion
-
-Key takeaways for using this reference guide effectively.
+Prepare schema migration and rollback instructions, deployment target and operational checks when the feature needs them. Review the concrete result before publication. Keep paid transactions, external messages and production deployment within the user's explicit authorization.

package/bundled-skills/senior-fullstack/references/tech_stack_guide.md

@@ -1,103 +1,7 @@
-# Tech Stack Guide
+# Stack inspection checklist
 
-## Overview
+Read the project's dependency manifests, lockfiles, entrypoints and build configuration. Record the frontend framework, backend runtime, persistence layer, authentication boundary and deployment target without replacing them merely to match an example stack.
 
-This reference guide provides comprehensive information for senior fullstack.
+Identify the commands the project actually declares for type checking, tests, linting and build. Check installed versions before selecting an API or adding a dependency. Preserve environment files and keep credentials out of logs and source control.
 
-## Patterns and Practices
-
-### Pattern 1: Best Practice Implementation
-
-**Description:**
-Detailed explanation of the pattern.
-
-**When to Use:**
-- Scenario 1
-- Scenario 2
-- Scenario 3
-
-**Implementation:**
-```typescript
-// Example code implementation
-export class Example {
-  // Implementation details
-}
-```
-
-**Benefits:**
-- Benefit 1
-- Benefit 2
-- Benefit 3
-
-**Trade-offs:**
-- Consider 1
-- Consider 2
-- Consider 3
-
-### Pattern 2: Advanced Technique
-
-**Description:**
-Another important pattern for senior fullstack.
-
-**Implementation:**
-```typescript
-// Advanced example
-async function advancedExample() {
-  // Code here
-}
-```
-
-## Guidelines
-
-### Code Organization
-- Clear structure
-- Logical separation
-- Consistent naming
-- Proper documentation
-
-### Performance Considerations
-- Optimization strategies
-- Bottleneck identification
-- Monitoring approaches
-- Scaling techniques
-
-### Security Best Practices
-- Input validation
-- Authentication
-- Authorization
-- Data protection
-
-## Common Patterns
-
-### Pattern A
-Implementation details and examples.
-
-### Pattern B
-Implementation details and examples.
-
-### Pattern C
-Implementation details and examples.
-
-## Anti-Patterns to Avoid
-
-### Anti-Pattern 1
-What not to do and why.
-
-### Anti-Pattern 2
-What not to do and why.
-
-## Tools and Resources
-
-### Recommended Tools
-- Tool 1: Purpose
-- Tool 2: Purpose
-- Tool 3: Purpose
-
-### Further Reading
-- Resource 1
-- Resource 2
-- Resource 3
-
-## Conclusion
-
-Key takeaways for using this reference guide effectively.
+For a proposed feature, state which layers must change and which contract each layer owns. Prefer an existing component, service or repository abstraction when its behavior fits. Record unsupported environments and missing provider access as limitations.

package/bundled-skills/senior-fullstack/scripts/code_quality_analyzer.py

@@ -58,19 +58,11 @@ class CodeQualityAnalyzer:
             print(f"✓ Target validated: {self.target_path}")
     
     def analyze(self):
-        """Perform the main analysis or operation"""
-        if self.verbose:
-            print("📊 Analyzing...")
-        
-        # Main logic here
-        self.results['status'] = 'success'
-        self.results['target'] = str(self.target_path)
-        self.results['findings'] = []
-        
-        # Add analysis results
-        if self.verbose:
-            print(f"✓ Analysis complete: {len(self.results.get('findings', []))} findings")
-    
+        """Fail closed: this historical helper has no implementation."""
+        raise NotImplementedError(
+            "This helper is an unimplemented skeleton; use the project's real tools."
+        )
+
     def generate_report(self):
         """Generate and display the report"""
         print("\n" + "="*50)

package/bundled-skills/senior-fullstack/scripts/fullstack_scaffolder.py

@@ -58,19 +58,11 @@ class FullstackScaffolder:
             print(f"✓ Target validated: {self.target_path}")
     
     def analyze(self):
-        """Perform the main analysis or operation"""
-        if self.verbose:
-            print("📊 Analyzing...")
-        
-        # Main logic here
-        self.results['status'] = 'success'
-        self.results['target'] = str(self.target_path)
-        self.results['findings'] = []
-        
-        # Add analysis results
-        if self.verbose:
-            print(f"✓ Analysis complete: {len(self.results.get('findings', []))} findings")
-    
+        """Fail closed: this historical helper has no implementation."""
+        raise NotImplementedError(
+            "This helper is an unimplemented skeleton; use the project's real tools."
+        )
+
     def generate_report(self):
         """Generate and display the report"""
         print("\n" + "="*50)

package/bundled-skills/senior-fullstack/scripts/project_scaffolder.py

@@ -58,19 +58,11 @@ class ProjectScaffolder:
             print(f"✓ Target validated: {self.target_path}")
     
     def analyze(self):
-        """Perform the main analysis or operation"""
-        if self.verbose:
-            print("📊 Analyzing...")
-        
-        # Main logic here
-        self.results['status'] = 'success'
-        self.results['target'] = str(self.target_path)
-        self.results['findings'] = []
-        
-        # Add analysis results
-        if self.verbose:
-            print(f"✓ Analysis complete: {len(self.results.get('findings', []))} findings")
-    
+        """Fail closed: this historical helper has no implementation."""
+        raise NotImplementedError(
+            "This helper is an unimplemented skeleton; use the project's real tools."
+        )
+
     def generate_report(self):
         """Generate and display the report"""
         print("\n" + "="*50)

package/bundled-skills/seo-authority-builder/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 an E-E-A-T specialist analyzing content for authority and trust signals.
 

package/bundled-skills/seo-cannibalization-detector/SKILL.md

@@ -21,7 +21,7 @@ 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`.
+- Use the examples below; no separate implementation playbook is bundled.
 
 You are a keyword cannibalization specialist analyzing content overlap between provided pages.
 
@@ -66,7 +66,7 @@ You are a keyword cannibalization specialist analyzing content overlap between p
 1. Analyze keywords in provided pages
 2. Identify topic and keyword overlap
 3. Compare search intent targets
-4. Assess content similarity percentage
+4. Describe observed similarity and its method; do not invent a measured percentage
 5. Find differentiation opportunities
 6. Suggest consolidation if needed
 7. Recommend unique angle for each
@@ -121,6 +121,10 @@ Resolution Strategy:
 
 Focus on clear differentiation. Each page should serve a unique purpose with distinct targeting.
 
+## Evidence and change boundaries
+
+Topic or keyword overlap is a candidate for investigation, not proof of harmful cannibalization. Require supplied Search Console/analytics evidence, query intent and relevant observation windows before claiming ranking loss. Preserve pages that serve different intents. Canonical tags are hints for duplicate or substantially similar content, not a generic fix for every shared keyword. Propose the exact consolidation/redirect target, preserve useful content and existing links, and verify backups/rollback before an authorized site change. No publishing or redirect mutation is performed by this audit alone.
+
 ## Limitations
 - Use this skill only when the task clearly matches the scope described above.
 - Do not treat the output as a substitute for environment-specific validation, testing, or expert review.

package/bundled-skills/seo-content/SKILL.md

@@ -16,6 +16,14 @@ allowed-tools:
   - Bash
   - WebFetch
 ---
+## 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:
+
+- `seo/references/eeat-framework.md`
+
+Obtain the required material from the [declared upstream source](https://github.com/AgriciDaniel/claude-seo), 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.
+
 
 # Content Quality & E-E-A-T Analysis
 

package/bundled-skills/seo-content-auditor/SKILL.md

@@ -21,7 +21,7 @@ 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`.
+- Use the examples below; no separate implementation playbook is bundled.
 
 You are an SEO content auditor analyzing provided content for optimization opportunities.
 
@@ -65,6 +65,8 @@ You are an SEO content auditor analyzing provided content for optimization oppor
 ## Output
 
 **Content Audit Report:**
+
+Any 1–10 score is an explicitly stated editorial rubric, not a Google E-E-A-T measurement, ranking predictor or validated quality certificate. Prefer findings with quoted evidence and unknowns to unsupported numeric precision. Do not invent credentials, testimonials, source citations or performance data. Draft recommendations; publication requires the target’s authorization.
 | Category | Score | Issues Found | Recommendations |
 |----------|-------|--------------|----------------|
 | Content Depth | X/10 | Missing subtopics | Add sections on... |

package/bundled-skills/seo-directory-backlinks/SKILL.md

@@ -11,6 +11,14 @@ tags: [sme, seo, backlinks, citations, directories, local-seo, nap-consistency,
 tools: []
 source_repo: WHOISABHISHEKADHIKARI/sme-ops-system-builder
 ---
+## 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:
+
+- `../../references/backlink-directory-master-list.md`
+
+Obtain the required material from the [declared upstream source](https://github.com/WHOISABHISHEKADHIKARI/sme-ops-system-builder), 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.
+
 
 # SEO Directories & Backlinks
 

package/bundled-skills/seo-image-gen/SKILL.md

@@ -14,6 +14,20 @@ allowed-tools:
   - WebFetch
   - Write
 ---
+## 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/prompt-engineering.md`
+- `<support-root>/references/seo-image-presets.md`
+- `<support-root>/references/gemini-models.md`
+- `<support-root>/references/mcp-tools.md`
+- `<support-root>/references/post-processing.md`
+- `<support-root>/references/cost-tracking.md`
+- `<support-root>/references/presets.md`
+
+Obtain the required material from the [declared upstream source](https://github.com/AgriciDaniel/claude-seo), 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.
+
 
 # SEO Image Gen: AI Image Generation for SEO Assets (Extension)
 

package/bundled-skills/seo-keyword-strategist/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 keyword strategist analyzing content for semantic optimization opportunities.
 

package/bundled-skills/seo-meta-optimizer/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 meta tag optimization specialist creating compelling metadata within best practice guidelines.
 

package/bundled-skills/seo-schema/SKILL.md

@@ -17,6 +17,14 @@ allowed-tools:
   - WebFetch
   - Write
 ---
+## 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/schema-types.md`
+
+Obtain the required material from the [declared upstream source](https://github.com/AgriciDaniel/claude-seo), 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.
+
 
 # Schema Markup Analysis & Generation
 

package/bundled-skills/seo-snippet-hunter/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 featured snippet optimization specialist formatting content for position zero potential.
 

package/bundled-skills/seo-structure-architect/SKILL.md

@@ -21,7 +21,7 @@ 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`.
+- Use the examples below; no separate implementation playbook is bundled.
 
 You are a content structure specialist analyzing and improving information architecture.
 
@@ -54,7 +54,7 @@ You are a content structure specialist analyzing and improving information archi
 
 ## Schema Markup Priority
 
-**High-Impact Schemas:**
+**Schema types to consider only when they match visible content:**
 - Article/BlogPosting
 - FAQ Schema
 - HowTo Schema
@@ -106,6 +106,10 @@ H1: Primary Keyword Focus
 
 Focus on logical flow and scannable content. Create clear information hierarchy for users and search engines.
 
+## Structured-data scope
+
+Valid Schema.org markup does not guarantee a Google rich result. Verify current feature eligibility in [Google’s structured-data gallery](https://developers.google.com/search/docs/appearance/structured-data/search-gallery); HowTo rich results are deprecated; [Google’s May 2026 update](https://developers.google.com/search/updates) states that FAQ rich results stopped appearing on May 7, 2026. Keep semantic markup only where it describes real visible content; do not promise either rich-result feature. Mark up only visible, truthful content and genuine reviews; never fabricate rating totals or customer evidence. Validate the exact JSON-LD and actual rendered page. Prepare changes as a draft; publishing, canonical/redirect changes and new plugins require target authorization.
+
 ## Limitations
 - Use this skill only when the task clearly matches the scope described above.
 - Do not treat the output as a substitute for environment-specific validation, testing, or expert review.

package/bundled-skills/sequence-psychologist/SKILL.md

@@ -5,12 +5,18 @@ risk: safe
 source: community
 date_added: "2026-04-04"
 ---
-You are a **Behavioral Psychologist specializing in persuasion sequencing and relationship psychology**. Your task is to design email nurture sequences and multi-touch communication flows using psychological principles of curiosity loops, reciprocity, commitment, and emotional pacing.
+Use a marketing planning and audience-research lens. Your task is to design email nurture sequences and multi-touch communication flows using psychological principles of curiosity loops, reciprocity, commitment, and emotional pacing.
 
 ## When to Use
 - Use when an email, onboarding, or sales sequence needs a better step-by-step persuasion arc.
 - Use when each touchpoint should prepare the next instead of repeating the same appeal.
 
+## Evidence and scope
+
+Use observed audience research and verified product facts. Psychological interpretations and the author-year references below are inherited conceptual context, not validated evidence for this exact workflow or a guaranteed conversion effect. Before using a scientific claim externally, verify the actual publication, method and applicability; omit unsupported claims. This is marketing planning, not clinical diagnosis. Do not infer sensitive traits or exploit vulnerabilities.
+
+Original contribution: [PR 451](https://github.com/sickn33/agentic-awesome-skills/pull/451) by MMEHDI0606; [immutable source snapshot](https://github.com/MMEHDI0606/antigravity-awesome-skills/blob/9c61357e3e6bb167946036f52ac1e28fc82e04d0/skills/sequence-psychologist/SKILL.md). This identifies the contributed instructions, not scientific validation or a new upstream endorsement.
+
 ## CONTEXT GATHERING
 
 Before designing a sequence, establish:
@@ -31,23 +37,23 @@ People move when messages create a manageable emotional arc: curiosity, recognit
 
 **Step 1 - Define the emotional arc**
 Map each email to a single emotional objective.
-*Research basis: persuasive sequences work better when they pace emotion and cognition instead of repeating the same ask (Cialdini; narrative sequence research).*
+*Planning hypothesis (verify before presenting as research): persuasive sequences work better when they pace emotion and cognition instead of repeating the same ask (Cialdini; narrative sequence research).*
 
 **Step 2 - Open the loop**
 Create a curiosity gap or unresolved question the next email will answer.
-*Research basis: open loops increase attention when the promised payoff is real (Zeigarnik effect; curiosity research).*
+*Planning hypothesis (verify before presenting as research): open loops increase attention when the promised payoff is real (Zeigarnik effect; curiosity research).*
 
 **Step 3 - Give before asking**
 Use useful content, insight, or relief before the ask.
-*Research basis: reciprocity and liking increase receptivity when the audience has already received value (Cialdini).*
+*Planning hypothesis (verify before presenting as research): reciprocity and liking increase receptivity when the audience has already received value (Cialdini).*
 
 **Step 4 - Escalate commitment gradually**
 Move from low-friction responses to higher-friction decisions.
-*Research basis: foot-in-the-door and consistency effects increase compliance when the steps are coherent (Cialdini; behavioral change research).*
+*Planning hypothesis (verify before presenting as research): foot-in-the-door and consistency effects increase compliance when the steps are coherent (Cialdini; behavioral change research).*
 
 **Step 5 - End with a clean decision**
 Make the final email simple, concrete, and autonomy-preserving.
-*Research basis: choice clarity reduces avoidance and supports follow-through (Fogg; Lavoie & Quick, 2013).*
+*Planning hypothesis (verify before presenting as research): choice clarity reduces avoidance and supports follow-through (Fogg; Lavoie & Quick, 2013).*
 
 ## DECISION MATRIX
 
@@ -94,7 +100,7 @@ The line between persuasion and manipulation is pacing a real relationship towar
 
 ## SKILL CHAINING
 
-Before invoking this skill, the agent should have completed:
+Optional context from related skills (equivalent supplied research is sufficient; do not create a prerequisite cycle):
 - [ ] `@customer-psychographic-profiler`
 - [ ] `@awareness-stage-mapper`
 - [ ] `@objection-preemptor`
@@ -119,6 +125,8 @@ Before finalizing output, the agent asks:
 
 > Rewrite this email sequence with a clearer step-by-step persuasion arc and credible transitions.
 
+**Illustrative output:** Draft three opt-in messages: useful explanation, verified example and optional next step; record consent/stop conditions and do not send anything as part of planning.
+
 ## Limitations
 - Use this skill only when the task clearly matches the scope described above.
 - Do not treat the output as a substitute for environment-specific validation, testing, or expert review.

package/bundled-skills/service-mesh-expert/SKILL.md

@@ -20,7 +20,6 @@ Expert service mesh architect specializing in Istio, Linkerd, and cloud-native n
 - 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`.
 
 ## Capabilities