evidence-indexing

Included with Lifetime

$97 forever

Maintain README.md (purpose) and INDEX.md (artifact enumeration) in every evidence directory. Refuse to leave any evidence dir un-indexed at gate completion.

General

What this skill does


# evidence-indexing

Every evidence directory must be navigable. This skill enforces that.

## Behavior contract

After any phase completes (and after every gate):

1. For each subdirectory under `e2e-evidence/<run-id>/`:
   - If `README.md` missing → generate: 1-paragraph purpose statement explaining what this directory contains.
   - If `INDEX.md` missing → generate: enumerated table of every artifact (path, byte count, what it represents).
2. If directory has > 10 files: split INDEX.md into sections by step/journey/role.
3. Verify every artifact in INDEX.md actually exists on disk (no phantom citations).

## INDEX.md structure

```markdown
# Evidence Index — <phase or journey name>

**Run:** <run-id>
**Phase:** <phase number + name>
**Generated:** <ISO-8601>

## Artifacts

| File | Size | Type | What it shows |
|---|---|---|---|
| step-01-login-loaded.png | 24kb | screenshot | /login renders successfully |
| step-02-submit-pressed.png | 28kb | screenshot | Submit button click registered |
| step-03-dashboard.json | 1.2kb | API response | Dashboard payload after auth |
| ... | ... | ... | ... |
```

## When to use

- After every phase artifact lands in `e2e-evidence/`
- Before invoking any gate (`completion-gate`, `oracle-review`)
- As a periodic maintenance pass

## When NOT to use

- Directories not under `e2e-evidence/` (logs/, reports/, plans/ have their own conventions)

## Iron rules

- **Refuse to leave any evidence dir un-indexed at gate-completion time.**
- **Never invent files.** Every INDEX.md entry must exist on disk.
- **Never delete an evidence file** to "clean up" the index — captured = immutable.

Files: 1

Size: 1.9 KB

Complexity: 10/100

Category: General

Source: https://github.com/krzemienski/shannon-framework/tree/main/modules/completion/skills/evidence-indexing

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts