Kinds / Canonical
agent-skills/
Executable know-how in the Agent Skills shape: a SKILL.md an agent can load and follow.
147 files · 6 projects
lossless-monorepo121
Implementation Notes for Deck Iteration Workflow
Phase Implementation Template
Slide Variant Template
example-vc
lossless-monorepo/agent-skills/astro-knots/references/ecosystem
lossless-monorepo/agent-skills/astro-knots/references/philosophy
lossless-monorepo/agent-skills/astro-knots/references/playbooks/github-pages-deploy
lossless-monorepo/agent-skills/astro-knots/references/playbooks/llms-txt-and-md-sidecars
lossless-monorepo/agent-skills/astro-knots/references/playbooks/new-site-setup
lossless-monorepo/agent-skills/astro-knots/references/playbooks/opengraph-system
lossless-monorepo/agent-skills/astro-knots/references/tech-stack
lossless-monorepo/agent-skills/astro-knots/skill
The Lossless Group's Astro Knots conventions — vision, tech hierarchy, approved frameworks, and hard prohibitions for the family of ~10+ Astro sites and the Lossless Flavored Markdown ecosystem. Use whenever working on an Astro project in the lossless-monorepo (or any sibling repo), scaffolding new sites, choosing dependencies, building components, integrating LFM, or when the user mentions "Astro Knots", "LFM", "Lossless Flavored Markdown", or "pseudomonorepo". Hard prohibitions on React, JSX, Angular, and unnecessary dependencies.
lossless-monorepo/agent-skills/augment-speakers-panelists/skill
lossless-monorepo/agent-skills/authoring
lossless-monorepo/agent-skills/candidates
Running backlog of potential future skills for the Lossless Group. Reference only - not a loadable skill.
lossless-monorepo/agent-skills/changelog-conventions/references/changelog-first-development
lossless-monorepo/agent-skills/changelog-conventions/references/filename-conventions
lossless-monorepo/agent-skills/changelog-conventions/references/frontmatter-spec
lossless-monorepo/agent-skills/changelog-conventions/references/voice-and-shape
lossless-monorepo/agent-skills/changelog-conventions/references/what-counts
lossless-monorepo/agent-skills/changelog-conventions/skill
How The Lossless Group writes and structures changelog/ entries across all repos (projects, true monorepos, pseudomonorepos). Use whenever shipping or pushing a coherent chunk of work, when scaffolding a new repo's changelog/ directory, when authoring a product release message, when the user says "log this", "write a changelog", or "ship note", or when reviewing a changelog/ file. Also fires when the user drops screenshots for an entry or the work being logged is visual — composes with prep-images-for-embed so images get CDN-hosted with real alt text without the user naming both skills. Encodes the strict frontmatter (publish, lede, ISO dates), filename pattern, "it exists" priority, the never-use-relative-image-paths rule (entries get rolled up into parent sites, so relative paths break), and the show-don't-enforce ethos.
Title in title case
One-sentence hook that makes the reader want to keep reading. Specific, not generic.
PRODUCT vX.Y.Z — Release Title
What this release does in one attention-grabbing sentence
lossless-monorepo/agent-skills/claude
lossless-monorepo/agent-skills/cloudflare-artifacts-interface/references/api-map
lossless-monorepo/agent-skills/cloudflare-artifacts-interface/skill
Operate Cloudflare Artifacts, Cloudflare's Git-compatible versioned storage for agents, from an agent session through the REST API, Wrangler, a Worker binding, or plain git. Use when someone wants a repo per agent, session, task, or user; wants to create, fork, import, list, read, or delete Artifacts repos or namespaces; needs a read or write token for git clone/push; wants to hand a workspace to another agent or reviewer; wants to read files from a repo without cloning; wants to clean up stale repos or check cost; or mentions "Artifacts", "artifacts.cloudflare.net", "art_v1_" tokens, "env.ARTIFACTS", or "wrangler artifacts". Supplies the three-credential model (API token for control, repo token for git, binding inside a Worker), safety tiers that put deletes, namespace jurisdictions, and long-lived write tokens behind a confirmation, token hygiene (never persist a token in .git/config), naming that avoids collisions, and the billing and size limits that make bulk creation a decision.
lossless-monorepo/agent-skills/context-vigilance/references/developing-a-spec
lossless-monorepo/agent-skills/context-vigilance/references/doc-type-guide
lossless-monorepo/agent-skills/context-vigilance/references/frontmatter-spec
lossless-monorepo/agent-skills/context-vigilance/references/philosophy
lossless-monorepo/agent-skills/context-vigilance/references/status-discipline
lossless-monorepo/agent-skills/context-vigilance/references/versioning
lossless-monorepo/agent-skills/context-vigilance/skill
Lossless Group's framework for managing context-v/ directories in any project. Use whenever creating, updating, or organizing files in any context-v/ folder (specs, plans, prompts, blueprints, reminders, agent-skills, explorations, issues — plus the universal extra/ and sitemap/, and the experimental loops/, handoffs/, decisions/, habits/, contracts/, docs/, and briefs/), or when the user asks about context engineering, AI co-development workflow, or the "context-v" convention. Enforces directory roles, three- or four-part versioning, YAML frontmatter standard, wikilink cross-references, and the prep/reflective/journey cognitive modes.
lossless-monorepo/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/15f60674bf070c2f
lossless-monorepo/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/25f0de5c86750b7e
lossless-monorepo/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/38b666f4189ea895
lossless-monorepo/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/40f956e078923920
lossless-monorepo/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/6c019018c31645a0
lossless-monorepo/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/76082587295e27c1
lossless-monorepo/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/795e94c1c0c2cc5a
lossless-monorepo/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/88d0ded5729b5482
lossless-monorepo/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/a2c70d73d66ca2cc
lossless-monorepo/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/b1a9507c907e5868
lossless-monorepo/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/ba5de0bff3839e6d
lossless-monorepo/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/c4c0fa68d0682b61
lossless-monorepo/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/e552f2b87caf8f63
lossless-monorepo/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/f57055e06641af3c
lossless-monorepo/agent-skills/crawl-fetch-ingest/cache/calm-storm-ventures/jina/fa616c0558874713
lossless-monorepo/agent-skills/crawl-fetch-ingest/future-work
Known v1 limitations and planned extensions for the crawl-fetch-ingest skill
lossless-monorepo/agent-skills/crawl-fetch-ingest/routines/investor-credibility-ingest
Sub-workflow of crawl-fetch-ingest. Company-anchored expansion through a list of backer firms — for each firm, ingest its team + its portfolio companies (with brand assets), so the operating company's deck/site can render credibility cards for readers starting from near-zero context. Stops at the firms' portfolio companies; does NOT descend to portco CEOs.
lossless-monorepo/agent-skills/crawl-fetch-ingest/routines/triage-brand-assets
Sub-workflow of crawl-fetch-ingest. Walks every brand asset that was fetched for a firm through a quality review, classifying each into good-to-go / not-urgent-passable / urgent-rework / deferred-for-now so the user can prioritize manual cleanup.
lossless-monorepo/agent-skills/crawl-fetch-ingest/schema/company
Canonical frontmatter shape for portfolio/{slug}.md (CP3 output — portfolio companies)
lossless-monorepo/agent-skills/crawl-fetch-ingest/schema/firm
Canonical frontmatter shape for firm.md (the firm-level metadata file)
lossless-monorepo/agent-skills/crawl-fetch-ingest/schema/person
Canonical frontmatter shape for team/{slug}.md and portfolio/{slug}-ceo.md (CP1, CP2, CP4 outputs)
lossless-monorepo/agent-skills/crawl-fetch-ingest/setup
One-time setup for the crawl-fetch-ingest skill — secrets file, MCP servers, helper scripts
lossless-monorepo/agent-skills/crawl-fetch-ingest/skill
The Lossless Group's workflow for filling in team and portfolio metadata for VC firms and the operating companies they back — crawl a firm's site, fetch structured data + brand assets for people and companies referenced in a deck/PDF, ingest as canonical .md files with YAML frontmatter. Supports two starting anchors — firm-anchored (one VC → its team → its portfolio → portco CEOs) and company-anchored (one operating company → its backer firms → each backer's team + portfolio, stopping there) — for credibility-card use. Use whenever you need to recreate VC team pages, advisor sections, or portfolio company sections in HTML/Tailwind/Reveal slideshows; whenever the input is "here's a PDF and/or a firm URL, fill in the people and companies"; whenever you need headshots, LinkedIn URLs, company logos (SVG preferred), CEO metadata; whenever you need to "ingest our backers" or "make these investors legible to readers"; whenever the user mentions "fill out the team", "find the headshots", "credibility ingest", "we need their portfolio companies", or names this skill directly. Encodes the four-checkpoint cascade (VC team → advisors → portfolio companies → portco CEOs), the cross-tool fallback pattern (Firecrawl → Tavily → OpenGraph.io), the global-cache-per-firm convention so the same firm's data is reused across multiple decks/memos, and the loose canonical schema that sites converge toward on refactor (not enforced on ingest).
lossless-monorepo/agent-skills/create-contact-list-from-image-or-spreadsheet/skill
Turn a roster — a phone photo of a printed sign-in sheet, a screenshot, a PDF, a CSV, or a spreadsheet — into a verified contact CSV, importable vCards for iPhone and Android, and a comma-separated E.164 number list ready to paste into Messages. Use whenever the user drops a photo of a list of people and wants it "parsed", whenever they say "make contact cards", "generate vCards", "get these into my phone", "make a WhatsApp group from this", "I need everyone's numbers", "turn this roster into a CSV"; whenever an event/cohort/conference/class/retreat roster needs to become a group chat; whenever numbers need normalizing to E.164. Encodes the band-crop transcription discipline that makes photo OCR trustworthy (EXIF auto-orient, overlapping full-res bands — never read digits off a downscaled overview), the E.164-always rule, the name-prefix trick that survives WhatsApp's names-only picker search, the one-vCard-format-covers-both-platforms fact, the flag-don't-fix verification pass, and the hard reality that WhatsApp has no bulk-add — invite links are the fallback.
lossless-monorepo/agent-skills/decile-hub-connector/references/endpoint-inventory
lossless-monorepo/agent-skills/decile-hub-connector/skill
How augment-it (and any Lossless VC-client workspace) talks to the Decile Hub API — the first per-client custom connector. Use whenever pulling from or pushing to Decile Hub (people, organizations, pipeline prospects, deal shares, deal memos, funds/entities, portfolio companies, capital accounts, notes, tasks, files, events), wiring the Decile connector for a new client, building or maintaining the decile-mcp server, mapping Decile records into the SurrealDB canonical layer, or when the user mentions "Decile", "DecileHub", "DECILE_API_URL", "DECILE_HUB_API_KEY", or a per-client CRM connector. Encodes the auth (raw API token in the Authorization header — no Bearer), the per-tenant subdomain base URL, the THREE distinct pagination patterns, the upsert-by-natural-key write semantics, the custom_data_points / variables (merge-tag) system, and the mapping of Decile people/organizations onto the SurrealDB canonical persons/organizations tables. The authoritative contract is the on-disk OpenAPI spec; this skill is the operating guide on top of it.
lossless-monorepo/agent-skills/deck-iteration-workflow/skill
The Lossless Group's workflow for developing slides-only Astro sites for fundraise processes, aligned with the calmstorm-decks project patterns and the iterative approach from the "Develop a Slides-only Astro Site for a Fundraise Process" specification. Use when creating or modifying slide decks, managing slide variants, or implementing the structured iteration workflow for fundraise material development.
lossless-monorepo/agent-skills/event-prep/references/templates
lossless-monorepo/agent-skills/event-prep/skill
The Lossless Group's method for preparing for, working, and recapping a conference or summit — the "company brain" event workflow across markdown notes in the content repo and the operator's Twenty CRM. Use whenever the user shares an event URL and asks who to meet, says "prep me for <event>", "build an event map", "who's going to be at", "rank the speakers", "what sessions should I attend", "log who I met at", "re-sync the event map", or "recap <event>"; whenever a file under content/sources/Events/ or client-content/<client>/Events/ is created or edited; and whenever badge photos, business cards, or an attendee export from an event need to land in the CRM. Encodes the lifecycle (series note → prep map → event → interaction logging → recap re-sync), lens-based routing to the right folder and Twenty instance, the priority and touchpoint keys, the top-conversations table with asks and opening lines, the unverified-marking and sources-footer discipline, and the propose-before-write pattern for CRM records. Composes with lossless-crm-interface-guidelines, which owns every CRM write rule.
lossless-monorepo/agent-skills/expense-report-generation/skill
How to turn raw card and bank statement downloads into a defensible, client-ready expense report. Use whenever the user asks to build an expense report, reconcile AmEx or bank statements, work out "what is this charge for", aggregate reimbursables for a client or trip, split a claim by month, or render an expense PDF; whenever a folder of statement CSVs/PDFs needs to become a submittable document; or whenever the user says "expense report", "reimbursement", "what am I paying for", "which card was that on", "make this a PDF". Encodes the parent-company descriptor trap (Loom bills as ATLASSIAN, Trae as BYTEDANCE), the never-invent-a-product-name rule, the statement-close gap that silently truncates trips, cheap PDF text extraction, and the two-section BASE/EXTENDED structure.
lossless-monorepo/agent-skills/generate-consistent-og-images/skill
How to generate share-imagery (OpenGraph banners, portraits, squares, tall WhatsApp/iMessage cards) for any Lossless site or splash page so the resulting images form a coherent visual family — via two coexisting techniques: Ideogram illustration, or rasterizing the project's own hero/specimen component with macOS's `qlmanage`+`sips` (or a Playwright screenshot for higher fidelity). Use whenever a site, splash, plugin page, or fundraise deck needs an OG image generated or refreshed; whenever the user says "make an og image", "generate a banner", "we need a share image", "regenerate banners across formats", "the unfurl looks stale", "screenshot the hero for the share image", "turn this component into an OG image"; whenever scaffolding a new Astro Knots site that doesn't yet have an `og:image` or a `DESIGN.md`; whenever per-page or per-component custom illustrative imagery is needed even if it deliberately departs from the OG-image canon; whenever an existing OG image (of either technique) might already be live and a decision is needed about replacing vs. keeping it. Encodes the pattern of (1) choose Ideogram illustration vs. hero rasterization per the Strategy Choice section, (2) check / create a DESIGN.md following the Google Stitch open spec, (3) check / add an `imagery:` recipe block to that DESIGN.md, (4) call Ideogram v3 generate with every field locked except `prompt` and `aspect_ratio` (or rasterize the hero via `qlmanage`+`sips`), (5) save with the canonical naming convention, (6) treat WhatsApp + iMessage chat-preview as the primary share surface and other socials as secondary, (7) run the Case Protocol before wiring anything into a live `og:image` tag. The skill never sees an API key in source — `IDEOGRAM_API_KEY` lives in `~/.secrets` and is inherited from the shell, same pattern as the `crawl-fetch-ingest` skill.
lossless-monorepo/agent-skills/gh-cli-projects-tasks-conventions/skill
How The Lossless Group uses the `gh` CLI for GitHub issues and Projects v2 tasks across the pseudomonorepo tree. Use whenever creating, editing, or listing GitHub Project tasks via `gh project item-create`, `gh project item-add`, or `gh project item-edit`; whenever creating repo issues via `gh issue create`; whenever the user mentions "gh project", "create a task", "create an issue", "add to the project", "draft a project item", "ProjectV2", labels, milestones, issue types, or asks to script task/issue creation; whenever an agent is about to author a task body that references one or more `context-v/` files. Encodes the **task-body-is-a-github-link** convention — every task whose work-context lives in a `context-v/` file gets a body whose primary content is a clickable GitHub URL to that file in its own repo (NOT a deep path inside the parent monorepo, because each pseudomonorepo level is its own git repo and the URL must respect that) — and the **prefill-the-sidebar** convention: query the repo/org's actual labels, milestones, assignees, and issue types, infer the best fit, ask the user only when nothing fits logically. Composes with the `pseudomonorepos` skill to identify which repo a local context-v path belongs to and which branch tier (`development` / `main` / `master`) the link should target.
lossless-monorepo/agent-skills/git-conventions/references/body-structure
lossless-monorepo/agent-skills/git-conventions/references/examples
lossless-monorepo/agent-skills/git-conventions/references/header-patterns
lossless-monorepo/agent-skills/git-conventions/skill
The Lossless Group's git commit message conventions — structured headers with action verbs and effort groupings, paragraph-spaced bodies that explain impact before implementation, and "Also included" riders for minor changes. Use when writing commit messages, reviewing commits, or when the user mentions "commit message format", "git conventions", or asks how to structure a commit.
lossless-monorepo/agent-skills/graphify/references/add-watch
lossless-monorepo/agent-skills/graphify/references/exports
lossless-monorepo/agent-skills/graphify/references/extraction-spec
lossless-monorepo/agent-skills/graphify/references/github-and-merge
lossless-monorepo/agent-skills/graphify/references/hooks
lossless-monorepo/agent-skills/graphify/references/query
lossless-monorepo/agent-skills/graphify/references/transcribe
lossless-monorepo/agent-skills/graphify/references/update
lossless-monorepo/agent-skills/graphify/skill
Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.
lossless-monorepo/agent-skills/graphify/vendored
lossless-monorepo/agent-skills/hubspot-interface/references/connector-setup
lossless-monorepo/agent-skills/hubspot-interface/references/tool-map
lossless-monorepo/agent-skills/hubspot-interface/skill
Operate a client's HubSpot CRM from Claude (Desktop, claude.ai, Teams, Claude Code) through HubSpot's remote MCP server at mcp.hubspot.com, via HubSpot's native Claude connector or a custom MCP connector, with the REST API as the operator's escape hatch. Use when someone asks about a contact, company, or deal ("is X in HubSpot?", "what stage is this deal?", "who owns this account?"), wants a call, meeting, or note logged, wants records created, updated, or associated, wants a pipeline roundup, or asks to touch properties, pipelines, segments, campaigns, marketing emails, or website content. Supplies the safety tiers that separate record writes from account-wide schema changes and public publishing, the internal-name-versus-label rule for properties and stages, the dedupe rules (contacts dedupe on email, companies do not dedupe on domain over the API, and there is no merge tool over MCP), and the discipline of reporting only what the records support.
lossless-monorepo/agent-skills/lossless-crm-interface-guidelines/skill
Conventions for reading and writing the operator's Twenty CRM instances (Lossless, Palmer AI, The Water Foundation) via MCP. Use whenever adding or enriching a company, person, deal, thesis, event, or portfolio relationship; when triaging a list or export into the CRM; or when extending the CRM schema. Encodes instance routing, the custom object model (Investment, Deal Source, Deal Prospect, Thesis, Thesis Fit, Events, Interaction), the forced-choice scoring standard, provenance rules, the companion-timeline-row rule that makes custom objects visible on a Person or Company timeline, and known MCP pitfalls.
lossless-monorepo/agent-skills/lossless-flavored-markdown/references/extensibility
lossless-monorepo/agent-skills/lossless-flavored-markdown/references/frontmatter-schema
lossless-monorepo/agent-skills/lossless-flavored-markdown/references/package-and-setup
lossless-monorepo/agent-skills/lossless-flavored-markdown/references/syntax-and-directives
lossless-monorepo/agent-skills/lossless-flavored-markdown/references/triggers-to-component-pipeline
lossless-monorepo/agent-skills/lossless-flavored-markdown/skill
The Lossless Group's extended-markdown flavor — what LFM is, when to use it, how its directives normalize across syntaxes (CommonMark, GFM, Obsidian callouts, remark-directive, Markdoc), how citations and link previews work, and how sites extend it via trigger maps and theme tokens. Use whenever authoring or rendering content in any Astro Knots site, integrating the @lossless-group/lfm package, building or registering custom components for markdown, debugging callouts/embeds/citations, or when the user mentions "LFM", "Lossless Flavored Markdown", "extended markdown", "directive syntax", "wikilink", "trigger map", "callout", or "hex-code citation".
lossless-monorepo/agent-skills/maintain-design-md/skill
How to author and maintain a `DESIGN.md` file at the root of any Lossless project (site, splash page, plugin landing, fundraise deck) following Google Stitch's open spec. Use whenever a project is missing a `DESIGN.md` and an agent needs the project's visual identity in machine-readable form; whenever the user mentions "design tokens", "design system", "DESIGN.md", or "Stitch spec"; whenever theme/CSS-token work changes the runtime values (new CSS custom property in `:root`, renamed token, new mode, new component pattern, refreshed palette, refreshed typography scale) and the documented contract has drifted; whenever a sibling skill (`generate-consistent-og-images`, `theme-system`, `astro-knots`) needs to read locked design values; whenever the user says "the agent doesn't know what color we use" or "let's write down the design system." Encodes (1) the Stitch spec's frontmatter token groups (colors, typography, rounded, spacing, components) and the eight prose sections in canonical order, (2) the maintenance triggers — what kinds of code changes should bounce back into the document, (3) the "runtime CSS is source of truth, DESIGN.md is the contract" discipline, (4) the precedent for off-spec extensions like an `imagery:` block, (5) anti-patterns. The skill never sees an API key or makes network calls — it's a pure-document discipline.
lossless-monorepo/agent-skills/maintain-design-md/templates/design-md-scaffold
★ One paragraph describing the visual identity. Mention the runtime source-of-truth path so future agents know where to read the actual values.
lossless-monorepo/agent-skills/maintain-filemap/skill
Use whenever the directory shape of a Lossless pseudomonorepo (or any child repo) changes — a new top-level directory is added, a submodule is mounted or unmounted, a major subsystem is renamed — or on a weekly cadence, or before any release that would land on GitHub, to regenerate the `FILEMAP.md` at each affected repo's root so collaborators see the current shape without cloning. Triggers when the user mentions "filemap", "tree", "directory layout", "repo overview", "what does this repo even contain", "new collaborator joining"; also when the agent itself proposes adding/removing a top-level dir or a submodule, because that's exactly the moment the discipline matters.
lossless-monorepo/agent-skills/maintain-splash-pages/skill
The Lossless Group's pattern for repo-level splash pages — small Astro sites at <repo>/splash/ that ship to GitHub Pages on push to main, render the repo's changelog/ + context-v/ alongside curated marketing copy, and stay isolated from any package the repo also publishes. Use proactively whenever scaffolding a noteworthy new repo (every "important" repo wants one), when shipping a coherent chunk of work that an external reader would land on, when adding a feature (search, sort, tags row, theme mode) to an existing splash, when converting a legacy apps/<name>/ site to splash/, when troubleshooting a Pages deploy, or when the user mentions "splash", "GitHub Pages", "lossless-group.github.io", "Pagefind on our site", or working under a splash/ directory. Codifies the proven shape across three reference implementations (memopop-site, content-farm/splash, lfm/splash) and the package-isolation discipline that keeps splashes safe to add to repos that also publish to JSR/npm.
lossless-monorepo/agent-skills/obsidian-vault-hygiene/skill
How to promote loose notes in the operator's Obsidian vault (content-md/lossless) into their proper typed folders with standard frontmatter — back up, classify, merge duplicates, verify the URL, OG-fetch, tag, move, and repair wikilinks. Use whenever the user points at a note sitting at the vault root "waiting for metadata love", asks to "tag it and move it to the right folder", "run OG fetch", "clean up the root", "these VCs are in the root", or whenever an agent is about to create a note and finds an empty or thin root stub with the same name; also when clicking a bare [[link]] in Obsidian has created empty root files. Encodes the vault-is-symlinks layout (root not under git, typed folders are), the backup-first rule, the high/medium/low classification gate, merge-don't-duplicate, fill-only-empty OG fetching, line-wise frontmatter edits that preserve key order, and the post-move link-uniqueness check.
lossless-monorepo/agent-skills/open-graph-share-seo-geo/references/llms-txt-implementation
lossless-monorepo/agent-skills/open-graph-share-seo-geo/references/seo-best-practices
lossless-monorepo/agent-skills/open-graph-share-seo-geo/references/sitemap-implementation
lossless-monorepo/agent-skills/open-graph-share-seo-geo/references/unfurler-matrix
lossless-monorepo/agent-skills/open-graph-share-seo-geo/references/user-tools-for-image-generation
lossless-monorepo/agent-skills/open-graph-share-seo-geo/skill
How to make a page unfurl reliably in iMessage, WhatsApp, Slack, Discord, LinkedIn, and X; surface to search engines via sitemap.xml + robots.txt; and stay legible to generative engines (GEO), including the llms.txt standard for LLM corpus ingest. Use when adding or debugging OpenGraph / Twitter Card metadata, picking an OG image format, choosing where to host the image, fixing pages that "won't unfurl", auditing share previews, scaffolding /llms.txt and /llms-full.txt, or adding @astrojs/sitemap + robots.txt to a splash or marketing site. Encodes the JPEG-over-WebP rule, the ImageKit content-negotiation gotcha, the absolute-URL requirement, the og:image:type-must-match-bytes invariant, the cache-busting recipe for forcing a re-unfurl, the prose-in-markdown source-of-truth pattern for llms.txt, and the sitemap filter that keeps non-HTML routes (llms.txt, 404) out of the search-engine index.
lossless-monorepo/agent-skills/openpanel-analytics/skill
Adds and verifies OpenPanel analytics on Lossless Astro sites and splash pages, deployed on Vercel, GitHub Pages, or both. Covers the production-only Analytics.astro component, the OPENPANEL_CLIENT_ID variable on each host, the OpenPanel "supported domains" setting whose absence silently 401s every event, and a curl-plus-DevTools verification. Use when adding analytics to a site or splash, when a site deployed to a new host or domain, when OpenPanel shows no data, or when the user mentions OpenPanel, analytics, tracking, traffic, or "is anyone visiting".
lossless-monorepo/agent-skills/overlay-svg-text/skill
How to overlay on-brand SVG text on Lossless OG / share imagery — Hack Bold gradient-filled h1, thin sans eyebrow, Poor Story handwritten note. Use whenever a generated OG image needs title/eyebrow/sub text composited on top before it ships (the empty-region zone from `generate-consistent-og-images` is the canvas this skill paints into), whenever an unfurl preview looks too anonymous without a wordmark or subtitle, whenever a fundraise-deck slide needs a brand-flavored title overlay on a hero image, whenever the user says "overlay text on the OG image", "add a title to the banner", "make the unfurl say something", "drop a wordmark on this", or names this skill directly. Encodes the brand-wide type system (Hack Bold for gradient h1, thin sans for eyebrow, Poor Story for handwritten notes), the per-site gradient-from-DESIGN.md discipline (the brand SVGs are raster-baked references, not editable gradient sources — the editable gradient lives in each project's DESIGN.md), the canonical SVG fill-with-gradient pattern (simpler and more portable than mask/union for this use case), and the sharp-based compositing pipeline that writes JPEG-out for delivery per the open-graph-share-seo-geo skill.
lossless-monorepo/agent-skills/prep-images-for-embed/skill
Turn raw screenshots into embeddable, CDN-hosted images with real alt text — rename, resize, strip metadata, stage in a gitignored folder, upload to ImageKit, and emit SEO-correct markdown or HTML. Use whenever the user drops screenshots and wants them in a changelog entry, splash page, spec, or any markdown surface; whenever they say "add these screenshots", "put these images in the changelog", "upload these to the CDN", "make this post image-heavy"; whenever local image references need converting to CDN URLs; or whenever an image is destined for an og:image. Encodes the measured content-negotiation result (upload JPEG, never WebP — the WebP fallback is a PNG up to 3x larger), the alt-text-is-not-optional rule, the per-repo gitignored staging convention, and the naming scheme that makes filenames themselves carry SEO weight.
lossless-monorepo/agent-skills/pseudomonorepos/references/anatomy
lossless-monorepo/agent-skills/pseudomonorepos/references/branch-alignment
lossless-monorepo/agent-skills/pseudomonorepos/references/content-rollup
lossless-monorepo/agent-skills/pseudomonorepos/references/lifecycle-workflow
lossless-monorepo/agent-skills/pseudomonorepos/references/search-first
lossless-monorepo/agent-skills/pseudomonorepos/references/the-tree
lossless-monorepo/agent-skills/pseudomonorepos/skill
The Lossless Group's coined term and pattern — parent repos that aggregate child repos (often as git submodules) primarily to host a parent-level context-v/. Use whenever working anywhere in lossless-monorepo or its descendants, when starting any new task that might overlap with prior work, when scaffolding a new project, when the user mentions "pseudomonorepo", "submodule", "context-v", or names of the children (ai-labs, astro-knots, content-farm, tidyverse), AND ALWAYS when the user proposes to move/relocate/re-clone/re-nest a repo within the tree (which triggers the HARD STOP three-precondition checklist — local branches synced, remote branches catalogued, gitignored secrets backed up). Encodes the search-first-before-creating behavior, the tree-walking discipline, and the relocation-safety protocol.
lossless-monorepo/agent-skills/readme
Overview of the Lossless Skills collection - installation instructions, skill status, and contributing guidelines. Reference only.
lossless-monorepo/agent-skills/remake-deck/skill
Remake a company's source pitch deck (PDF, PPTX, or folder of slide images) into N clean-room design variants that play in the DidiDecks Scroll-UI shell. The agent takes the VP Eng / orchestrator role and runs the dididecks-ai plan `Remake-Source-Deck-into-Design-Variants`, which extracts and audits the deck, fans out N designers who each produce one coherent HTML + Tailwind deck without seeing the original layout or each other, refactors each into Astro `Section__<Name>.astro` components rendered from one `index.astro`, wires the deck registry, and verifies every variant in the shell. Use whenever the user says "/remake-deck", "remake this deck", "redesign their deck", "give me three takes on this pitch deck", "turn this PDF deck into dididecks variants", or hands over a client's source deck under dididecks-ai and wants new designs from it. Arguments are company, client-site, source-deck path, plus optional KEY=value overrides (N_VARIANTS, DECK_SLUG, CONTENT_POLICY, BRAND_POLICY, INCLUDE_FAITHFUL). Composes with deck-iteration-workflow (this is its Phase 1, done N times in parallel), astro-knots, theme-system, and setup-new-dddecks-workspace (run that first if the client-site doesn't exist yet).
lossless-monorepo/agent-skills/search-lossless-corpus/skill
Use whenever the user asks a question that prior work might already have answered — "what did we decide about X", "when did we ship X", "why did we choose X over Y", "has this failed before", "where did we put X" — and generally to ground answers in The Lossless Group's own corpus instead of training-data folklore. Encodes the four local Chroma collections (`context-vigilance-corpus`, `lossless-changelog`, `claude-code-sessions`, `claude-code-tool-traces`) reachable via the `chroma` MCP server, the four-step agentic-search loop (decompose → execute → evaluate → synthesize), the citation discipline (source path + timestamp + repo slug for every claim), and the metadata-filter patterns that make queries precise. Triggers on questions about prior decisions, shipped work, past Claude Code sessions, recurring tool failures, or any "did we already…" framing. Does not cover Chroma setup, ingestion pipelines, or maintenance — those are handled by [[chroma-local]] and the [[context-vigilance-kit]] scripts.
lossless-monorepo/agent-skills/slide-target/skill
Load the full working context for ONE DidiDecks slide (deck/variant/slot) so an agent can iterate on it slide-by-slide without re-explaining where things live. The first of the `slide-*` skill family (target → improve → rank → decompose). Use whenever the user wants to work on a specific slide of a DidiDecks/Astro deck — "let's work on slide 2", "fix this card", "/slide-target rural-income v1 02", "go slide by slide", "target the funder-pipeline slide" — or when iterating on a client-site deck under dididecks-ai (reach-edu-hub, chroma-decks, etc.). Assembles the section file, the slides.ts slot, the narrative slot, the rank/audit status, the live URLs, and the design-system tokens for exactly that slide, then scopes all work to it. Composes with deck-iteration-workflow and theme-system.
lossless-monorepo/agent-skills/splash/design
Design system for the lossless-agent-skills splash. Operator/CLI posture — the splash reads like a `man` page rendered on a high-end terminal. Mono- forward (JetBrains Mono is the headline AND the meta), brutalist hairline cards (no glow, sharp 2-3px radii), blueprint-grid backdrop. Dark ("operator") is the default mode; light ("daylight inspection") and vibrant ("demo") are first-class. Brand spine is terminal-teal + amber + magenta — deliberately diverged from sibling Lossless splashes (memopop's cyan-led, lfm's ink-violet, ai-labs's sodium-led). Tokens mirror the CSS custom properties in `src/styles/theme.css`; that file is the runtime source of truth, this DESIGN.md is the human- and agent-readable contract.
lossless-monorepo/agent-skills/study-repos-first/skill
The Lossless Group's discipline of pinning a curated collection of upstream repos (a "study") around a domain question *before* designing or coding in that domain. Use when starting work that touches conventions, file formats, schemas, protocols, or any decision where prior art exists; when the user mentions "study", "studies/", "reference collection", "prior art", "pin a submodule", or names of existing studies (open-specs-and-standards, memory-layers-for-agents, data-analytics-specifications-and-standards); when scaffolding a new study, extending one, or deciding whether something belongs in a study vs. a project. Encodes the "read upstream code, don't paraphrase from training data" behavior.
lossless-monorepo/agent-skills/surrealdb-canonical-layer/skill
Verify a SurrealDB-backed canonical layer directly, over the `surrealdb` MCP server, instead of writing a disposable Node script per check. Use whenever the user asks to confirm a batch of writes landed correctly ("did the FreedomFest speakers get tagged right", "do these people have an org relationship", "check that event's rows aren't duplicated"), whenever a new client/event/import needs its data audited for coherence, whenever setting up SurrealMCP for a new project, or when the user mentions "SurrealDB", "canonical layer", "client_access tagging", "affiliation edge", or names this skill directly. Encodes augment-it's live schema (persons/organizations/affiliations/observations/events) as the worked example, the per-table client_access shape (string[] on most tables, singular string on observations — a real inconsistency, not a typo), the flag-don't-fix verification discipline, and the read-only-vs-full-CRUD tradeoff of the official surrealmcp server. Generalizes past augment-it to any project (dididecks-ai, memopop-ai) that adopts the same schemaless-canonical-layer + observations-as-log pattern.
lossless-monorepo/agent-skills/theme-system/references/file-organization
lossless-monorepo/agent-skills/theme-system/references/two-tier-tokens
lossless-monorepo/agent-skills/theme-system/references/vibrant-mode-implementation
lossless-monorepo/agent-skills/theme-system/skill
The Lossless Group's theme and mode architecture — two-tier token system, three-mode contract (light/dark/vibrant), theme.css organization, and design system conventions. Use when setting up themes/modes for any Astro Knots site, debugging mode toggles, working with CSS tokens, or when the user mentions "vibrant mode", "two-tier tokens", "theme.css", or design system patterns.
dididecks-aiai-labs10
Loops — recurring maintenance disciplines that keep the repo legible over time
A new context-v category for skills that aren't one-shot specs or plans but **recurring rhythms** — the small, regular maintenance moves that keep a fast-moving repo readable to humans + agents who weren't there when the work happened. Each loop lives as its own subdirectory with a SKILL.md, optional scripts/, and templates/. Companion concept (TBD): `context-v/pairing/` for human-agent collaboration disciplines.
dididecks-ai/agent-skills/loops/git-conventions/references/body-structure
dididecks-ai/agent-skills/loops/git-conventions/references/examples
dididecks-ai/agent-skills/loops/git-conventions/references/header-patterns
dididecks-ai/agent-skills/loops/git-conventions/skill
The Lossless Group's git commit message conventions — structured headers with action verbs and effort groupings, paragraph-spaced bodies that explain impact before implementation, and "Also included" riders for minor changes. Use when writing commit messages, reviewing commits, or when the user mentions "commit message format", "git conventions", or asks how to structure a commit.
dididecks-ai/agent-skills/loops/maintain-design-md/skill
How to author and maintain a `DESIGN.md` file at the root of any Lossless project (site, splash page, plugin landing, fundraise deck) following Google Stitch's open spec. Use whenever a project is missing a `DESIGN.md` and an agent needs the project's visual identity in machine-readable form; whenever the user mentions "design tokens", "design system", "DESIGN.md", or "Stitch spec"; whenever theme/CSS-token work changes the runtime values (new CSS custom property in `:root`, renamed token, new mode, new component pattern, refreshed palette, refreshed typography scale) and the documented contract has drifted; whenever a sibling skill (`generate-consistent-og-images`, `theme-system`, `astro-knots`) needs to read locked design values; whenever the user says "the agent doesn't know what color we use" or "let's write down the design system." Encodes (1) the Stitch spec's frontmatter token groups (colors, typography, rounded, spacing, components) and the eight prose sections in canonical order, (2) the maintenance triggers — what kinds of code changes should bounce back into the document, (3) the "runtime CSS is source of truth, DESIGN.md is the contract" discipline, (4) the precedent for off-spec extensions like an `imagery:` block, (5) anti-patterns. The skill never sees an API key or makes network calls — it's a pure-document discipline.
dididecks-ai/agent-skills/loops/maintain-design-md/templates/design-md-scaffold
★ One paragraph describing the visual identity. Mention the runtime source-of-truth path so future agents know where to read the actual values.
dididecks-ai/agent-skills/loops/maintain-filemap/skill
Use whenever the directory shape of a Lossless pseudomonorepo (or any child repo) changes — a new top-level directory is added, a submodule is mounted or unmounted, a major subsystem is renamed — or on a weekly cadence, or before any release that would land on GitHub, to regenerate the `FILEMAP.md` at each affected repo's root so collaborators see the current shape without cloning. Triggers when the user mentions "filemap", "tree", "directory layout", "repo overview", "what does this repo even contain", "new collaborator joining"; also when the agent itself proposes adding/removing a top-level dir or a submodule, because that's exactly the moment the discipline matters.
dididecks-ai/agent-skills/readme
dididecks-ai/agent-skills/setup-new-dddecks-workspace/skill
Scaffold a new dididecks-ai client workspace end-to-end — submodule scaffold under `client-sites/<slug>/`, DESIGN.md from the client's brand identity, theme tokens, auth-surface wiring, initial substantiation-corpus connection, and a Scroll-UI starter deck the deck-iteration-workflow can pick up from. Two source-of-branding modes — **website-parse** (crawl the client's public site for tokens, fonts, logos via `crawl-fetch-ingest`) and **source-code-copy** (lift `theme.css` / `DESIGN.md` / brand assets directly from an existing repo when the client is us, an adjacent Lossless property, or otherwise hands over their source). Use whenever a new engagement starts and a `client-sites/<slug>/` submodule does not yet exist; whenever the user says "set up a workspace for <client>", "scaffold a new client", "we have a new client", "spin up a deck site for <firm>"; whenever The Lossless Group itself or any other internal Lossless property needs a deck-site of its own (source-code-copy mode triggers automatically when the brand source is a sibling Lossless repo); and as the cloud-workspace evolves, whenever the equivalent flow needs to fire from a chat surface rather than a CLI. Composes the existing skills — does not re-implement them — for crawl-fetch-ingest, maintain-design-md, theme-system, generate-consistent-og-images, deck-iteration-workflow, and pseudomonorepos (the submodule and branch-tier discipline).
self-host-stack10
self-host-stack/agent-skills/custom-domain-cutover/skill
Point a custom (sub)domain at a Railway service and survive the cutover — DNS records, wildcard overrides, cert issuance, and the stale-cache theater that follows. Use whenever minting a `*.didi.sh` (or any custom) domain for a client hub/app, whenever a freshly-cut domain "doesn't work" on someone's machine while probes say it's live, or whenever the user says "I can't see the subdomain."
self-host-stack/agent-skills/decilehub-interface/readme
self-host-stack/agent-skills/decilehub-interface/references/connector-setup
self-host-stack/agent-skills/decilehub-interface/references/pipeline-vocabulary
self-host-stack/agent-skills/decilehub-interface/references/tool-map
self-host-stack/agent-skills/decilehub-interface/skill
Operate a VC firm's Decile Hub from Claude Desktop, claude.ai, or Claude Teams via Decile's native MCP connector — 158 tools across the LP/investor pipeline, deal flow, portfolio, fund admin, data room, and outbound email. Use when someone asks about an LP or a deal ("is X in our pipeline?", "what stage?", "who referred us?"), wants a call or voice memo logged, wants records created or updated, wants a pipeline or portfolio roundup, or wants to send an email, newsletter, PACT, or LPA. Supplies the safety tiering Decile omits (its 158 tools carry zero annotations, so list_people and publish_newsletter look alike), the People-vs-Organizations-vs-Prospects model, where notes actually land, the never-create-a-duplicate rule (there is no merge tool), and the discipline of reporting only what the record supports.
self-host-stack/agent-skills/decilehub-interface/templates/deal-upsert
self-host-stack/agent-skills/decilehub-interface/templates/lp-upsert
self-host-stack/agent-skills/decilehub-interface/templates/speech-to-text-upsert
self-host-stack/agent-skills/vc-firm-profile-ingest/skill
Research a VC firm from the open web and land it in BOTH systems in one pass — a Twenty CRM company record with a research note attached, and a cross-linked Outline wiki page in the Venture Firms collection following the house profile template. Use whenever the operator says "create a VC profile", "add <firm> to the CRM and the wiki", "profile <firm>", "research this fund and write it up", "who are they and should we care", or names this skill. Encodes the dedupe-first discipline (98+ companies already exist — never create a second record), the two-call note attachment Twenty requires, the composite link-field shapes that silently fail as plain strings, the Twenty↔Outline join (the wiki page header carries the CRM record UUID), the house page template with its open-questions checklist, and the sourcing hierarchy that keeps contaminated aggregator data out of the record. Client-scoped: collection and workspace IDs below are Palmer AI's.
augment-itai-labs3
augment-it/agent-skills/decile-hub-interface/skill
The operator-facing workflow layer for getting real-world data INTO and OUT OF a client's Decile Hub CRM — sitting on top of the decile-hub-connector API contract. Use whenever importing a batch of real records into Decile (voice-note transcripts, CSV lead lists, LP rosters, event attendees), matching hand-collected records to existing Decile prospects by name, appending notes to people/prospects, or reasoning about the People-vs-Organizations-vs-Pipelines-vs-Prospects data model for a fundraising pipeline. Triggers when the user says "import these into Decile", "add these to the pipeline", "match these to Decile", "put these voice notes / this list into Decile", "attach a note to the prospect", "which pipeline do these belong to", or names the importer script decile-import-voicenotes.mjs. Encodes the read-only introspection recipe (whoami → pipelines?kind=investor → stages → prospect shape), the name-matching import pattern (Apple Voice Memos and most hand-collected records carry NO email, so the filename/typed-name is the identity key and Decile supplies the rest), where notes actually land (the Person/prospectable, NOT the pipeline row — so they surface across every pipeline that Person is in, tied to one pipeline only by the note's context label), the idempotent + additive + dry-run-first import discipline, the aliases.json spelling-bridge, and the .env gotchas that silently break the connector. The authoritative API contract is [[decile-hub-connector]] + the on-disk swagger; this skill is how a human operator drives it.
augment-it/agent-skills/inbox-curation/skill
didi's triage discipline for filing captured links and sources into the right corpus (thesis/strategy/topic) inside augment-it. Use whenever the user gives didi a URL to save, asks to "file this under <corpus name>", names an existing thesis/strategy by name for a link to go under, or it's unclear which corpus a captured link belongs to. Encodes the decision tree (named + existing corpus → source.add directly; new corpus → propose domain.create first; unclear → propose or park in the inbox), the domain-resolution discipline (resolve names against the live "Existing corpora" list, never fabricate a domain_type/domain_slug), and the boundary with corpus.inbox.add (the untriaged capture-first fallback). The capability catalog and args shapes live in services/workspace/src/chat.ts's CURATOR_CHAT_VERBS slab — this skill is the reasoning on top of it.
augment-it/agent-skills/triage-inbox-w-suggestions/skill
The operator+agent discipline for draining a client's corpus inbox (clients/<client>/corpus/inbox/) — agent scans each pending file, stamps a triage_suggestion, and proposes destinations in confidence-banded batches; the operator sweeps. Proven on the first co-pilot run (2026-07-25: reach-edu 141→4 in six batches); carries the run playbook, six-bucket org taxonomy, pointer/stream/gated routing, and reusable scripts/ helpers. Use whenever the user says "triage the inbox", "work through the inbox", "drain the inbox", "/triage-inbox", or asks to file/sort pending inbox captures. Encodes the destination model (funder org folder, person, or domain — with SurrealDB as the single canonical index and cheap reference .md copies fanned into any additionally-relevant folder), the six task lanes (TRIAGE/EXTRACT/ENRICH/DEDUPE/FLAG/DISCARD), the tagging convention (YAML array, Train-Case with lowercase connector words), and the batch/resume rhythm. Co-pilot phase: agent proposes, operator disposes; nothing files without an operator sweep.
astro-knots2
astro-knots/agent-skills/dependency-upgrade-loop/skill
Fan out across all active Astro Knots sites, upgrade dependencies in safe → risky order (patch/minor first, then major bumps like Astro and TypeScript), fix breaking changes, verify builds with `pnpm build` + `pnpm exec astro check`, write changelog entries, and push submodules. Loops until every site is current. Invoke via `/loop` to self-pace across all sites, or pass a specific site name to target one.
astro-knots/agent-skills/generate-site-design-variants/skill
Redesign a site as N complete, genuinely different design directions built in parallel against one shared content layer — working code, two-tier theming, three-mode contract, themed image assets, consistent stack — so a stakeholder can compare them like-for-like and retiring the losers is a delete rather than a refactor. Use whenever a prospective or existing client needs a redesign pitch, whenever the user says "three directions", "design variants", "show them some options", "redesign this site", "build a spike", "competing designs", or asks to generate multiple looks for one site; also when scaffolding the chooser/brand-kit/design-system surfaces those variants need. Encodes the spine-before-pixels ordering, the one-content-layer rule, per-direction Tier 2 theme files, the single-family themed-imagery pattern, constraint-in-code, and the no-cross-imports isolation that makes variants disposable.