opencode-skills-collection 4.0.53 → 4.0.55

package/bundled-skills/incident-responder/resources/implementation-playbook.md

@@ -0,0 +1,23 @@
+# Incident response handoff
+
+## Inputs
+
+Affected journey, detection time, incident commander, response permissions and approved communication channel.
+
+## Procedure
+
+1. Record impact, uncertainty and the last known healthy state. Establish a single decision owner and a timestamped event log.
+2. Prioritize a reversible mitigation supported by evidence. Record expected recovery, abort threshold and rollback before an authorized production change.
+3. Validate recovery through the user journey and dependency health over an agreed observation window. Draft the handoff and follow-up actions; send external updates only with authorization.
+
+## Worked example
+
+Checkout failures start after a configuration change. Compare affected instances, propose restoring the prior configuration, and verify successful checkout rather than merely green processes.
+
+## Verification and handoff
+
+Report the actual files or configuration changed, checks performed, observed results and any untested environment. Keep the original inputs and evidence sufficient to reproduce the conclusion.
+
+## Limitations
+
+Severity labels and response times are organization-specific, not universal SLAs. Never invent a recovery ETA or confirmed root cause.

package/bundled-skills/incident-response-incident-response/SKILL.md

@@ -170,6 +170,12 @@ Orchestrate multi-agent incident response with modern SRE practices for rapid re
 
 Production incident requiring immediate response: $ARGUMENTS
 
+## Example
+
+**User request:**
+
+> Use @incident-response-incident-response for this task: Use when working with incident response incident response.
+
 ## 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/industrial-brutalist-ui/SKILL.md

@@ -19,6 +19,12 @@ tools: [claude, cursor, codex, antigravity]
 - Use when building data-heavy dashboards, portfolios, editorial pages, or command-center UIs that should feel raw and mechanical.
 - Use when a design must reject soft gradients, rounded consumer UI, glassmorphism, and generic SaaS card layouts.
 
+## Example
+
+**User request:**
+
+> Review this interface with @industrial-brutalist-ui, identify the highest-impact design problems, and propose an implementation-ready improvement.
+
 ## Limitations
 
 - This style is intentionally severe and may not fit consumer products, accessibility-sensitive flows, or brands that require warmth and softness.

package/bundled-skills/instagram/scripts/config.py

@@ -7,6 +7,7 @@ Importado por todos os outros scripts.
 from __future__ import annotations
 
 import os
+import stat
 import shutil
 from pathlib import Path
 from typing import Any, Dict
@@ -23,6 +24,35 @@ EXPORTS_DIR = DATA_DIR / "exports"
 STATIC_DIR = ROOT_DIR / "static"
 DB_PATH = DATA_DIR / "instagram.db"
 
+def protect_state_path(path, *, directory=False):
+    """Repair only owned state paths; never follow links or mutate hard links."""
+    flags = os.O_RDONLY | getattr(os, "O_NOFOLLOW", 0) | getattr(os, "O_NONBLOCK", 0)
+    if path.is_symlink():
+        raise OSError(f"Refusing linked state path: {path}")
+    if directory:
+        path.mkdir(parents=True, exist_ok=True, mode=0o700)
+        # Windows does not support opening directories this way; privacy there
+        # is governed by the user profile ACL, not POSIX permission bits.
+        if os.name == "nt":
+            path.chmod(0o700)
+            return
+        flags |= getattr(os, "O_DIRECTORY", 0)
+    elif not path.exists():
+        return
+    fd = os.open(path, flags)
+    try:
+        info = os.fstat(fd)
+        valid = stat.S_ISDIR(info.st_mode) if directory else stat.S_ISREG(info.st_mode) and info.st_nlink == 1
+        if not valid:
+            raise OSError(f"Refusing unsafe state path: {path}")
+        if hasattr(os, "fchmod"):
+            os.fchmod(fd, 0o700 if directory else 0o600)
+        else:
+            os.chmod(path, 0o600)
+    finally:
+        os.close(fd)
+
+
 # Tokens and app secrets are stored in the SQLite database. Keep every newly
 # created database, journal, and sidecar private, and migrate legacy state once.
 os.umask(0o077)
@@ -30,14 +60,9 @@ if LEGACY_DATA_DIR.exists() and LEGACY_DATA_DIR != DATA_DIR and not DATA_DIR.exi
     DATA_DIR.parent.mkdir(parents=True, exist_ok=True, mode=0o700)
     shutil.move(str(LEGACY_DATA_DIR), str(DATA_DIR))
     print(f"AVISO: dados sensiveis do Instagram migrados para {DATA_DIR}")
