status-things
Show .things/ status - registered collections, item counts, git state, and optional tag aggregation. Use when user says 'things status', 'what do I have', 'show me my things'.
What this skill does
<purpose>
Show an overview of everything stored in `.things/`.
</purpose>
<steps>
<step id="load-config" number="1">
<description>Load Configuration</description>
<load-config>
Resolve the user's home directory (run `echo $HOME` via Bash). Use this absolute path for all file operations below -- never pass `~` to the Read tool.
1. Read `<home>/.things/config.json`
2. Read `<home>/.things/registry.json`
<if condition="config-missing">Tell the user to run `/things:setup-things`.</if>
</load-config>
</step>
<step id="gather-stats" number="2">
<description>Gather Collection Stats</description>
For each registered collection in `registry.json`:
<if condition="directory-per-item">
- Count subdirectories in `<home>/.things/<collection-path>/` (exclude files, only count directories)
- Get the most recent modification time across all files
</if>
<if condition="flat-files">
- Count files matching `file_pattern` in `<home>/.things/<collection-path>/`
- Get the most recent modification time
</if>
<if condition="master-index-exists">
- Read the master index file and use its `total_items` count as a cross-check
</if>
</step>
<step id="gather-git-status" number="3">
<description>Gather Git Status</description>
```bash
git -C <home>/.things status --short 2>/dev/null
```
```bash
git -C <home>/.things log --oneline -1 2>/dev/null
```
<extract>Determine: clean/dirty, last commit date, ahead/behind remote (if configured).</extract>
</step>
<step id="quick-validation" number="4">
<description>Check for Validation Issues</description>
Do a quick structural check for each collection:
<check name="directory-exists">Does the collection directory exist?</check>
<check name="master-index-valid">If `master_index` is specified, does the file exist and parse as valid JSON?</check>
<check name="no-orphans">Any obvious orphaned directories (directories in `.things/` that aren't in the registry and aren't `shared/` or `.git/`)?</check>
</step>
<step id="tag-aggregation" number="5">
<description>Optional Tag Aggregation (--tags)</description>
<if condition="tags-flag">
Read the central tag index:
<phase name="read-central-index" number="1">
Read `<home>/.things/tags/index.json`. If it doesn't exist, fall back to scanning `*/tags.json` files.
</phase>
<phase name="present-table" number="2">
Present as a table: tag name, total count, last used, plugins/collections that use it. Sort by total count descending.
</phase>
</if>
</step>
<step id="present-output" number="6">
<description>Present Output</description>
<template name="status-healthy">
```
.things status:
Location: <home>/.things
Git: <clean|dirty>, <last commit info>, <remote status>
Collections:
shared/people <n> items last modified: <relative time>
shared/roles <n> items last modified: <relative time>
shared/companies <n> items last modified: <relative time>
think-like/profiles <n> items last modified: <relative time>
...
Health: all collections valid
```
</template>
<template name="status-with-issues">
```
Health:
! think-like/profiles/linus-torvalds: missing index.json
! orphaned directory: old-data/ (not in registry)
```
</template>
</step>
</steps>
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce 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).
relationship-science-coach
IncludedUse 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.
building-sf-integrations
IncludedSalesforce 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).
venue-templates
IncludedAccess 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.
let-fate-decide
IncludedDraws 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.
net-ops
IncludedCross-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.