个人作者

Vytautas Cepas

Agentic AI Systems Researcher & Engineer

机构 · @MBD-Lithuania @vilniustech所在地 · Vilnius, Lithuania更新于 2026-11-15

Skills
19
仓库
1
职业覆盖
0
场景覆盖
0
Stars
★ 0

Vytautas Cepas 的 Skills 19

VytCepas
VytCepas/harbor-core

systems-thinking

For a problem where the obvious fix has already failed or made things worse. The cause usually lives three or four layers below the events that keep appearing; this finds that structure, matches it against the ~10 known archetypes to get the canonical intervention, and checks second-order effects before you commit. Event-level fixes are what it exists to replace. USE WHEN systems thinking, causal loop, feedback loops, archetypes, leverage points, iceberg model, fix the system, why does this keep happening, recurring problem, second-order effects, the fix made it worse, this keeps coming back. NOT FOR incident causal chains (use root-cause-analysis).

★ 0
VytCepas
VytCepas/harbor-core

red-team

Adversarial analysis deploying parallel expert agents to stress-test ideas, strategies, and plans — decomposes into atomic claims, attacks them, then steelmans and counter-argues, producing severity-ranked findings with remediation. USE WHEN red team, attack idea, counterarguments, critique, stress test, devil's advocate, find weaknesses, break this, poke holes, strongest objection. NOT FOR collaborative debate to find best path (use council).

★ 0
VytCepas
VytCepas/harbor-core

first-principles

Physics-based reasoning framework (Musk methodology) that deconstructs a problem to irreducible fundamental truths, classifies every element as hard constraint, soft constraint, or assumption, then reconstructs the optimal solution from fundamentals alone. USE WHEN first principles, fundamental truths, challenge assumptions, real constraint, rebuild from scratch, start over, physics first, question everything, reasoning by analogy. NOT FOR structural feedback loops (use systems-thinking).

★ 0
VytCepas
VytCepas/harbor-core

company-help

Explains this laptop's safety settings in plain words: why a step was stopped, asked about or is waiting for an admin, where work files belong, and how to get a website allowed. USE WHEN a step is refused or blocked, a permission question appears, a site or download fails, or someone asks what Harbor is or where to save files. NOT FOR changing a setting: nobody here can.

★ 0
VytCepas
VytCepas/harbor-core

test-strength

Prove a load-bearing test can actually fail, and that it fails for the right reason. Break the thing it guards, watch it go red, restore — then check it stays green on a valid-but-unusual input, because red on a mutant proves discrimination, not correctness. USE WHEN a suite is written or changed, a guard is trusted, a gate reports zero, or a green result is about to be cited as evidence. NOT FOR reviewing a diff for defects (audit-review-fanout), or running a suite to see it pass (`bin/test-suite-run.sh`).

★ 0
VytCepas
VytCepas/harbor-core

status-suggest-scan

Runs the repeated-work scan and says in plain words what a person keeps doing by hand. USE WHEN a person asks what they repeat or what Harbor could take over. NOT FOR building what it finds.

★ 0
VytCepas
VytCepas/harbor-core

skill-catalog

The index of every skill, `harbor` verb, agent-facing bin tool and credentialed CLI on this box, each with the path or exact command; most are hidden from your listing and this is the only route to them. USE WHEN you are about to wait on CI or a PR, run a suite, push, merge or do any scripted chore by hand, or do reasoning work by hand: design an eval or a pass^k study, run a red-team pass, chase a root cause, reason from first principles, get independent perspectives, write or optimise a prompt, extract a paper, generate options. ALSO WHEN what skills do I have, list skills, find a tool, is there a harbor command for this, how do I wait on CI, skill-book (its old name). NOT FOR invoking a skill already in your listing.

★ 0
VytCepas
VytCepas/harbor-core

member-setup

Adopt Harbor in an organisation: hub repo, signing key, pinned harbor-core, a setup zip per colleague, releases. USE WHEN onboarding a company or colleague, building a setup zip, raising the hub pin. NOT FOR a project's own CI.

★ 0
VytCepas
VytCepas/harbor-core

housekeeping

暂无简介

★ 0
VytCepas
VytCepas/harbor-core

doc-learning-artifact

The approved house style and build kit for study pages — an exam guide, a course explainer, a revision page: one section per tab, hand-drawn SVG diagrams whose boxes open a detail card INLINE under the diagram, a saved-answer quiz, study aids, and a Playwright check that runs in real Chrome on desktop and iPhone. USE WHEN building or updating a study guide, exam guide, course notes page, revision page or learning artifact; when somebody wants to learn a course, a lecture series or a topic from one page. NOT FOR an architecture or system diagram (`doc-atlas`), a status report or findings, or anything that is not meant to be studied.

★ 0
VytCepas
VytCepas/harbor-core

doc-knowledge-base