-for directory in (DATA_DIR.parent.parent, DATA_DIR.parent, DATA_DIR, EXPORTS_DIR):
-    directory.mkdir(parents=True, exist_ok=True, mode=0o700)
-    try:
-        directory.chmod(0o700)
-    except OSError:
-        pass
-if DB_PATH.exists() and not DB_PATH.is_symlink():
-    DB_PATH.chmod(0o600)
+for directory in (DATA_DIR, EXPORTS_DIR):
+    protect_state_path(directory, directory=True)
+protect_state_path(DB_PATH)
 
 # ── Instagram Graph API ───────────────────────────────────────────────────────
 API_VERSION = "v21.0"

package/bundled-skills/interactive-portfolio/SKILL.md

@@ -32,489 +32,9 @@ seconds count. You help people stand out without being gimmicky.
 - Creative coding
 - Memorable experiences
 
-## Capabilities
+## Detailed Guide
 
-- Portfolio architecture
-- Project showcase design
-- Interactive case studies
-- Personal branding for devs/designers
-- Contact conversion
-- Portfolio performance
-- Work presentation
-- Testimonial integration
-
-## Patterns
-
-### Portfolio Architecture
-
-Structure that works for portfolios
-
-**When to use**: When planning portfolio structure
-
-## Portfolio Architecture
-
-### The 30-Second Test
-In 30 seconds, visitors should know:
-1. Who you are
-2. What you do
-3. Your best work
-4. How to contact you
-
-### Essential Sections
-| Section | Purpose | Priority |
-|---------|---------|----------|
-| Hero | Hook + identity | Critical |
-| Work/Projects | Prove skills | Critical |
-| About | Personality + story | Important |
-| Contact | Convert interest | Critical |
-| Testimonials | Social proof | Nice to have |
-| Blog/Writing | Thought leadership | Optional |
-
-### Navigation Patterns
-```
-Option 1: Single page scroll
-- Best for: Designers, creatives
-- Works well with animations
-- Mobile friendly
-
-Option 2: Multi-page
-- Best for: Lots of projects
-- Individual case study pages
-- Better for SEO
-
-Option 3: Hybrid
-- Main sections on one page
-- Detailed case studies separate
-- Best of both worlds
-```
-
-### Hero Section Formula
-```
-[Your name]
-[What you do in one line]
-[One line that differentiates you]
-[CTA: View Work / Contact]
-```
-
-### Project Showcase
-
-How to present work effectively
-
-**When to use**: When building project sections
-
-## Project Showcase
-
-### Project Card Elements
-| Element | Purpose |
-|---------|---------|
-| Thumbnail | Visual hook |
-| Title | What it is |
-| One-liner | What you did |
-| Tech/tags | Quick scan |
-| Results | Proof of impact |
-
-### Case Study Structure
-```
-1. Hero image/video
-2. Project overview (2-3 sentences)
-3. The challenge
-4. Your role
-5. Process highlights
-6. Key decisions
-7. Results/impact
-8. Learnings (optional)
-9. Links (live, GitHub, etc.)
-```
-
-### Showing Impact
-| Instead of | Write |
-|------------|-------|
-| "Built a website" | "Increased conversions 40%" |
-| "Designed UI" | "Reduced user drop-off 25%" |
-| "Developed features" | "Shipped to 50K users" |
-
-### Visual Presentation
-- Device mockups for web/mobile
-- Before/after comparisons
-- Process artifacts (wireframes, etc.)
-- Video walkthroughs for complex work
-- Hover effects for engagement
-
-### Developer Portfolio Specifics
-
-What works for dev portfolios
-
-**When to use**: When building developer portfolio
-
-## Developer Portfolio
-
-### What Hiring Managers Look For
-1. Code quality (GitHub link)
-2. Real projects (not just tutorials)
-3. Problem-solving ability
-4. Communication skills
-5. Technical depth
-
-### Must-Haves
-- GitHub profile link (cleaned up)
-- Live project links
-- Tech stack for each project
-- Your specific contribution (for team projects)
-
-### Project Selection
-| Include | Avoid |
-|---------|-------|
-| Real problems solved | Tutorial clones |
-| Side projects with users | Incomplete projects |
-| Open source contributions | "Coming soon" |
-| Technical challenges | Basic CRUD apps |
-
-### Technical Showcase
-```javascript
-// Show code snippets that demonstrate:
-- Clean architecture decisions
-- Performance optimizations
-- Clever solutions
-- Testing approach
-```
-
-### Blog/Writing
-- Technical deep dives
-- Problem-solving stories
-- Learning journeys
-- Shows communication skills
-
-### Portfolio Interactivity
-
-Adding memorable interactive elements
-
-**When to use**: When wanting to stand out
-
-## Portfolio Interactivity
-
-### Levels of Interactivity
-| Level | Example | Risk |
-|-------|---------|------|
-| Subtle | Hover effects, smooth scroll | Low |
-| Medium | Scroll animations, transitions | Medium |
-| High | 3D, games, custom cursors | High |
-
-### High-Impact, Low-Risk
-- Custom cursor on desktop
-- Smooth page transitions
-- Project card hover effects
-- Scroll-triggered reveals
-- Dark/light mode toggle
-
-### Creative Ideas
-```
-- Terminal-style interface (for devs)
-- OS desktop metaphor
-- Game-like navigation
-- Interactive timeline
-- 3D workspace scene
-- Generative art background
-```
-
-### The Balance
-- Creativity shows skill
-- But usability wins jobs
-- Mobile must work perfectly
-- Don't hide content behind interactions
-- Have a "skip" option for complex intros
-
-## Sharp Edges
-
-### Portfolio more complex than your actual work
-
-Severity: MEDIUM
-
-Situation: Spent 6 months on portfolio, have 2 projects to show
-
-Symptoms:
-- Been "working on portfolio" for months
-- More excited about portfolio than projects
-- Portfolio tech more impressive than work
-- Afraid to launch
-
-Why this breaks:
-Procrastination disguised as work.
-Portfolio IS a project, but not THE project.
-Diminishing returns on polish.
-Ship it and iterate.
-
-Recommended fix:
-
-## Right-Sizing Your Portfolio
-
-### The MVP Portfolio
-| Element | MVP Version |
-|---------|-------------|
-| Hero | Name + title + one line |
-| Projects | 3-4 best pieces |
-| About | 2-3 paragraphs |
-| Contact | Email + LinkedIn |
-
-### Time Budget
-```
-Week 1: Design and structure
-Week 2: Build core pages
-Week 3: Add 3-4 projects
-Week 4: Polish and launch
-```
-
-### The Truth
-- Your portfolio is not your best project
-- Shipping beats perfecting
-- You can always iterate
-- Better projects > better portfolio
-
-### When to Stop
-- Core pages work on mobile
-- 3-4 solid projects showcased
-- Contact form works
-- Loads in < 3 seconds
-- Ship it.
-
-### Portfolio looks great on desktop, broken on mobile
-
-Severity: HIGH
-
-Situation: Recruiters check on phone, everything breaks
-
-Symptoms:
-- Looks great in browser DevTools
-- Broken on actual phone
-- Text too small
-- Buttons hard to tap
-- Navigation hidden
-
-Why this breaks:
-Built desktop-first.
-Didn't test on real devices.
-Complex interactions don't translate.
-Forgot about thumb zones.
-
-Recommended fix:
-
-## Mobile-First Portfolio
-
-### Mobile Reality
-- 60%+ traffic is mobile
-- Recruiters browse on phones
-- First impression = mobile impression
-
-### Mobile Must-Haves
-- Readable without zooming
-- Tappable links (min 44px)
-- Navigation works
-- Projects load fast
-- Contact easy to find
-
-### Testing Checklist
-```
-[ ] iPhone Safari
-[ ] Android Chrome
-[ ] Tablet sizes
-[ ] Slow 3G simulation
-[ ] Real device (not just DevTools)
-```
-
-### Graceful Degradation
-```css
-/* Complex hover → simple tap */
-@media (hover: none) {
-  .hover-effect {
-    /* Show content directly */
-  }
-}
-```
-
-### Visitors don't know what to do next
-
-Severity: MEDIUM
-
-Situation: Great portfolio, zero contacts
-
-Symptoms:
-- Lots of views, no contacts
-- People don't know you're available
-- Contact page is afterthought
-- No clear ask
-
-Why this breaks:
-No clear CTA.
-Contact buried at bottom.
-Multiple competing actions.
-Assuming visitors will figure it out.
-
-Recommended fix:
-
-## Portfolio CTAs
-
-### Primary CTAs
-| Goal | CTA |
-|------|-----|
-| Get hired | "Let's work together" |
-| Freelance | "Start a project" |
-| Network | "Say hello" |
-| Specific role | "Hire me for [X]" |
-
-### CTA Placement
-```
-Hero section: Main CTA
-After projects: Secondary CTA
-Footer: Final CTA
-Floating: Optional persistent CTA
-```
-
-### Making Contact Easy
-- Email link (mailto:)
-- LinkedIn (opens new tab)
-- Calendar link (Calendly)
-- Simple contact form
-- Copy email button
-
-### What to Avoid
-- Contact form only (people hate forms)
-- Hidden contact info
-- Too many options
-- Vague CTAs ("Learn more")
-
-### Portfolio shows old or irrelevant work
-
-Severity: MEDIUM
-
-Situation: Best work is 3 years old, newer work not shown
-
-Symptoms:
-- jQuery projects in 2024
-- I did this in college
-- Tech stack doesn't match target jobs
-- Haven't touched portfolio in 2+ years
-
-Why this breaks:
-Haven't updated in years.
-Newer work is "not ready."
-Scared to remove old favorites.
-Portfolio drift.
-
-Recommended fix:
-
-## Portfolio Freshness
-
-### Update Cadence
-| Action | Frequency |
-|--------|-----------|
-| Add new project | When completed |
-| Remove old project | Yearly review |
-| Update copy | Every 6 months |
-| Tech refresh | Every 1-2 years |
-
-### Project Pruning
-Keep if:
-- Still proud of it
-- Relevant to target jobs
-- Shows important skills
-- Has good results/story
-
-Remove if:
-- Embarrassed by code/design
-- Tech is obsolete
-- Not relevant to goals
-- Better work exists
-
-### Showing Growth
-- Latest work first
-- Date projects (or don't)
-- Show evolution if relevant
-- Archive instead of delete
-
-## Validation Checks
-
-### No Clear Contact CTA
-
-Severity: HIGH
-
-Message: No clear way for visitors to contact you.
-
-Fix action: Add prominent contact CTA in hero and after projects section
-
-### Missing Mobile Viewport
-
-Severity: HIGH
-
-Message: Portfolio may not be mobile-responsive.
-
-Fix action: Add <meta name='viewport' content='width=device-width, initial-scale=1'>
-
-### Unoptimized Portfolio Images
-
-Severity: MEDIUM
-
-Message: Portfolio images may be slowing down load time.
-
-Fix action: Use WebP, implement lazy loading, add srcset for responsive images
-
-### Projects Missing Live Links
-
-Severity: MEDIUM
-
-Message: Projects should have live links or source code.
-
-Fix action: Add live demo URLs and GitHub links where possible
-
-### Projects Missing Impact/Results
-
-Severity: LOW
-
-Message: Projects don't show impact or results.
-
-Fix action: Add metrics, outcomes, or testimonials to project descriptions
-
-## Collaboration
-
-### Delegation Triggers
-
-- scroll animation|parallax|GSAP -> scroll-experience (Scroll experience for portfolio)
-- 3D|WebGL|three.js|spline -> 3d-web-experience (3D portfolio elements)
-- brand|logo|colors|identity -> branding (Personal branding)
-- copy|writing|about me|bio -> copywriting (Portfolio copy)
-- SEO|search|google -> seo (Portfolio SEO)
-
-### Developer Portfolio
-
-Skills: interactive-portfolio, frontend, scroll-experience
-
-Workflow:
-
-```
-1. Plan portfolio structure
-2. Select 3-5 best projects
-3. Design hero and project sections
-4. Add subtle scroll animations
-5. Implement and optimize
-6. Launch and share
-```
-
-### Creative Portfolio
-
-Skills: interactive-portfolio, 3d-web-experience, scroll-experience, branding
-
-Workflow:
-
-```
-1. Define personal brand
-2. Design unique experience
-3. Build interactive elements
-4. Showcase work creatively
-5. Ensure mobile works
-6. Launch
-```
-
-## Related Skills
-
-Works well with: `scroll-experience`, `3d-web-experience`, `landing-page-design`, `personal-branding`
+Read [the detailed guide](references/detailed-guide.md) before executing this skill. It retains the complete procedure and reference material. Treat its safety, prerequisites, and validation requirements as mandatory. For focused work, load the relevant sections; for end-to-end work, read the guide completely.
 
 ## When to Use
 - User mentions or implies: portfolio