一键在 Manus 中运行任何 Skill

forgejo-direct-api

星标0

分支0

更新时间2026年6月9日 08:22

Use when working directly with Forgejo v15 APIs, private repositories, Actions workflows, runners, pull requests, reviews, statuses, releases, packages, webhooks, organizations, users, or admin operations. Prefer Forgejo's live Swagger and direct endpoints over GitHub-shaped assumptions.

安装

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

在 Manus 中运行

来源

ANcpLua

ANcpLua/ancplua-skills

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

下载

在 Manus 中运行

Forgejo Direct API

Use this skill for Forgejo-first work. Do not start from GitHub names unless the user explicitly asks for GitHub comparison.

Rules

Use live Swagger as authority: <instance>/swagger.v1.json.
Use Forgejo names: repository, actions runner, workflow, run, task, pull request, review, issue comment, commit status, package, release, webhook.
Prefer direct Forgejo API calls over wrappers or compatibility shims.
Keep tokens out of logs and responses.
Use Authorization: token $FORGEJO_TOKEN unless the instance documents another auth scheme.
Treat ActivityPub endpoints as federation only; they are not part of qyl CI, review, package, or repo automation.

Reference files

references/forgejo-api-map.md: Forgejo-native endpoint map by task.
references/forgejo-v15-endpoints.md: generated full v15 route inventory from live Swagger.
references/forgejo-actions-runner.md: Actions workflow, runner, label, secret, variable, dispatch, and run/task notes.
references/forgejo-ai-review.md: Forgejo-native AI review flow using pull request, review, issue comment, and status APIs.

qyl private repo path

