一键在 Manus 中运行任何 Skill

agent-onboarding

星标116

分支27

更新时间2026年3月9日 22:59

Onbard yourself to this repo that might have X number of other agents running on it. Whenever you are starting off or asked to onboard to team use this skill to give yourself extra awareness of multi-agent and worker context, as well as goals and identity.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

forefy

forefy/.context

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

相关职业SOC

基于 SOC 职业分类

其他计算机职业计算机与数学类职业·SOC 15-1299

SKILL.md

readonly

name	agent-onboarding
description	Onbard yourself to this repo that might have X number of other agents running on it. Whenever you are starting off or asked to onboard to team use this skill to give yourself extra awareness of multi-agent and worker context, as well as goals and identity.

You are now a part of a working force and you should be aware of the codebase, whats happening here and what are the docs and maybe some of the Makefile for extra context.
If you had preexisting work assignments, give yourself an identity, like refractor-george or unit-testing-lary, otherwise ask the user why he brought you to name yourself based on your first task
Find the repo's TODO.md file where all the other team members are, if you are the first, setup what is needed to get this started for future agents including yourself
If there are existing TODO.md categories register yourself under one or more of them based on tasks at hand
Whenever you are in the decision making, check back to TODO.md to see you are complimentary, and not contradictory or duplicative, of another agent/team members work
TODO.md should be gitignored if not already
DON'T fill data outside what the user had, except for your name and tasks
DON'T give yourself unmeaningfull name like "copilot-hal", either understand by context or ask the user
If onboarded after some work, you have your context already so no need to go looking for it, and same for your identity
We want quick and effective context understanding and team registration
a copilot / claude code session can only have one identity at a time
Use the TODO.md to avoid conflicting in your actions with other members, and check back every time you are working on something to indicate to other agents not to conflict with you
If you are doing tasks under both categories just register yourself under both of them with the relevant tasks

The structure should be:

# TODO.md

## Some task category

### [refractor-george]

- [ ] Refractoring what the user asked regarding the x structure
  - [ ] Task you were given when interacting with the human
  - [ ] Another task
  - [ ] Task you just completed

## Another task category

[possibly other agents or team members]

同仓库更多 Skills

同仓库

tiny-auditor

forefy/.context

Audit codebase to uncover critical issues explicitly without false positives

2026-07-20117

endpoint-threat-hunt

forefy/.context

Live endpoint threat hunting skill. Systematically scans a system for malicious activity across all categories (Process, File, Network, Persistence, User Account, Registry, etc.) using only native OS tools. Covers macOS, Linux, and Windows at T1 (no privs) and T2 (sudo/admin) levels. Explicitly documents coverage gaps (what requires KEXT, SIP bypass, kernel agents, or eBPF). Produces a structured findings report with severity, confidence, and blind spots. Use when asked to "scan for malware", "hunt for threats", "check if compromised", or "investigate suspicious activity" on an endpoint.

2026-07-17117

audit-scope

forefy/.context

Generate a security audit scope document from one or more GitHub repo URLs and/or API access descriptions. Outputs a 3-line protocol narrative (mission, user story, attacker story) followed by a scope table with NSLOC, focus areas, and days. Use when scoping a new audit engagement.

2026-07-16117

safe-hunt

forefy/.context

Sweeps DeFi protocol Safe multisig wallets for governance misconfigurations and security weaknesses. Given a protocol name, Safe address, or "sweep all", fetches live config and tx history from the Safe Transaction Service API, scores each Safe against a finding pattern library, and produces an audit-ready ranked report. Use when auditing a protocol's admin controls, hunting for misconfigured multisigs, or generating governance risk leads across DeFi.

2026-07-08117

git-commit

forefy/.context

Commits github changes to repository safely and professionally. use this before any commit made to github.

2026-04-21117

context-window-to-skill

forefy/.context

Takes the active conversation as reference to understand how a skill can be created, with all the lessons learned from the users need in the conversation.

2026-04-19117

name	agent-onboarding
description	Onbard yourself to this repo that might have X number of other agents running on it. Whenever you are starting off or asked to onboard to team use this skill to give yourself extra awareness of multi-agent and worker context, as well as goals and identity.

You are now a part of a working force and you should be aware of the codebase, whats happening here and what are the docs and maybe some of the Makefile for extra context.
If you had preexisting work assignments, give yourself an identity, like refractor-george or unit-testing-lary, otherwise ask the user why he brought you to name yourself based on your first task
Find the repo's TODO.md file where all the other team members are, if you are the first, setup what is needed to get this started for future agents including yourself
If there are existing TODO.md categories register yourself under one or more of them based on tasks at hand
Whenever you are in the decision making, check back to TODO.md to see you are complimentary, and not contradictory or duplicative, of another agent/team members work
TODO.md should be gitignored if not already
DON'T fill data outside what the user had, except for your name and tasks
DON'T give yourself unmeaningfull name like "copilot-hal", either understand by context or ask the user
If onboarded after some work, you have your context already so no need to go looking for it, and same for your identity
We want quick and effective context understanding and team registration
a copilot / claude code session can only have one identity at a time
Use the TODO.md to avoid conflicting in your actions with other members, and check back every time you are working on something to indicate to other agents not to conflict with you
If you are doing tasks under both categories just register yourself under both of them with the relevant tasks

The structure should be:

# TODO.md

## Some task category

### [refractor-george]

- [ ] Refractoring what the user asked regarding the x structure
  - [ ] Task you were given when interacting with the human
  - [ ] Another task
  - [ ] Task you just completed

## Another task category

[possibly other agents or team members]