Stats
Actions
Tags
From quant-llm-skills
Use when aggregating beneficial-ownership filings (Schedule 13D, 13G, amendments) or insider transaction filings (Form 3, 4, 5, 144) to compute total insider holdings or insider activity. Defines the joint-filer, group, and shared-voting-power deduplication rules so that a single position is not double-counted across N filers.
How this skill is triggered — by the user, by Claude, or both
Slash command
/quant-llm-skills:insider-dedupThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The default join of "all insider filings → sum of shares" overcounts
The default join of "all insider filings → sum of shares" overcounts positions, often by 2–10x. The reason: SEC rules require multiple related parties (funds, GPs, advisers, family members, trustees, beneficial owners) to each file a 13D/G or Form 4 covering the SAME underlying shares. Naive summation = fictional ownership numbers.
Beneficial ownership is per-share, not per-filer. If three filers report the same 1,000,000 shares because of a shared-voting-power arrangement, the position is 1,000,000 — not 3,000,000.
The reverse is also true: separate parties may individually file 13D/G for distinct positions. You cannot blindly dedup either; you must read the filings.
A typical activist or institutional 13D group:
Filer 1: The fund (Limited Partnership) — reports 1,000,000 sh
Filer 2: The fund's GP (LLC) — reports 1,000,000 sh
Filer 3: The investment manager / adviser — reports 1,000,000 sh
Filer 4: The CEO / managing member (individual) — reports 1,000,000 sh
All four are filing the same SC 13D as a "group". The cover page of each filing reports the same 1,000,000 shares. Naive sum = 4,000,000; true position = 1,000,000.
When an executive transacts through a trust, an LLC, or a family office, multiple Form 4s may be filed for the same transaction:
The transaction S 50,000 @ $10.00 may appear three times for what
is one sale.
Vanguard, BlackRock, and similar issuers file at the asset-manager level with multiple subsidiary entities. Same beneficial position, multiple cover-page disclosures.
Group identity (Item 2). If multiple 13D/G filings list each other as members of the same Section 13(d) group, treat as ONE position. The cover-page share counts of all members are typically identical (or report sub-allocations summing to the group total).
Shared voting / dispositive power. Schedule 13D Item 5 reports "sole" vs "shared" voting and dispositive power. When two filers each report shared power over the same N shares, those N shares appear once, not twice.
Family attribution. Spouse and dependent-children holdings are reported on the executive's Form 4 with footnotes ("shares held by spouse"). If the spouse files separately, dedup against the executive's filing.
Entity layering. Fund → GP → Adviser → Managing Member is one chain. If the chain reports the SAME shares at each level, dedup to the lowest economic owner (typically the fund / LP).
Joint reporters on a single 13D/G. The cover page lists all joint filers; the agreement under Item 6 typically attaches the joint filing agreement. Treat as one filing for sum purposes.
These look similar but represent distinct positions:
atm-detection and recent 424B activity:
total beneficial holdings + ATM-issued shares + outstanding shares
should reconcile to total shares outstanding within ~5%.
Larger gaps = missed dilution event or missed group.sec-filing-types.)This is not a beneficial-ownership extractor. It defines the
deduplication semantics so a downstream summation produces a real
number rather than a multi-counted fiction. Combine with
sec-filing-types for form context and lookahead-safety for
historical reconstruction of holdings.
npx claudepluginhub jefrnc/quant-llm-skills --plugin quant-llm-skillsSearches MemPalace before answering questions about past work, people, projects, or prior decisions. Returns verbatim stored content instead of guessing from model memory.
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Implements vector databases with Pinecone, Weaviate, Qdrant, Milvus, pgvector for semantic search, RAG, recommendations, and similarity systems. Optimizes embeddings, indexing, and hybrid search.