GET /user
GET /repos/{owner}/{repo}
authenticated git push
.forgejo/workflows/*.yml
runner label matches runs-on
GET /repos/{owner}/{repo}/actions/runs
GET /repos/{owner}/{repo}/actions/tasks

Refresh and verify

From this skill directory:

scripts/fetch-forgejo-swagger.sh https://v15.next.forgejo.org

FORGEJO_TOKEN=... scripts/verify-forgejo-skill.sh https://v15.next.forgejo.org ANcpLua qyl

Without FORGEJO_TOKEN, verification still checks documented routes against Swagger and skips private repo probes.

同仓库更多 Skills

同仓库

maf-dotnet-source-of-truth

ANcpLua/ancplua-skills

Write Microsoft Agent Framework (.NET) code against the cloned, SHA-pinned source — never from memory or from Microsoft Learn, which lag the source by weeks and keep pre-GA signatures alive long after they were renamed. USE FOR: writing or reviewing any code that touches Microsoft.Agents.AI / Microsoft.Agents.AI.Abstractions (AIAgent, ChatClientAgent, AgentSession, AgentResponse, RunAsync/RunStreamingAsync) or Microsoft.Extensions.AI (IChatClient, ChatMessage, ChatRole, ChatOptions, AITool); a compile error or "method not found" on a MAF type; porting a doc/blog sample that uses AgentThread / AgentRunResponse / CompleteAsync / GetNewThread; deciding whether to wrap an IChatClient in an agent vs hand-rolling the tool loop. ESPECIALLY use it the moment you are about to emit a MAF type or method name from memory — that is exactly when the stale-rename traps bite. DO NOT USE FOR: Microsoft.Extensions.AI internals unrelated to agents; non-.NET MAF (Python); conceptual "why" questions where Learn is fine (use micro

2026-07-210

mcp-csharp-sdk-1-4-1

ANcpLua/ancplua-skills

Authoritative reference for the Model Context Protocol C#/.NET SDK 1.4.1. Use for MCP servers, clients, tools, prompts, resources, transports, sessions, tasks, sampling, elicitation, roots, identity, auth, filters, completions, logging, pagination, HTTP context, McpServer, McpClient, and ModelContextProtocol.* APIs. Always load the relevant reference file before answering.

2026-07-210

extension-store-publishing

ANcpLua/ancplua-skills

Enable, wire up, and operate automated browser-extension publishing to all three stores — Microsoft Edge Add-ons (Partner Center Publish API, ApiKey auth), Chrome Web Store (API v2, Google OAuth refresh token), and Firefox Add-ons / AMO (API v5, HS256 JWT). Use whenever the task touches publishing or updating a browser extension on any store, a publish:edge / publish:chrome / publish:firefox script, the env vars EDGE_PRODUCT_ID / EDGE_API_KEY / EDGE_CLIENT_ID / CWS_CLIENT_ID / CWS_CLIENT_SECRET / CWS_REFRESH_TOKEN / CWS_PUBLISHER_ID / CWS_ITEM_ID / AMO_JWT_ISSUER / AMO_JWT_SECRET, enabling a store publish API, a failing upload, "submission in progress" / "pending review" errors, or automating extension releases — and ESPECIALLY when you are tempted to conclude publishing is blocked because API credentials are missing. Missing credentials are a minutes-long console fix, never a blocker.

2026-07-100

prompt-engineering-expert

ANcpLua/ancplua-skills

Use when the user wants help writing, refining, debugging, or evaluating a prompt, system prompt, custom instruction, agent prompt, or skill description. Triggers on phrases like "improve this prompt", "why isn't Claude doing X", "write a system prompt for...", "review my instructions", "this prompt isn't working", "the model keeps doing Y", "how should I phrase this", or any request to design, fix, or analyze AI prompts. Also triggers when the user is iterating on Claude Code skills, agent instructions, CLAUDE.md / AGENTS.md files, description fields for triggering accuracy, few-shot example design, or debugging unexpected model output. Use this even when the user hasn't named prompt engineering explicitly — if they're discussing a prompt's behavior or how to phrase something for a model, this applies. Also use for Claude Fable 5 / Mythos 5 prompting — migrating prompts from older models, effort tuning, agentic behavior issues, or unexpected refusals.

2026-07-070

microsoft-first-research

ANcpLua/ancplua-skills

Weave Microsoft-Learn-grounded research into ANY substantive help for this user, whose work is overwhelmingly Microsoft-centric (qyl on .NET / Foundry / Microsoft Agent Framework; the microsoft-ai-hackathon tracks Otto, Agent Battle Arena, Inventory Reorder Copilot). Reach for this at the START of essentially any research, design, debugging, "how do I", "is this current / latest", API-shape, SDK-error, or build task — proactively consult the Microsoft Learn MCP and the microsoft-docs skills and the local ground-truth checkouts BEFORE answering from memory, even when the user never types "Microsoft", "Azure", ".NET", or "docs". This is a routing / insurance skill that exists specifically so Microsoft grounding stops getting skipped ~half the time. Stand down only when the task is explicitly about a non-Microsoft stack (AWS, GCP, OpenAI, etc.) or is a trivial mechanical edit with no knowledge question. Pairs with the microsoft-learn-grounding skill.

2026-06-260

microsoft-learn-grounding

ANcpLua/ancplua-skills

Operate the Microsoft Learn MCP — the free, no-auth dogfood API behind Ask Learn and Copilot for Azure — at expert level, and verify how fresh any Microsoft Learn page actually is. Use whenever grounding an answer in Microsoft / Azure / .NET / M365 / Foundry / Agent Framework / Copilot Studio docs, deciding whether a Learn page is current, looking up a page's "Last updated" date / ms.date / source commit, capping token spend on doc searches, or debugging why the Learn MCP returned nothing useful — even when the user never says "Microsoft Learn" or "MCP". Covers the three tools (microsoft_docs_search, microsoft_docs_fetch, microsoft_code_sample_search), the maxTokenBudget control, dynamic tool discovery, the daily-refresh freshness model, and the key gotcha that the MCP strips last-updated metadata so you must read it from the rendered page instead.

2026-06-260

name	forgejo-direct-api
description	Use when working directly with Forgejo v15 APIs, private repositories, Actions workflows, runners, pull requests, reviews, statuses, releases, packages, webhooks, organizations, users, or admin operations. Prefer Forgejo's live Swagger and direct endpoints over GitHub-shaped assumptions.
metadata	{"short-description":"Direct Forgejo v15 API and Actions guide"}

Forgejo Direct API

Use this skill for Forgejo-first work. Do not start from GitHub names unless the user explicitly asks for GitHub comparison.

Rules

Use live Swagger as authority: <instance>/swagger.v1.json.
Use Forgejo names: repository, actions runner, workflow, run, task, pull request, review, issue comment, commit status, package, release, webhook.
Prefer direct Forgejo API calls over wrappers or compatibility shims.
Keep tokens out of logs and responses.
Use Authorization: token $FORGEJO_TOKEN unless the instance documents another auth scheme.
Treat ActivityPub endpoints as federation only; they are not part of qyl CI, review, package, or repo automation.

Reference files

references/forgejo-api-map.md: Forgejo-native endpoint map by task.
references/forgejo-v15-endpoints.md: generated full v15 route inventory from live Swagger.
references/forgejo-actions-runner.md: Actions workflow, runner, label, secret, variable, dispatch, and run/task notes.
references/forgejo-ai-review.md: Forgejo-native AI review flow using pull request, review, issue comment, and status APIs.

qyl private repo path

GET /user
GET /repos/{owner}/{repo}
authenticated git push
.forgejo/workflows/*.yml
runner label matches runs-on
GET /repos/{owner}/{repo}/actions/runs
GET /repos/{owner}/{repo}/actions/tasks

Refresh and verify

From this skill directory:

scripts/fetch-forgejo-swagger.sh https://v15.next.forgejo.org

FORGEJO_TOKEN=... scripts/verify-forgejo-skill.sh https://v15.next.forgejo.org ANcpLua qyl

Without FORGEJO_TOKEN, verification still checks documented routes against Swagger and skips private repo probes.