opencode-skills-collection 4.1.15 → 4.1.16

package/bundled-skills/swiftui-ui-patterns/references/lightweight-clients.md

@@ -16,13 +16,13 @@ struct SomeClient {
 
 extension SomeClient {
     static func live(baseURL: URL = URL(string: "https://example.com")!) -> SomeClient {
-        let session = URLSession.shared
+        // Scaffold only: no live network implementation is bundled.
         return SomeClient(
             fetchItems: { limit in
-                // build URL, call session, decode
+                throw URLError(.unsupportedURL) // Implement and test the project adapter before use.
             },
             search: { query, limit in
-                // build URL, call session, decode
+                throw URLError(.unsupportedURL) // Implement and test the project adapter before use.
             }
         )
     }

package/bundled-skills/swiftui-ui-patterns/references/list.md

@@ -13,7 +13,7 @@ Use `List` for feed-style content and settings-style rows where built-in row reu
 - Use `.listStyle(.grouped)` for multi-section discovery/search pages where section grouping helps.
 - Apply `.scrollContentBackground(.hidden)` + a custom background when you need a themed surface.
 - Use `.listRowInsets(...)` and `.listRowSeparator(.hidden)` to tune row spacing and separators.
-- Use `.environment(\\.defaultMinListRowHeight, ...)` to control dense list layouts.
+- Use `.environment(\.defaultMinListRowHeight, ...)` to control dense list layouts.
 
 ## Example: feed list with scroll-to-top
 
@@ -34,7 +34,7 @@ struct TimelineListView: View {
         }
       }
       .listStyle(.plain)
-      .environment(\\.defaultMinListRowHeight, 1)
+      .environment(\.defaultMinListRowHeight, 1)
       .onChange(of: scrollToId) { _, newValue in
         if let newValue {
           proxy.scrollTo(newValue, anchor: .top)

package/bundled-skills/swiftui-ui-patterns/references/matched-transitions.md

@@ -17,10 +17,12 @@ Use matched transitions to create smooth continuity between a source view (thumb
 struct MediaPreview: View {
   @Namespace private var namespace
   @State private var selected: MediaAttachment?
+  let attachment: MediaAttachment
 
   var body: some View {
     ThumbnailView()
-      .matchedTransitionSource(id: selected?.id ?? "", in: namespace)
+      .matchedTransitionSource(id: attachment.id, in: namespace)
+      .onTapGesture { selected = attachment }
       .sheet(item: $selected) { item in
         MediaViewer(item: item)
           .navigationTransition(.zoom(sourceID: item.id, in: namespace))

package/bundled-skills/swiftui-ui-patterns/references/media.md

@@ -26,6 +26,9 @@ struct MediaPreviewRow: View {
           LazyImage(url: attachment.previewURL) { state in
             if let image = state.image {
               image.resizable().aspectRatio(contentMode: .fill)
+            } else if state.error != nil {
+              Image(systemName: "photo.badge.exclamationmark")
+                .accessibilityLabel("Image unavailable")
             } else {
               ProgressView()
             }

package/bundled-skills/swiftui-ui-patterns/references/overlay.md

@@ -22,10 +22,15 @@ struct AppRootView: View {
         if let toast {
           ToastView(toast: toast)
             .transition(.move(edge: .top).combined(with: .opacity))
-            .onAppear {
-              DispatchQueue.main.asyncAfter(deadline: .now() + 2) {
+            .task(id: toast.id) {
+              do {
+                try await Task.sleep(for: .seconds(2))
+                try Task.checkCancellation()
+                guard self.toast?.id == toast.id else { return }
                 withAnimation { self.toast = nil }
-              }
+              } catch is CancellationError {
+                return
+              } catch { return }
             }
         }
       }

package/bundled-skills/swiftui-ui-patterns/references/performance.md

@@ -32,11 +32,8 @@ ForEach(Array(items.enumerated()), id: \.offset) { _, item in
 
 ```swift
 struct FeedView: View {
-  let items: [FeedItem]
-
-  private var sortedItems: [FeedItem] {
-    items.sorted(using: KeyPathComparator(\.createdAt, order: .reverse))
-  }
+  // Sorted and cached by the owning store when its input changes.
+  let sortedItems: [FeedItem]
 
   var body: some View {
     List(sortedItems) { item in

package/bundled-skills/swiftui-ui-patterns/references/scroll-reveal.md

@@ -127,7 +127,9 @@ This keeps the motion coherent and avoids duplicate-hit-target bugs.
 - Do not store derived state like `isSecondaryVisible` unless another API requires it. Prefer deriving it from `progress` or visible scroll targets.
 - Beware of layout feedback loops when measuring heights. Clamp zero values and update only when the measured height actually changes.
 
-## Concrete example
+## Historical author examples
+
+These are the original author’s private checkout paths, not bundled files or prerequisites. Use the self-contained schematic pattern above and real files from the current project; do not claim these historical files were opened.
 
 - Pool iOS tile detail reveal: `/Users/dimillian/Documents/Dev/Pool/pool-ios/Pool/Sources/Features/Tile/Detail/TileDetailView.swift`
 - Secondary content anchor example: `/Users/dimillian/Documents/Dev/Pool/pool-ios/Pool/Sources/Features/Tile/Detail/TileDetailIntentListView.swift`

package/bundled-skills/swiftui-ui-patterns/references/searchable.md

@@ -41,20 +41,36 @@ struct ExploreView: View {
         Text(scope.title)
       }
     }
-    .task(id: searchQuery) {
-      await runSearch()
+    .task(id: [searchQuery, String(describing: searchScope)]) {
+      await runSearch(query: searchQuery, scope: searchScope)
     }
   }
 
-  private func runSearch() async {
-    guard !searchQuery.isEmpty else {
+  private func runSearch(query requestedQuery: String, scope requestedScope: SearchScope) async {
+    guard !requestedQuery.isEmpty else {
       results = []
+      isSearching = false
       return
     }
     isSearching = true
-    defer { isSearching = false }
-    try? await Task.sleep(for: .milliseconds(250))
-    results = await fetchResults(query: searchQuery, scope: searchScope)
+    defer {
+      if !Task.isCancelled && searchQuery == requestedQuery && searchScope == requestedScope {
+        isSearching = false
+      }
+    }
+    do {
+      try await Task.sleep(for: .milliseconds(250))
+      try Task.checkCancellation()
+      let fetched = await fetchResults(query: requestedQuery, scope: requestedScope)
+      try Task.checkCancellation()
+      guard searchQuery == requestedQuery && searchScope == requestedScope else { return }
+      results = fetched
+    } catch is CancellationError {
+      return
+    } catch {
+      guard !Task.isCancelled else { return }
+      results = []
+    }
   }
 }
 ```

package/bundled-skills/swiftui-ui-patterns/references/sheets.md

@@ -34,13 +34,10 @@ enum SheetDestination: Identifiable, Hashable {
 
   var id: String {
     switch self {
-    case .composer, .editProfile:
-      // Use the same id to ensure only one editor-like sheet is active at a time.
-      return "editor"
-    case .settings:
-      return "settings"
-    case .report:
-      return "report"
+    case .composer: return "composer"
+    case .editProfile: return "edit-profile"
+    case .settings: return "settings"
+    case .report(let itemID): return "report-\(itemID)"
     }
   }
 }
@@ -122,19 +119,28 @@ struct EditItemSheet: View {
 
   let item: Item
   @State private var isSaving = false
+  @State private var saveError: String?
 
   var body: some View {
     VStack {
       Button(isSaving ? "Saving..." : "Save") {
         Task { await save() }
       }
+      .disabled(isSaving)
+      if let saveError { Text(saveError) }
     }
   }
 
   private func save() async {
+    guard !isSaving else { return }
     isSaving = true
-    await store.save(item)
-    dismiss()
+    defer { isSaving = false }
+    do {
+      try await store.save(item) // Project adapter must report actual failure.
+      dismiss()
+    } catch {
+      saveError = "Save failed. Please try again."
+    }
   }
 }
 ```
@@ -143,7 +149,7 @@ struct EditItemSheet: View {
 
 - Centralize sheet routing so features can present modals without wiring bindings through many layers.
 - Use `sheet(item:)` to guarantee a single sheet is active and to drive presentation from the enum.
-- Group related sheets under the same `id` when they are mutually exclusive (e.g., editor flows).
+- Give every destination a distinct stable identity, including its associated item ID. One optional sheet value already expresses mutual exclusion; sharing IDs can preserve the wrong content.
 - Keep sheet views lightweight and composed from smaller views; avoid large monoliths.
 - Let sheets own their actions and call `dismiss()` internally instead of forwarding `onCancel` or `onConfirm` closures through many layers.
 

package/bundled-skills/swiftui-ui-patterns/references/split-views.md

@@ -49,7 +49,10 @@ struct AppView: View {
 
 ## Alternative: NavigationSplitView
 
-`NavigationSplitView` can handle sidebar + detail + supplementary columns for you, but is harder to customize in cases like:\n- a dedicated notification column independent of selection,\n- custom sizing, or\n- different toolbar behaviors per column.
+`NavigationSplitView` can handle sidebar + detail + supplementary columns for you, but is harder to customize in cases like:
+- a dedicated notification column independent of selection,
+- custom sizing, or
+- different toolbar behaviors per column.
 
 ```swift
 @MainActor

package/bundled-skills/systematic-debugging/condition-based-waiting-example.ts

@@ -5,154 +5,40 @@
 import type { ThreadManager } from '~/threads/thread-manager';
 import type { LaceEvent, LaceEventType } from '~/threads/types';
 
-/**
- * Wait for a specific event type to appear in thread
- *
- * @param threadManager - The thread manager to query
- * @param threadId - Thread to check for events
- * @param eventType - Type of event to wait for
- * @param timeoutMs - Maximum time to wait (default 5000ms)
- * @returns Promise resolving to the first matching event
- *
- * Example:
- *   await waitForEvent(threadManager, agentThreadId, 'TOOL_RESULT');
- */
-export function waitForEvent(
-  threadManager: ThreadManager,
-  threadId: string,
-  eventType: LaceEventType,
-  timeoutMs = 5000
-): Promise<LaceEvent> {
-  return new Promise((resolve, reject) => {
-    const startTime = Date.now();
-
-    const check = () => {
-      const events = threadManager.getEvents(threadId);
-      const event = events.find((e) => e.type === eventType);
-
-      if (event) {
-        resolve(event);
-      } else if (Date.now() - startTime > timeoutMs) {
-        reject(new Error(`Timeout waiting for ${eventType} event after ${timeoutMs}ms`));
-      } else {
-        setTimeout(check, 10); // Poll every 10ms for efficiency
-      }
-    };
-
-    check();
-  });
+// Requires the source project's Lace interfaces. Polling reads must be synchronous.
+// Bounds cannot interrupt a blocking getter; rejected getters stop without another timer.
+async function poll<T>(read: () => T | undefined, description: string, timeoutMs: number): Promise<T> {
+  if (!Number.isFinite(timeoutMs) || timeoutMs < 0) throw new Error('Invalid timeout');
+  const deadline = performance.now() + timeoutMs;
+  while (true) {
+    const value = read();
+    if (value !== undefined) return value;
+    if (performance.now() >= deadline) throw new Error(`Timeout waiting for ${description}`);
+    await new Promise<void>(resolve => setTimeout(resolve, 10));
+  }
 }
 
-/**
- * Wait for a specific number of events of a given type
- *
- * @param threadManager - The thread manager to query
- * @param threadId - Thread to check for events
- * @param eventType - Type of event to wait for
- * @param count - Number of events to wait for
- * @param timeoutMs - Maximum time to wait (default 5000ms)
- * @returns Promise resolving to all matching events once count is reached
- *
- * Example:
- *   // Wait for 2 AGENT_MESSAGE events (initial response + continuation)
- *   await waitForEventCount(threadManager, agentThreadId, 'AGENT_MESSAGE', 2);
- */
-export function waitForEventCount(
-  threadManager: ThreadManager,
-  threadId: string,
-  eventType: LaceEventType,
-  count: number,
-  timeoutMs = 5000
-): Promise<LaceEvent[]> {
-  return new Promise((resolve, reject) => {
-    const startTime = Date.now();
-
-    const check = () => {
-      const events = threadManager.getEvents(threadId);
-      const matchingEvents = events.filter((e) => e.type === eventType);
-
-      if (matchingEvents.length >= count) {
-        resolve(matchingEvents);
-      } else if (Date.now() - startTime > timeoutMs) {
-        reject(
-          new Error(
-            `Timeout waiting for ${count} ${eventType} events after ${timeoutMs}ms (got ${matchingEvents.length})`
-          )
-        );
-      } else {
-        setTimeout(check, 10);
-      }
-    };
-
-    check();
-  });
+export function waitForEvent(manager: ThreadManager, threadId: string,
+  eventType: LaceEventType, timeoutMs = 5000): Promise<LaceEvent> {
+  return poll(() => manager.getEvents(threadId).find(event => event.type === eventType),
+    eventType, timeoutMs);
 }
 
-/**
- * Wait for an event matching a custom predicate
- * Useful when you need to check event data, not just type
- *
- * @param threadManager - The thread manager to query
- * @param threadId - Thread to check for events
- * @param predicate - Function that returns true when event matches
- * @param description - Human-readable description for error messages
- * @param timeoutMs - Maximum time to wait (default 5000ms)
- * @returns Promise resolving to the first matching event
- *
- * Example:
- *   // Wait for TOOL_RESULT with specific ID
- *   await waitForEventMatch(
- *     threadManager,
- *     agentThreadId,
- *     (e) => e.type === 'TOOL_RESULT' && e.data.id === 'call_123',
- *     'TOOL_RESULT with id=call_123'
- *   );
- */
-export function waitForEventMatch(
-  threadManager: ThreadManager,
-  threadId: string,
-  predicate: (event: LaceEvent) => boolean,
-  description: string,
-  timeoutMs = 5000
-): Promise<LaceEvent> {
-  return new Promise((resolve, reject) => {
-    const startTime = Date.now();
-
-    const check = () => {
-      const events = threadManager.getEvents(threadId);
-      const event = events.find(predicate);
-
-      if (event) {
-        resolve(event);
-      } else if (Date.now() - startTime > timeoutMs) {
-        reject(new Error(`Timeout waiting for ${description} after ${timeoutMs}ms`));
-      } else {
-        setTimeout(check, 10);
-      }
-    };
+export function waitForEventCount(manager: ThreadManager, threadId: string,
+  eventType: LaceEventType, count: number, timeoutMs = 5000): Promise<LaceEvent[]> {
+  if (!Number.isInteger(count) || count < 1) return Promise.reject(new Error('Invalid count'));
+  return poll(() => {
+    const events = manager.getEvents(threadId).filter(event => event.type === eventType);
+    return events.length >= count ? events : undefined;
+  }, `${count} ${eventType} events`, timeoutMs);
+}
 
-    check();
-  });
+export function waitForEventMatch(manager: ThreadManager, threadId: string,
+  predicate: (event: LaceEvent) => boolean, description: string,
+  timeoutMs = 5000): Promise<LaceEvent> {
+  return poll(() => manager.getEvents(threadId).find(predicate), description, timeoutMs);
 }
 
-// Usage example from actual debugging session:
-//
-// BEFORE (flaky):
-// ---------------
-// const messagePromise = agent.sendMessage('Execute tools');
-// await new Promise(r => setTimeout(r, 300)); // Hope tools start in 300ms
-// agent.abort();
-// await messagePromise;
-// await new Promise(r => setTimeout(r, 50));  // Hope results arrive in 50ms
-// expect(toolResults.length).toBe(2);         // Fails randomly
-//
-// AFTER (reliable):
-// ----------------
-// const messagePromise = agent.sendMessage('Execute tools');
-// await waitForEventCount(threadManager, threadId, 'TOOL_CALL', 2); // Wait for tools to start
-// agent.abort();
-// await messagePromise;
-// await waitForEventCount(threadManager, threadId, 'TOOL_RESULT', 2); // Wait for results
-// expect(toolResults.length).toBe(2); // Always succeeds
-//
-// Result: 60% pass rate → 100%, 40% faster execution
+// Scope observations to the current thread/request and await the actual tool events
+// before cancelling or asserting. Historical source outcomes (15 repaired cases,
+// 60% to 100% observed pass rate) are not a guarantee for other tests.

package/bundled-skills/systematic-debugging/condition-based-waiting.md

@@ -97,7 +97,7 @@ See `condition-based-waiting-example.ts` in this directory for complete implemen
 
 ```typescript
 // Tool ticks every 100ms - need 2 ticks to verify partial output
-await waitForEvent(manager, 'TOOL_STARTED'); // First: wait for condition
+await waitForEvent(manager, threadId, 'TOOL_CALL'); // First: wait for condition
 await new Promise(r => setTimeout(r, 200));   // Then: wait for timed behavior
 // 200ms = 2 ticks at 100ms intervals - documented and justified
 ```

package/bundled-skills/tdd-orchestrator/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 an expert TDD orchestrator specializing in comprehensive test-driven development coordination, modern TDD practices, and multi-agent workflow management.
 

package/bundled-skills/team-composition-analysis/SKILL.md

@@ -5,6 +5,15 @@ risk: none
 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>/references/compensation-benchmarks.md`
+- `<support-root>/references/equity-calculator.md`
+
+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.
+
 
 # Team Composition Analysis
 
@@ -25,7 +34,6 @@ Design optimal team structures, hiring plans, compensation strategies, and equit
 - 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`.
 
 ## Overview
 

package/bundled-skills/technical-tutorials/SKILL.md

@@ -18,7 +18,7 @@ Read [the detailed guide](references/detailed-guide.md) before executing this sk
 
 ## When to Use
 
-Use this skill when you need when the user wants to create step-by-step technical tutorials, quickstarts, or code walkthroughs. Trigger phrases include "tutorial," "quickstart," "getting started guide," "walkthrough," "step by step," "how to guide," "hands-on guide," or "code tutorial.".
+Use this skill when you need to create step-by-step technical tutorials, quickstarts, or code walkthroughs. Trigger phrases include "tutorial," "quickstart," "getting started guide," "walkthrough," "step by step," "how to guide," "hands-on guide," or "code tutorial.".
 
 
 This skill helps you create step-by-step tutorials that actually work. Covers prerequisite handling, progressive complexity, troubleshooting sections, and creating those satisfying "it works!" moments.

package/bundled-skills/temporal-python-pro/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 an expert Temporal workflow developer specializing in Python SDK implementation, durable workflow design, and production-ready distributed systems.
 

package/bundled-skills/temporal-python-testing/SKILL.md

@@ -20,7 +20,6 @@ Comprehensive testing approaches for Temporal workflows using pytest, progressiv
 - 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/terraform-module-library/SKILL.md

@@ -5,6 +5,17 @@ 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>/assets/vpc-module/`
+- `<support-root>/assets/rds-module/`
+- `<support-root>/references/azure-modules.md`
+- `<support-root>/references/gcp-modules.md`
+
+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.
+
 
 # Terraform Module Library
 
@@ -20,7 +31,6 @@ Production-ready Terraform module patterns for AWS, Azure, and GCP infrastructur
 - 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`.
 
 ## Purpose
 

package/bundled-skills/test-automator/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 an expert test automation engineer specializing in AI-powered testing, modern frameworks, and comprehensive quality engineering strategies.
 

package/bundled-skills/testing-patterns/SKILL.md

@@ -159,16 +159,16 @@ describe('ComponentName', () => {
   });
 
   describe('Rendering', () => {
-    it('should render component with default props', () => {});
-    it('should render loading state when loading', () => {});
+    it.todo('should render component with default props');
+    it.todo('should render loading state when loading');
   });
 
   describe('User interactions', () => {
-    it('should call onPress when button is clicked', async () => {});
+    it.todo('should call onPress when button is clicked');
   });
 
   describe('Edge cases', () => {
-    it('should handle empty data gracefully', () => {});
+    it.todo('should handle empty data gracefully');
   });
 });
 ```
@@ -190,7 +190,7 @@ expect(await screen.findByText('Loaded')).toBeTruthy();
 ## User Interaction Patterns
 
 ```typescript
-import { fireEvent, screen } from '@testing-library/react-native';
+import { fireEvent, screen, waitFor } from '@testing-library/react-native';
 
 it('should submit form on button click', async () => {
   const onSubmit = jest.fn();
@@ -261,7 +261,7 @@ npm test ComponentName.test.tsx
 - **systematic-debugging**: Write test that reproduces bug before fixing
 
 ## When to Use
-This skill is applicable to execute the workflow or actions described in the overview.
+Use when writing Jest unit tests, test factories and mocks, or diagnosing a failing test through a red-green-refactor cycle.
 
 ## Limitations
 - Use this skill only when the task clearly matches the scope described above.

package/bundled-skills/trust-calibrator/SKILL.md

@@ -5,12 +5,18 @@ risk: safe
 source: community
 date_added: "2026-04-04"
 ---
-You are a **Social Psychologist specializing in trust formation and credibility research**. Your task is to diagnose the specific trust barriers a target audience holds toward a brand, offer, or category and prescribe the exact signals needed to build credibility.
+Use a marketing planning and audience-research lens. Your task is to diagnose the specific trust barriers a target audience holds toward a brand, offer, or category and prescribe the exact signals needed to build credibility.
 
 ## When to Use
 - Use when messaging needs the right level of certainty, proof, and claim strength for a skeptical audience.
 - Use when overclaiming, underselling, or weak credibility signals are hurting conversion.
 
+## 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/trust-calibrator/SKILL.md). This identifies the contributed instructions, not scientific validation or a new upstream endorsement.
+
 ## CONTEXT GATHERING
 
 Before calibrating trust, establish:
@@ -31,23 +37,23 @@ Trust forms when the audience believes the source can deliver, will act in their
 
 **Step 1 - Identify the trust barrier**
 Name what is missing: competence, intent, proof, familiarity, or legitimacy.
-*Research basis: trust formation is multi-dimensional and category-specific (Rowley et al., 2015).*
+*Planning hypothesis (verify before presenting as research): trust formation is multi-dimensional and category-specific (Rowley et al., 2015).*
 
 **Step 2 - Diagnose the category baseline**
 Determine whether the category is naturally trusted, distrusted, or polarized.
-*Research basis: category skepticism changes how much evidence is required before action (Nagy et al., 2022; Nguyen-Viet & Nguyen, 2024).*
+*Planning hypothesis (verify before presenting as research): category skepticism changes how much evidence is required before action (Nagy et al., 2022; Nguyen-Viet & Nguyen, 2024).*
 
 **Step 3 - Select the trust signal**
 Choose proof, transparency, credentials, endorsements, or process visibility.
-*Research basis: different trust signals solve different credibility gaps (Hovland; Bagozzi et al., 2021).*
+*Planning hypothesis (verify before presenting as research): different trust signals solve different credibility gaps (Hovland; Bagozzi et al., 2021).*
 
 **Step 4 - Sequence the signal**
 Place the signal before the highest-risk decision.
-*Research basis: trust grows when the audience receives the right signal at the right point in the funnel (Rowley et al., 2015).*
+*Planning hypothesis (verify before presenting as research): trust grows when the audience receives the right signal at the right point in the funnel (Rowley et al., 2015).*
 
 **Step 5 - Check for trust repair risk**
 Ensure the signal cannot be interpreted as overclaiming or manipulation.
-*Research basis: skepticism and backlash intensify when messages feel defensive or exaggerated (Nguyen-Viet & Nguyen, 2024).*
+*Planning hypothesis (verify before presenting as research): skepticism and backlash intensify when messages feel defensive or exaggerated (Nguyen-Viet & Nguyen, 2024).*
 
 ## DECISION MATRIX
 
@@ -95,7 +101,7 @@ The line between persuasion and manipulation is giving a person the signals they
 
 ## 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`
 
@@ -120,6 +126,8 @@ Before finalizing output, the agent asks:
 
 > Calibrate the certainty, proof, and claim strength in this message for a skeptical audience.
 
+**Illustrative output:** Map a reliability concern to the available incident history and recovery procedure; disclose the observation period and avoid an uptime percentage without a measured denominator.
+
 ## 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/tune-monitor/SKILL.md

@@ -9,6 +9,9 @@ date_added: 2026-07-01
 license: Apache-2.0
 license_source: https://github.com/monte-carlo-data/mc-agent-toolkit/blob/main/LICENSE
 ---
+## 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.
 
 # Tune Monitor: Noise Reduction Analysis
 ## When to Use