working-on

Included with Lifetime

$97 forever

Create or update a CLAUDE.md project inventory for the current directory. Works at any level of the code directory hierarchy.

General

What this skill does

# Project Inventory

Create or update a `CLAUDE.md` file in the current working directory that describes the projects found there.
This gives future Claude Code sessions immediate context about what lives in this directory.

## Behaviour by directory level

### Code root (e.g. `~/code/`)

List the org folders with a one-line description of each.
Point to each org's `CLAUDE.md` for details.
Include any top-level config (common tasks, cross-project work patterns).

### Org folder (e.g. `~/code/epinowcast/`)

List all repos in this org with type and description.
Detect type from files present:
- `DESCRIPTION` → R package
- `Project.toml` → Julia package
- `.tex` or `.qmd` manuscript files → paper
- `submission/` or `application/` dir → grant
- `_quarto.yml` without package files → website or slides
- Otherwise infer from contents

Get descriptions from `DESCRIPTION` Title field, `Project.toml` name, or first meaningful line of `README.md`.

### Individual repo

If run inside a repo, defer to `/init` behaviour (document build commands, architecture, etc.).
Do not duplicate what this skill does.

## When the CLAUDE.md already exists

If the argument is "update" or the file already exists:
1. Scan the directory for current subdirectories
2. Compare with the existing inventory
3. Report what changed (new repos, removed repos, description updates)
4. Update only the inventory section, preserving any other content the user has added

## When no CLAUDE.md exists

Ask the user:
1. What is this directory? (org folder, project collection, something else)
2. Are the subdirectories organised by any pattern?
3. What types of projects are here?

Then scan and generate the inventory.

## Output format

Use the same structure as existing org-level CLAUDE.md files.
Keep it concise: org name, one-line summary, then a table of repos.

## Auto-Exit When Standalone

**IMPORTANT**: If this command is being run as a standalone request, automatically exit after completing all phases successfully.

Files: 1

Size: 2.2 KB

Complexity: 10/100

Category: General

Source: https://github.com/seabbs/skills/tree/main/plugins/productivity/skills/working-on

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