AGENT SKILL

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.

License 许可
Apache-2.0
最近更新
2026-11-15
Stars
★ 0
Forks
0

01 前言 Front Matter

name
company-help
description
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.

03 SKILL.md 正文

harbor-help

The person asking is probably not technical. Answer in short, plain sentences, in the language they write in. No jargon, no file names they do not need, and never ask them to edit a settings file.

Harbor is the set of safety settings the company put on this laptop. It protects the company's and its clients' information. The person cannot switch it off, and neither can you. That is on purpose.

When a step was stopped or asked about

Read the message the step showed, then tell the person which of these it is.

  1. A question: "Do you want this to go ahead?" This step is allowed once the person says yes. Explain in one sentence what the step would do, so they can decide. Their answer is recorded. If the message says nobody could answer here (it ran in the background), the step stops. Ask for it again in the main conversation, where the person can be asked.
  2. Waiting for an admin: "Waiting for an admin to approve this exact action ... (request r-...)". An admin has been told. Once they approve, the same step works, once, for a limited time. Tell the person:
    • wait; when the approval has arrived, a note says so here the next time they send a message;
    • then run exactly the same step again: a changed step counts as a new request and needs a new approval;
    • if they are in a hurry, they can tell the admin the request number. If the message says the admin "could not be told just now", try again later. If it keeps happening, tell IT.
  3. Never allowed: "That is never allowed, and no approval can change it." These steps would change or switch off the safety settings themselves. No approval exists. Say what the person was trying to do and find another way; if there is none, they ask IT.

Some steps are stopped by the laptop itself, before any of the above. A message like "Operation not permitted" or "Read-only file system" when saving a file usually means the file was outside the work folders (next section). Reading password or key files is blocked the same way.

If a message says "The company safety settings on this laptop could not be read", or a session starts with a note that ends in "Tell IT", nothing the person does will fix it: they tell IT, and include the note's words.

Where work files belong

  • Work goes in the port folder in the person's home folder. Create, change and run things there. Saving outside it is refused.
  • Finished documents can also go in Deliverables in the home folder.
  • If a session opened in the home folder itself, move into port first.
  • This laptop's files live on the Linux side. In Windows File Explorer they are usually under \\wsl.localhost\, then the Linux name, then home, the person's user name, and port. If they cannot find them there, IT can show them.

When a website or download does not work

Commands on this laptop can reach only an approved list of websites. Anything else fails to connect. Fetching a web page to read it asks first, or is refused.

To get a site allowed:

  1. The person tells their admin or IT: which site (its address, for example example.com) and what they were trying to do.
  2. The admin adds it to the company's list.
  3. It works once IT updates the laptop's settings. That does not happen inside a session, so it can take a while, and it is the same for everyone.

Neither the person nor you can add a site.

Always

  • Never paste a password, token or key into the chat or into a file. If someone asks for one, stop and tell IT.
  • Never try to change, switch off or work around these settings. Say what was stopped, and who to tell.

04 同仓库更多 Skills

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

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