Design or restructure a knowledge base (a wiki, a document base, a shared agent memory store) so a person can browse it and an agent can find answers with list, read and keyword search alone, no RAG, to standards/knowledge-base.md. Output is a structure proposal or a conforming base, with a findability baseline and an after-measure. USE WHEN structure a wiki, reorganise a wiki or document base, dedupe pages, design a knowledge base, handbook or shared memory store, shelves and books, page templates, tags or metadata for pages, maps of content, llms.txt, entry page, glossary, findability, agents cannot find docs, avoid RAG or vector search. NOT FOR writing one page's content (write it to the page shape directly), Harbor's own doc kinds and front matter (standards/naming.md, harbor/D-90), or a code review.

★ 0
VytCepas
VytCepas/harbor-core

doc-deliverable-contract

Before writing anything a person outside this session will read — a client thread reply, a ticket comment, a recommendation, a proposal — restate the contract as your own constraint: the verb in the ask and what it licenses, the audience and therefore the language, and the word ceiling. Then hit the five moves — locus, elimination, ownership, their currency, termination. USE WHEN replying to a client or account team, answering a thread, writing a recommendation or proposal, drafting a ticket comment, sending findings to anyone, or when a correct analysis needs to become a usable answer. NOT FOR the investigation itself (casefile), or the durable map (topology).

★ 0
VytCepas
VytCepas/harbor-core

doc-atlas

The single owner of human-readable HTML artefacts on this box: an atlas whose subject is a DRAWING, not prose. The diagram takes the whole stage with pan-and-zoom navigation, clicking any component opens structured fields — what it is, what it carries, why it exists, which files it lives in — and nothing is learned by scrolling. Tabs group the diagrams, dropdowns hold the detail, every authored string has an enforced word ceiling, and the output lands in ~/Deliverables/<date>-<slug>/ as a local file. Renders archify specs. USE WHEN presenting an architecture, a technology stack, a module or connection structure to a person; when an existing atlas needs updating; when somebody asks for a diagram they can click. NOT FOR a status write-up, a what-changed report, findings, or test output — those belong in the terminal, the PR body or a repo doc, and an HTML page that reproduces terminal output is never opened twice. NOT FOR a projection of a TOPOLOGY.md, which is `topology`'s own report-gen.sh.

★ 0
VytCepas
VytCepas/harbor-core

audit-review-fanout

Review a code change with several cheap reviewers, each given a different lens, then verify every finding before reporting it. The deliverable is verified defects only, each with its evidence; none found is a valid result. USE WHEN review this PR, review the diff, code review, review my changes, audit this change, check before merge, second opinion on code. NOT FOR proving a test can fail (test-strength), or the merge decision (gate-merge).

★ 0
VytCepas
VytCepas/harbor-core

audit-claims

A fresh-context verifier checks each claim of an answer against its source before it ships. USE WHEN an answer carries a number, an exists/absent, a recommendation or a done, or leaves the session. NOT FOR a code diff (audit-review-fanout).

★ 0
VytCepas
VytCepas/harbor-core

agent-routing

Which model tier and effort each delegated agent runs on — Agent tool calls, headless `claude -p` runs, workflow agents and orchestrator launches — when to escalate, and what a brief must name so the run ends cleanly. The cheapest tier that passes the gate, chosen per call, never inherited. USE WHEN delegating to a subagent, choosing a model or effort for an agent, fanning out agents, writing a workflow or orchestrator launch, an Agent call was denied for a missing model, an agent failed and you are deciding whether to escalate. NOT FOR reviewing a diff (audit-review-fanout), or API code that calls Claude (claude-api).

★ 0
VytCepas
VytCepas/harbor-core

access-ledger

Which account to use on each system, the role it holds and what it cannot reach: harbor-private/access/ACCOUNTS.md, generated from the route cards; plus the one-ask access ledger. USE WHEN which account, wrong account, 401, 403, permission denied, Reauthentication failed, do I have access, can I reach X, need access, credentials, token, least privilege. NOT FOR obtaining or storing a credential (the operator holds those), or a number that is wrong (a casefile pack owns that).

★ 0
VytCepas
VytCepas/harbor-core

access-browser

Pick the right browser backend and drive it, then say what the run's absence is and is not evidence for. Two axes — does it need a login, and does it run attended or unattended — six rows, one of them refused because its backend is an unledgered credential. `harbor browser route` prints the contract; `harbor browser hosts` is the only instrument here that can support a NEGATIVE. USE WHEN which browser tool, does the pixel fire, no pixel fired, is the tag absent, what third parties load, subresource list, instrument a storefront, headless vs extension, drive a logged-in dashboard, harbor chrome lost or hidden tab, add a Commerce Manager data feed, screenshot someone else's site, consent banner changes what fires. NOT FOR administering a tag-manager or analytics container (its workload skill owns that), historical numbers (reporting-apis), or checking our OWN generated HTML — that is bin/doc-visual-check.sh, a build gate.

★ 0