Study foreign open-source projects to extract transferable architectural lessons into the Obsidian vault. `/teardown` runs a study session over a local clone, or over files fetched at a pinned SHA when no clone exists, dispatching a read-only `surveyor` agent per project through two ordered phases (current structure, then history/rationale) descending one user-picked layer at a time (system map, domain model, code), spot-checking citations before any write, and adding each layer to an interactive Artifact page and to one of two note types: a single-concern QUESTION note that accretes comparison rows across projects over time, or a whole-system PROJECT note anchored on a mental model. Both carry `projects_surveyed:` frontmatter pinning the repo, commit SHA, and date read — the index and the read log in one place. `/teardown-recheck` audits that pin against the corpus's current HEAD, diffing cited files since the recorded SHA and verifying that cited line numbers still point at what the note claims, so drift is caught instead of trusted. A reference instrument for lookup, not a learning exercise. Composes with librarian (graduation, refresh) and ndr (decisions about the user's own projects); distinct from craft:grok, which studies repos the user owns and intends to change.
Plugin teardown from marketplace jdh-agents in jdh313/jdh-agents. Commands read from the repo's manifest — 2 days ago.
teardown-recheckAudit a teardown note's pinned claims against what actually changed in the studied repo since the commit SHA recorded in its `projects_surveyed:` frontmatter — confirm the local clone is current, diff cited files since the recorded SHA, and verify cited `file.py:LINE` citations still point at what t
teardownStudy an outside open-source repository the user does not own, at source level, and land it as a durable vault note that later studies add to (plus an interactive Artifact page where the Artifact tool exists). Use only when the user names an outside repo or project and wants its internals — "teardow
surveyorStudies one foreign open-source project and writes cited architectural evidence to a file — what it does today, and why it is shaped that way. Dispatched by the `teardown` skill, one surveyor per project (or per concern within one large project), so a teardown fans out cleanly and each file's findin
Curates, catalogs, retrieves, and maintains your library of notes and knowledge in an Obsidian vault. Workflow-shaped (Capture / Process / Retrieve / Maintain) and agent-mediated (skills draft, agents execute). 19 skills + 4 agents + 6 references, coupled to the vault conventions in ~/Loose Ends/.claude/rules/{wiki.md,catalog.md} and the Templater templates in ~/Loose Ends/Templates/.
19 skills · 4 agents
Software craftsmanship discipline skills: grill (the interview primitive — walk a design tree one question at a time, facts looked up by subagent rather than asked, no acting until shared understanding), grill-with-docs (that loop applied to vocabulary, against per-repo CONTEXT.md glossaries), diagnose, prototype, tdd, improve-codebase-architecture, grok (stateful multi-session codebase comprehension with supersession-aware understanding records), zoom-out (adapted in part from mattpocock/skills, MIT), infra-review (architecture/security review of Terraform+Atlantis PRs), quiz-me (opt-in active-recall comprehension check after a code explanation), interrogate-model (holistic representability review of a domain model — the legitimate scenarios and personas it cannot express), design-by-stories (design an artifact's shape — schema, template, data model, config — by modeling its actors and user stories first, then deriving the shape from the stories), and lucid-architecture-diagram (drive AWS cloud architecture diagrams in Lucid, including the two silent-failure modes of its API). derive-conventions (derive a repo's unwritten house style from its own code, adjudicate each inferred rule with the human, and write the approved set to CONVENTIONS.md so the review agents stop re-deriving it). wizard (author an interactive bash wizard that walks a human through the steps only they can perform — third-party dashboards, credentials, CI secrets, one-off cutovers — from a hardened template), resolve-conflicts (recover each side's intent from commits, PRs, tickets and NDR heads before resolving a merge, rebase, or jj conflict; detects git vs jj and follows that VCS's own mechanics), and wait-what (user-invoked: re-pitch a message that did not land, in Simplified Technical English using the repo's own vocabulary) — all three adapted from mattpocock/skills, MIT. screen-critique (critique a UI screen design in a fixed order — purpose against its neighbouring screens, then structure,
19 skills · 3 agents
ADHD-friendly productivity coaching: daily planning (/today, /energy), end-of-day capture (/checkin), weekly scheduling (/plan-week) and review (/weekly), life-direction reviews (/review), goal-to-project alignment (/align), project lifecycle (/intake, /breakdown, /reentry, /sunset), idea capture (/spark), brain dump (/dump), task triage (/triage), decision journaling (/decide), and pattern analysis (momentum, overdue-rescue) with adaptive tone calibration
16 skills · 3 agents
Personal SDLC scaffolding for AI-assisted development. A lightweight, ephemeral 'contract' between user and AI drives each code change from captured idea to verified done; the durable layer (CLAUDE.md, ndr atoms, README) lives elsewhere. Lifecycle: capture -> draft -> implement -> close.
7 skills · 2 agents
PM helpers for team Linear workflows. Skills for a PM-mode planning session (read the real state, slice work into cold-handoff tickets, confirm every write), single-ticket authoring (a short shaping interview, body composed to the shared issue-body spec), the weekly grooming loop (per-person WIP), plan-to-tickets breakdown (assignee-aware), chart-first mapping of efforts too large to plan in one session, questionnaires that pull a blocking decision out of someone else's head, and end-of-cycle retro notes (attribution + Linear-first output). Composes with the linear plugin; ndr and librarian integrations are optional externals.
7 skills
Interpret Klippain Shake Tune results for 3D printers: diagnose issues from PNG graphs, explain findings, recommend fixes, and track results over time. Supports belt comparison, input shaper, vibration profile, axes map, and excitation tests.
1 skill · 5 agents
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
1 command · 3 agents
AI-powered codebase understanding — analyze, visualize, and explain any project
9 skills · 10 agents · hooks
Open-source AI job search that runs locally in your AI coding CLI: scan job portals, evaluate listings into a structured A-H report with a 1-5 score, tailor your CV, track applications
5 skills · hooks
ADR lifecycle management — create, index, supersede, and link Architecture Decision Records to code
5 skills · 1 command · 1 agent
Editorial diagrams in your brand, as self-contained HTML and SVG. Architecture, flowcharts, sequence, state machines, ER and database schemas, timelines, swimlanes, org charts, Gantt, Wardley maps, user journeys, service blueprints, UML class, lifecycle phase maps, and charts from bar, line and scatter to Sankey, treemap and heatmap, plus many more. Redraws draw.io, Mermaid, Excalidraw and PlantUML files. Exports SVG and PNG.
1 skill · 7 commands
53 marketing skills for technical marketers and founders: CRO, copywriting, cold email, prospecting, SEO, AI SEO, paid ads, SMS, ad creative, video production, image generation, co-marketing, churn prevention, pricing, referrals, revenue operations, sales enablement, customer research, site architecture, comprehensive AARRR-structured marketing plans, public relations and earned media, offer design, event marketing and webinars, and more
53 skills
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.