Run any Skill in Manus with one click

research-new

Stars4

Forks0

UpdatedJuly 11, 2026 at 19:54

Create a user-research note (interviews, usability test, survey, discovery) in 09-knowledge/research/ from the user-research template. Use when the user wants to plan or capture user research, customer interviews, usability testing, or discovery findings. Pass the study topic and optionally its project as args (e.g. "Onboarding interviews for payments-platform").

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

trustmaster

trustmaster/emos

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Market Research Analysts and Marketing SpecialistsBusiness and Financial Operations Occupations·SOC 13-1161

SKILL.md

readonly

name	research-new
description	Create a user-research note (interviews, usability test, survey, discovery) in 09-knowledge/research/ from the user-research template. Use when the user wants to plan or capture user research, customer interviews, usability testing, or discovery findings. Pass the study topic and optionally its project as args (e.g. "Onboarding interviews for payments-platform").

Create a user-research note in the knowledge base.

Read paths.knowledge_research (default 09-knowledge/research), paths.projects (default 03-projects), and owner.slug from .agents/config.yaml.

Determine the study topic from args and generate a slug (lowercase, hyphen-separated, max 6 words).
Resolve project association (optional). If args names a project (or one obviously applies), set projects: [slug] — validate each slug exists as a folder in {paths.projects}/. If none is stated but the topic could belong to an active project, ask which project(s) it informs; accept "none". A populated projects: makes the note surface in those projects' hub rollups under Knowledge on the next project-sync.
Read _templates/user-research.md.
Create {paths.knowledge_research}/{YYYY-MM-DD}-{slug}.md (today's date), creating the {paths.knowledge_research}/ folder if it doesn't exist.
Write the file from the template with frontmatter filled:
- title: from args
- slug: the slug
- status: planned
- owner: {{owner_slug}} resolved from config
- projects: the resolved slug array (else [])
- date: today's date
- leave method, participants as prompts/empty
- Keep the goal, findings, and insight sections as prompts to fill; preserve the append-only ## Raw notes log.
- Do not record PII — reference participants as P1, P2, … and keep names/contact details out of the file (the template says so; enforce it if the user pastes raw contacts).
Add - [ ] Run/synthesize research: {topic} #follow-up{project-tag} to the current week's active file in 01-weekly/, appending #project/{slug} for each linked project.
If any project was linked, offer to run project-sync {slug} now.

Output the created file path and any linked project(s).

More from this repository

same repository

create-github-issue

trustmaster/emos

Create a new GitHub issue (optionally added to a GitHub Project board) following the project's standard format — gathers the details, shows a draft for confirmation, then creates it via the `gh` CLI. Use when the user wants to file, open, or create a GitHub issue. Optionally pass the repo and/or issue title as args.

2026-07-164

github-browse

trustmaster/emos

Explore a remote GitHub repository read-only via the `gh` CLI — search code, read a file at a ref, view repo structure, trace the history/PRs touching a path, and blame lines. Use when investigating an incident or working an assignment against code you don't have checked out, across one or more repos. Pass the repo(s) (`owner/repo`) and what you're looking for as args.

2026-07-164

github-pr-fetch

trustmaster/emos

Fetch a GitHub pull request as a structured bundle (metadata, diff, changed files with stats, commits, CI/check status, and existing review comments) via the `gh` CLI. Transport-only — it retrieves, it does not judge. Used by the tool-agnostic `pr-review` skill; you normally won't invoke it directly. Pass a PR number, URL, or branch (and optionally `owner/repo`) as args.

2026-07-164

github-sync

trustmaster/emos

Sync a GitHub Project board into an emOS report grouped by status. Use when the user wants an up-to-date snapshot of a GitHub Projects (v2) board pulled into 10-reports/. Optionally pass a project number/URL, an owner, or a status filter as args.

2026-07-164

pr-review

trustmaster/emos

Do a first-line review pass on a pull request — summarize the changes, flag obvious issues, highlight architectural/dependency changes, and escalate what needs human attention. It hands you structured input to act on; it does NOT auto-approve or post to the code host. Use when the user wants a PR reviewed, triaged, or summarized before they dig in. Pass a PR number, URL, or branch as args.

2026-07-164

import-url

trustmaster/emos

Import any document by URL into emOS. Detects the transport (Confluence, Google Docs, GitHub, or a generic web page), delegates to the medium-specific provider skill when its capability is configured, classifies the content, files it, and pulls any action items assigned to the owner into the current week's plan. Use when the user gives a URL and wants its content brought into the vault. Pass the URL (and optionally a hint about the doc type) as args.

2026-07-124

name	research-new
description	Create a user-research note (interviews, usability test, survey, discovery) in 09-knowledge/research/ from the user-research template. Use when the user wants to plan or capture user research, customer interviews, usability testing, or discovery findings. Pass the study topic and optionally its project as args (e.g. "Onboarding interviews for payments-platform").

Create a user-research note in the knowledge base.

Read paths.knowledge_research (default 09-knowledge/research), paths.projects (default 03-projects), and owner.slug from .agents/config.yaml.

Determine the study topic from args and generate a slug (lowercase, hyphen-separated, max 6 words).
Resolve project association (optional). If args names a project (or one obviously applies), set projects: [slug] — validate each slug exists as a folder in {paths.projects}/. If none is stated but the topic could belong to an active project, ask which project(s) it informs; accept "none". A populated projects: makes the note surface in those projects' hub rollups under Knowledge on the next project-sync.
Read _templates/user-research.md.
Create {paths.knowledge_research}/{YYYY-MM-DD}-{slug}.md (today's date), creating the {paths.knowledge_research}/ folder if it doesn't exist.
Write the file from the template with frontmatter filled:
- title: from args
- slug: the slug
- status: planned
- owner: {{owner_slug}} resolved from config
- projects: the resolved slug array (else [])
- date: today's date
- leave method, participants as prompts/empty
- Keep the goal, findings, and insight sections as prompts to fill; preserve the append-only ## Raw notes log.
- Do not record PII — reference participants as P1, P2, … and keep names/contact details out of the file (the template says so; enforce it if the user pastes raw contacts).
Add - [ ] Run/synthesize research: {topic} #follow-up{project-tag} to the current week's active file in 01-weekly/, appending #project/{slug} for each linked project.
If any project was linked, offer to run project-sync {slug} now.

Output the created file path and any linked project(s).