Loading...
Loading...
Found 10,876 Skills
Analyze private placement and exempt offering compliance under Regulation D, the Investment Company Act fund exclusions, and FINRA private placement rules. Owns the accredited investor definition (Rule 501(a)), the '506(b) vs 506(c)' distinction, 'general solicitation' analysis, 'Form D' filing mechanics, the 'qualified purchaser' standard for 3(c)(7) funds, bad-actor disqualification, integration, and Rule 144 resale restrictions. Use when the user asks 'can my client invest in this private fund', whether an investor is an 'accredited investor' or qualified purchaser, how to verify accredited status in a 'Reg D offering', 506(c) verification steps, FINRA 5122/5123 filing obligations, or the Reg BI/fiduciary overlay when recommending private placements. Also trigger on 'exempt offering', 'private fund exemption', '3(c)(1) vs 3(c)(7)', or 'restricted securities holding period'.
Design oRPC v2 APIs contract-first, defining the API shape with oc from `@orpc/contract`, implementing it with implement from `@orpc/server`, and consuming the contract from typesafe clients. Use when a project depends on `@orpc/contract`, when defining a contract with oc, implementing a contract with implement, sharing an API contract between server and client packages, generating a contract from an existing OpenAPI spec, or publishing a typed API client to npm. Biases toward retrieval from the oRPC docs over pre-trained knowledge. For core builder, serving, and client work without a contract, use the orpc skill; for REST/OpenAPI exposure, spec generation, and OpenAPILink details, use the orpc-openapi skill.
Estate and gifting architecture for wealth management: the unified estate/gift/GST framework, lifetime exemption vs annual exclusion, basis step-up vs carryover, trust taxonomy, and beneficiary planning. Use when the user asks about the 'estate tax exemption', 'annual gift exclusion', 'step-up in basis', a 'revocable trust' or 'irrevocable trust', 'gifting to my kids', '529 superfunding', or the 'portability election'. Also trigger on questions about gift-splitting, Form 706 or Form 709, DSUE, ILITs, GRATs, SLATs, IDGTs, charitable remainder trusts, state estate or inheritance taxes, the SECURE Act 10-year rule for inherited IRAs, whether to gift appreciated stock now or leave it at death, or how to fund estate taxes for an illiquid estate. For income-tax angles of charitable giving (QCDs, donating appreciated securities, DAF bunching), see the tax-efficiency skill.
Socket.IO v4.x client patterns, connection lifecycle, reconnection, authentication, rooms, namespaces, acknowledgments, binary data, TypeScript integration
Enrich and search People Data Labs (PDL) Person and Company data, writing results to .xlsx. Five operations: enrich named PEOPLE into a profile, employment history and LinkedIn URL; IDENTIFY an ambiguous person as several scored candidates; SEARCH people by criteria (company, title, location); enrich COMPANIES into firmographics (industry, size, employees, HQ, founded, LinkedIn); and SEARCH companies by criteria. Use when the user has a list of names or companies and wants their job, employer, work history, LinkedIn URLs or company profiles looked up, or wants to find people or companies matching criteria. Trigger on phrases like "enrich these contacts", "find their LinkedIn", "look up these people", "who works at X", "find directors at Y", "enrich these companies", or "get firmographics for". Do not scrape LinkedIn directly — this uses a licensed data aggregator (PDL) instead, for legal and reliability reasons.
Upstash serverless Redis -- REST-based client, auto-serialization, pipelines, rate limiting, QStash, edge compatibility, global replication
Audit applications and infrastructure handling Protected Health Information against HIPAA — Security Rule (administrative, physical, technical safeguards), Privacy Rule, Breach Notification Rule, plus HITECH. Covers ePHI scoping, the 18 HIPAA identifiers, Business Associate Agreement (BAA) chain-of-liability, minimum-necessary standard, and breach notification timing. Use when the user mentions 'HIPAA,' 'HIPAA Security Rule,' 'HIPAA Privacy Rule,' 'PHI,' 'ePHI,' 'protected health information,' 'BAA,' 'business associate agreement,' 'covered entity,' 'business associate,' 'minimum necessary,' 'HIPAA breach,' 'HITECH,' 'healthcare compliance,' 'medical data,' 'patient data,' or audits any system that creates, receives, maintains, or transmits PHI.
Plan Requirements - generates a structured requirements document, asking clarifying questions about ambiguities before proceeding
Checks that test method and function names read as complete sentences describing behavior. Flags cryptic names like test1, testFoo, or abbreviated names that do not describe what is being tested. Designed to run on every PR. Do NOT use for test coverage, test structure, or non-test code.
Venue-calibrated peer-review simulation. Use when a researcher says "simulate reviewers", "mock review", "review my paper like a NeurIPS reviewer", "what would Reviewer 2 say", "red-team my paper", "find weaknesses before I submit", "peer review my paper", "strengths and weaknesses / pros and cons of my paper", "what to focus on", or wants a rubric score / borderline-reject risk estimate for a conference or journal (NeurIPS, ICML, ICLR, CVPR, KDD, SIGMOD, CHI, VLDB, LNCS, TKDE, TODS...). Builds a reviewer panel calibrated to the venue family and track (harsh NeurIPS main-track skeptics vs lenient demo-track judges), scores novelty/soundness/reproducibility/clarity on the venue's scale, hunts weaknesses grounded in quoted paper text, aggregates scores into a decision-risk band with borderline-reject flags, and outputs a prioritized fix list. Advisory only; improves the paper, never predicts the outcome, re-verifies facts against the live CFP, fabricates no citations or reviewers, and submits nothing.
Deep anonymization sweep for double-blind paper submissions, plus clean de-anonymization for camera-ready. Use when a researcher says "anonymize my paper", "double-blind check", "blind this submission", "remove author names", "did I leak my identity" — or, after acceptance, "de-anonymize" / "restore authors for camera-ready". Sweeps the whole leak surface, \author/\affiliation/\email/\orcid/\thanks, acknowledgments and grant numbers, hyperref pdfauthor and compiled-PDF metadata, first-person self-citations (rewritten to third person), GitHub/dataset/homepage links vs anonymized mirrors, LaTeX comments, .bib annotations, home-directory paths, and supplementary material (.git dirs, notebooks, LICENSE/AUTHORS files). Bundles a stdlib-only scanner (scan_anonymization.py, check ids shared with preflight-check) and a reversible-edit workflow (toggle + manifest) so every change is cleanly undone at camera-ready. Advisory only; never submits anything.
Drafts or rewrites a Related Work / prior work section positioned against actually-retrieved papers — derives the REQUIRED clusters from the paper's own claimed scope (not just whatever was retrieved), clusters prior work into themes, articulates the delta (what this paper adds) per cluster, enforces a per-cluster citation floor and routes empty expected clusters back to find-papers, follows the target community's placement and citation conventions (numeric ACM/IEEE vs natbib author-year, single- vs double-blind self-citation, where the section sits at NeurIPS/CHI/SIGMOD-style venues), and admits only verified citations. Use when the user says "related work", "prior work", "position my paper against the literature", "how do we differ from X", "reviewers said related work is thin/missing/a laundry list", or asks to add citations to a draft. Works from papers found via find-papers and/or an existing .bib — it never invents references.