Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

research

Sterne6

Forks0

Aktualisiert23. Juli 2026 um 17:10

Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

appelgriebsch

appelgriebsch/dotFiles

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

description	Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.
metadata	{"github-path":"skills/engineering/research","github-ref":"refs/tags/v1.1.0","github-repo":"https://github.com/mattpocock/skills","github-tree-sha":"06c848c1a1f3ae7afd88f040f73a8f3efee3494d"}
name	research

Spin up a background agent to do the research, so you keep working while it reads.

Its job:

Investigate the question against primary sources — official docs, source code, specs, first-party APIs — not a secondary write-up of them. Follow every claim back to the source that owns it.
Write the findings to a single Markdown file, citing each claim's source.
Save it where the repo already keeps such notes; match the existing convention, and if there is none, put it somewhere sensible and say where.

Mehr aus diesem Repository

gleiches Repository

ask-the-expert

appelgriebsch/dotFiles

Use this skill whenever a task would benefit from authoritative, technology-specific input beyond generalist knowledge — for example during code review, implementation planning, or troubleshooting, whenever the code, design, or issue touches Rust, Bun runtime TypeScript/JavaScript, Java/Spring Cloud microservices, GIS/geospatial processing, web front-end code, or Datadog observability data. This skill identifies the relevant expert sub-agent(s) for the technology or domain in scope, delegates to them via the Task tool, and synthesizes their findings into a single, actionable answer for the calling skill or user.

2026-07-246

appelgriebsch/dotFiles

Use the ax CLI instead of curl + throwaway parsing scripts whenever you fetch a URL, explore an unknown web page, or extract structured data from HTML. Trigger whenever you are about to write an inline script (python3 heredoc, node -e, regex over HTML) or a bare curl for one-off web fetching, scraping, or page exploration.

2026-07-246

brainstorm

appelgriebsch/dotFiles

This skill analyzes a given improvement ticket or idea and provides a detailed plan on how to implement it. It gathers relevant information from the ticket or request, including context, requirements, and constraints, and generates a step-by-step implementation plan. The skill also identifies potential challenges, required tests, and validation steps, and can assist in creating prototypes or breaking down the implementation into smaller tasks or milestones. When the implementation touches a technology with a dedicated expert (e.g. Rust, Bun/TypeScript, Java/Spring Cloud, GIS, web front-end, or Datadog observability), it consults the `ask-the-expert` skill to validate the proposed approach, risks, and tradeoffs before finalizing the plan.

2026-07-246

code-review

appelgriebsch/dotFiles

Use this skill when the user wants recently written or modified code reviewed, needs targeted feedback on code quality, security, performance, idiomatic usage, or architecture, or has specific technical questions about their codebase. This skill delegates to the `ask-the-expert` skill to identify the languages and technologies involved and consult the appropriate specialized experts, then synthesizes their findings into a single, prioritized review.

2026-07-246

troubleshoot

appelgriebsch/dotFiles

This skill analyzes a given problem or issue and provides a detailed troubleshooting plan to resolve it. It gathers relevant information from the problem description, including context, symptoms, and constraints, and generates a step-by-step troubleshooting plan. The skill also identifies potential causes, required tests, and validation steps, and can assist in creating prototypes or breaking down the troubleshooting into smaller tasks or milestones. When the issue touches a technology with a dedicated expert (e.g. Rust, Bun/TypeScript, Java/Spring Cloud, GIS, web front-end, or Datadog observability), it consults the `ask-the-expert` skill for root-cause input before finalizing the plan.

2026-07-246

writing-great-skills

appelgriebsch/dotFiles

Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.

2026-07-246

description	Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.
metadata	{"github-path":"skills/engineering/research","github-ref":"refs/tags/v1.1.0","github-repo":"https://github.com/mattpocock/skills","github-tree-sha":"06c848c1a1f3ae7afd88f040f73a8f3efee3494d"}
name	research

Spin up a background agent to do the research, so you keep working while it reads.

Its job:

Investigate the question against primary sources — official docs, source code, specs, first-party APIs — not a secondary write-up of them. Follow every claim back to the source that owns it.
Write the findings to a single Markdown file, citing each claim's source.
Save it where the repo already keeps such notes; match the existing convention, and if there is none, put it somewhere sensible and say where.