GitHub Actions Pat
bifrost-proxy/bifrost
用 Personal Access Token 通过 GitHub REST API 分析 Actions CI 的失败 run/job/step、拉取日志、轮询运行状态、做 PR code review,并驱动 fix → push → watch → iterate 的闭环。Token 只从 GITHUBTOKEN 环境变量读取,不落盘、不回显。适合在 bifrost remote /…
Start here for any change to an Arandu (Go) application that adds or changes behaviour -- "add invoices", "let users publish a post", "send a weekly report", "call the payment provider", "expose…
$ npx skills add arandu-io/arandu --skill arandu-feature -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install arandu-io/arandu arandu-feature --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/arandu-io/arandu.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/arandu-feature .claude/skills/arandu-feature && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "arandu-feature" agent skill from https://github.com/arandu-io/arandu/tree/main/.agents/skills/arandu-feature into .claude/skills/arandu-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "arandu-feature", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/arandu-io/arandu/tree/main/.agents/skills/arandu-featureType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add arandu-io/arandu --skill arandu-feature -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install arandu-io/arandu arandu-feature --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/arandu-io/arandu.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/arandu-feature .agents/skills/arandu-feature && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "arandu-feature" agent skill from https://github.com/arandu-io/arandu/tree/main/.agents/skills/arandu-feature into .agents/skills/arandu-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "arandu-feature", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add arandu-io/arandu --skill arandu-feature -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install arandu-io/arandu arandu-feature --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/arandu-io/arandu.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/arandu-feature .cursor/skills/arandu-feature && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "arandu-feature" agent skill from https://github.com/arandu-io/arandu/tree/main/.agents/skills/arandu-feature into .cursor/skills/arandu-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "arandu-feature", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/arandu-io/arandu.git --path .agents/skills/arandu-feature--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add arandu-io/arandu --skill arandu-feature -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install arandu-io/arandu arandu-feature --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/arandu-io/arandu.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/arandu-feature .gemini/skills/arandu-feature && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "arandu-feature" agent skill from https://github.com/arandu-io/arandu/tree/main/.agents/skills/arandu-feature into .gemini/skills/arandu-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "arandu-feature", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install arandu-io/arandu arandu-featureInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add arandu-io/arandu --skill arandu-feature -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/arandu-io/arandu.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/arandu-feature .github/skills/arandu-feature && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "arandu-feature" agent skill from https://github.com/arandu-io/arandu/tree/main/.agents/skills/arandu-feature into .github/skills/arandu-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "arandu-feature", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add arandu-io/arandu --skill arandu-feature -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install arandu-io/arandu arandu-feature --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/arandu-io/arandu.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/arandu-feature .opencode/skills/arandu-feature && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "arandu-feature" agent skill from https://github.com/arandu-io/arandu/tree/main/.agents/skills/arandu-feature into .opencode/skills/arandu-feature/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "arandu-feature", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
arandu-featureStart here for any change to an Arandu (Go) application that adds or changes behaviour -- "add invoices", "let users publish a post", "send a weekly report", "call the payment provider", "expose…
Arandu Feature is an agent skill from arandu-io/arandu. Start here for any change to an Arandu (Go) application that adds or changes behaviour -- "add invoices", "let users publish a post", "send a weekly report", "call the payment provider", "expose this to an assistant", "add an API endpoint". It classifies the feature, walks the anatomy and the "where each kind of code lives" table in AGENTS.md, picks the aru generators, says what to wire by hand and what to test, and names the family skill for each step. Use it before writing any file.
Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering REST APIs, Forms and invoices and Agent instruction files. It works with GitHub and Go. The repository describes itself as: The Arandu project skeleton, which aru new clones. The licence is MIT.
4 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit b8a4273. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
gobashFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Arandu Feature loads about 2.5k tokens when it runs. Until then it costs about 126 tokens; SKILL.md has 1,100 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from arandu-io/arandu at commit b8a4273, republished under its MIT licence (© arandu-io). 1,100 words, ~2,486 tokens.
.claude/skills/arandu-feature/SKILL.md (or your agent's skills folder).Any request that adds or changes what the application does. It is the entry to the other skills: it decides the shape of the feature, and each step names the family skill that holds that step's rules. A one-line fix inside code that already exists goes straight to the family skill of that code.
AGENTS.md whole: the anatomy table, the "Where each kind of code
lives" table and "What does not exist here".notes resource is the whole
anatomy in this repository: a model with a transition, a nested resource, a
named action, a JSON Resource, an event with a listener, a notification, a
scheduled job and an external client. .agents/skills/notes maps it.arandu-ecosystem before any table: a
module of the ecosystem may already own the capability.aru mcp, connect it (arandu-mcp): its
feature_recipe and where_does_it_go answer steps 1 to 3 below from the
contract of the pinned aru, and generate previews a generator before
it writes.Each symbol has one import path, and aru imports:catalog prints it for the
framework version in go.mod:
| what | import |
|---|---|
Grant, Subject, Authorize, Tenant, SystemGrant | github.com/arandu-io/hesape/auth |
Context, the argument of every action | github.com/arandu-io/hesape/http |
Router, Indexer and the other resource interfaces, Invoker | github.com/arandu-io/framework/http |
the route guards, RequireToken, Idempotent | github.com/arandu-io/framework/http/middleware |
validation.Errors, Validatable | github.com/arandu-io/hesape/validation |
database.DB, database.Transaction | github.com/arandu-io/hesape/database |
1. Classify the feature. Write down which of these it is; most are two or three at once.
| the feature | its first step | family skill |
|---|---|---|
| a new kind of record, with a table | aru make:module | arandu-module |
| a record that lives under another | aru make:module --parent=<resource> | arandu-module, arandu-http |
| a verb beyond CRUD on a record: publish, approve, cancel | a rule in the entity, aru make:controller --action | arandu-module, arandu-http |
| a screen or a part of one | a view, and maybe a partial | arandu-view |
| an answer to a program rather than a person | aru make:resource | arandu-api |
| work after the response, on a schedule or in reaction to a fact | aru make:job, aru make:event, aru make:listener, aru make:notification | arandu-async |
| a call to another system, a webhook, an assistant | aru make:client, aru make:mcp-tool | arandu-integrations |
| who may do it | the policy | arandu-policy |
| roles, balances, tags, Markdown, API docs | a module of the ecosystem | arandu-ecosystem |
2. Walk the anatomy in order, skipping the steps the feature does not have: specification, migration, model and its rules, factory and seeder, policy, request, service, controller, routes, view or resource, tests and wiring. The order is the order of dependence: each step compiles against the one before.
3. Put each piece where the table says. A rule of the entity in the model's custom block, the order of a use case in the service, input conversion in the controller, the answer in a view or a JSON Resource. A piece that seems to belong in two rows belongs in the one that does not need the other's collaborators.
4. Generate, then finish by hand. Every generator prints its wiring and
edits neither bootstrap/app.go nor routes/web.go. Paste what it printed,
read it, and write what it could not know in the custom blocks.
5. Test the path. A feature test that drives the feature the way its caller does, the tenant isolation of every new table, and the answers the family skill lists under "Acceptance test".
6. Report what is missing. A capability the framework or the generators do not have is a gap to name in the report, with the file that would have used it -- never a second way written in the application to cover it.
| step | command |
|---|---|
| specification | aru schema, aru generate <spec.yaml> --check, aru generate <spec.yaml> |
| a whole resource | aru make:module <name> --fields "..." --tenant [--parent=<resource>] |
| one artifact | aru make:model, aru make:migration, aru make:policy, aru make:request, aru make:service, aru make:controller, aru make:resource, aru make:job, aru make:event, aru make:listener, aru make:notification, aru make:client, aru make:mcp-tool, aru make:command, aru make:enum, aru make:mail, aru make:middleware, aru make:factory, aru make:seeder, aru make:test |
| the generated query | aru model:build |
| the views | aru view:build |
| what is wired | aru route:list, aru schedule:list, aru about |
| the architecture check | aru doctor |
aru <command> --help prints its usage line with every flag it takes.
Every step of a feature leaves an artifact the next step relies on, and the compiler holds each of them to its contract. This file is the checklist of the example's steps, written as the assertions the compiler checks:
package feature
import (
fhttp "github.com/arandu-io/framework/http"
"github.com/arandu-io/hesape/auth"
hevents "github.com/arandu-io/hesape/events"
hhttp "github.com/arandu-io/hesape/http"
"github.com/arandu-io/hesape/queue"
"github.com/arandu-io/hesape/validation"
clients "<module>/app/Clients"
controllers "<module>/app/Http/Controllers"
requests "<module>/app/Http/Requests"
resources "<module>/app/Http/Resources"
appjobs "<module>/app/Jobs"
listeners "<module>/app/Listeners"
models "<module>/app/Models"
policies "<module>/app/Policies"
)
// The notes feature, step by step.
var (
_ auth.Policy[models.Note] = policies.NotePolicy{} // the policy
_ validation.Validatable = requests.NoteRequest{} // the request
_ fhttp.Indexer = (*controllers.NoteController)(nil) // the controller
_ fhttp.Indexer = (*controllers.CommentController)(nil)
_ hhttp.JsonResource = resources.NoteResource{} // the answer to a program
_ hevents.Publisher = (*listeners.NotifyNoteAuthor)(nil) // the reaction to note.published
_ queue.Handler = (*appjobs.SendNotesDigestHandler)(nil) // the nightly job
_ clients.Newsletter = (*clients.NewsletterClient)(nil) // the external system
_ clients.Newsletter = (*clients.NewsletterFake)(nil) // and its fake
_ = (*models.Note).Publish // the transition is the entity's
)validate(). AGENTS.md
says what is here instead.What a generator does not cover is written between // arandu:begin custom
and // arandu:end custom in the file it wrote, and survives the next run with
--force. A file finished by hand outside those markers -- as the example's
controller is -- is changed by hand from then on, and its skill says so.
All of it is by hand, in two files, from what the generators print:
bootstrap/app.go builds every collaborator once, in Build, and hands it
down: services to controllers, the notifier to listeners, the clients to
services, the queue to the provider that schedules.routes/web.go holds the field on Deps and the route lines, in the custom
block, behind the guard the route needs.bootstrap/background.go registers job handlers; app/Providers declares
scheduled tasks; routes/console.go declares commands.The feature is done when:
tests.SignedIn, a JSON client with Accept: application/json, the
scheduler through RunNow, the relay through Drain;tenant_id is claimed in
tests/Feature/TenantScope_test.go and has a cross-tenant test that reads
and writes;aru doctor reporting nothing new.This skill orders the work; it does not hold the rules of any step. Where a family skill and this one seem to disagree, the family skill is right about its step. Where a generator, a family skill and the code disagree, the code is right and the other two are wrong -- report it.
Run them all, in this order, as AGENTS.md lists them:
export GOWORK=off
aru model:build --check
aru view:build
gofmt -l $(find . -name '*.go' -not -path '*/testdata/*' -not -name '*.kyse.go')
go vet ./...
bash tests/test-layout-guard.sh
go test -race ./...
go build ./...
aru doctor<!-- arandu:begin custom -->
<!-- arandu:end custom -->
© arandu-io, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .agents/skills/arandu-feature of arandu-io/arandu.
Open the folder on GitHubat commit b8a4273
Arandu Feature next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Arandu Feature this skillarandu-io/arandu | 281 | — | ~2.5k | Automated safety check: Pass | MIT | |
| GitHub Actions Patbifrost-proxy/bifrost | 161 | — | ~2k | Automated safety check: Pass | MIT | |
| Browserwingbrowserwing/browserwing | 1.4k | — | ~1.8k | Automated safety check: Pass | MIT | |
| MCP Apps Builderawslabs/cli-agent-orchestrator | 1.4k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| AI Self ImprovementJocysCom/FocusLogger | 213 | — | ~1.1k | Automated safety check: Pass | GPL-3.0 | |
| Setup Matt Pocock Skillsywwynm/EverythingDone | 144 | 8 repos | ~1.7k | Automated safety check: Pass | GPL-3.0 |
bifrost-proxy/bifrost
用 Personal Access Token 通过 GitHub REST API 分析 Actions CI 的失败 run/job/step、拉取日志、轮询运行状态、做 PR code review,并驱动 fix → push → watch → iterate 的闭环。Token 只从 GITHUBTOKEN 环境变量读取,不落盘、不回显。适合在 bifrost remote /…
browserwing/browserwing
Browser automation platform with 78 built-in scripts and full CLI.
awslabs/cli-agent-orchestrator
Load the official MCP Apps builder skills (create-mcp-app, migrate-oai-app, add-app-to-server, convert-web-app) from github.com/modelcontextprotocol/ext-apps.
JocysCom/FocusLogger
Update, create, improve, and synchronise this repository's AI agent instructions and related assets (including skills).
ywwynm/EverythingDone
Sets up an Agent skills block in AGENTS.md/CLAUDE.md and docs/agents/ so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc…
johnpapa/ai-ready
ANALYSIS SKILL — Analyze any repository and generate AI-ready configuration — a canonical AGENTS.md, thin per-tool pointer files, skills, CI workflows, issue templates.
arandu-io/arandu
Answering a program rather than a person in an Arandu (Go) application -- a JSON Resource, a JSON answer from the same routes the pages use, problem+json errors, bearer-token authentication and…
arandu-io/arandu
Work that does not happen inside the request in an Arandu (Go) application -- background jobs and the worker, scheduled tasks, domain events through the outbox, listeners, notifications, mail and…
arandu-io/arandu
Decides whether a feature belongs in the application or in one of five shared Arandu modules before adding permissions, wallets, tags, Markdown rendering or API docs.
arandu-io/arandu
Controllers, requests and routes of an Arandu (Go) application -- the seven resource actions, a resource nested under another, a singleton, a single-action (invokable) controller, a named action…
arandu-io/arandu
Reaching other systems from an Arandu (Go) application, and letting them reach it -- the client of an external API with its interface and fake, webhooks sent and received, and tools, resources and…
arandu-io/arandu
Adds a new entity, resource or CRUD module to an Arandu Go application by writing a YAML specification instead of hand-writing the Go code.
Start here for any change to an Arandu (Go) application that adds or changes behaviour -- "add invoices", "let users publish a post", "send a weekly report", "call the payment provider", "expose…. Arandu Feature is an agent skill from arandu-io/arandu. Start here for any change to an Arandu (Go) application that adds or changes behaviour -- "add invoices", "let users publish a post", "send a weekly report", "call the payment provider", "expose this to an assistant", "add an API endpoint".
Arandu Feature fits situations like: tasks that involve REST APIs; tasks that involve Forms and invoices; tasks that involve Agent instruction files.
Run `npx skills add arandu-io/arandu --skill arandu-feature -a claude-code`. Or copy the skill folder (.agents/skills/arandu-feature in arandu-io/arandu) into .claude/skills/arandu-feature in your project. Claude Code loads it when a task matches its description.
Run `npx skills add arandu-io/arandu --skill arandu-feature -a codex`. Or copy the skill folder (.agents/skills/arandu-feature in arandu-io/arandu) into .agents/skills/arandu-feature in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add arandu-io/arandu --skill arandu-feature -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/arandu-feature, .gemini/skills/arandu-feature, .github/skills/arandu-feature and .opencode/skills/arandu-feature in your project.
Going by SKILL.md and its folder, Arandu Feature needs the command-line tools its instructions call (go and bash).
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Arandu Feature is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.5k tokens (SKILL.md is roughly 9.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Arandu Feature: GitHub Actions Pat (bifrost-proxy/bifrost, 161 stars), Browserwing (browserwing/browserwing, 1.4k stars), MCP Apps Builder (awslabs/cli-agent-orchestrator, 1.4k stars) and AI Self Improvement (JocysCom/FocusLogger, 213 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
arandu-io (a GitHub organization) maintains it in arandu-io/arandu, which has 281 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 10, 2026.
Source: arandu-io/arandu on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.