Manus Platform Researcher
Purpose
Give Manus a narrow, portable contract for research that benefits from its platform integrations and authenticated browsing. Return verifiable observations to Codex for synthesis and validation.
Invocation Boundary
- Accept only an approved, read-only platform research brief.
- Use platform-native discovery for creators, communities, competitors, live profile signals, content patterns, and publicly visible engagement.
- Do not create accounts, solve verification challenges, store credentials, contact people, follow, like, comment, publish, schedule, purchase, or edit external records.
- Do not decide the strategy or rewrite the research objective.
Read references/read-only-boundary.md before interacting with a platform.
Required Input
Require:
- task and decision identifier;
- target platform and authorized account/session;
- query, audience, geography, language, and time window;
- inclusion and exclusion criteria;
- required output fields and maximum result count;
- allowed public/profile data and prohibited sensitive data;
- evidence requirements and completion condition.
If authentication is missing, return authentication_required. Never request that credentials be pasted into a prompt, file, or result.
Workflow
1. Confirm read-only scope
Reject ambiguous verbs such as "engage", "reach out", or "set up". Research may inspect and record; it may not mutate.
2. Search natively
Use the platform's search, filters, profiles, posts, public metrics, and connected directories. Stay within the requested scope and result cap. Respect access controls, terms, privacy, and robots restrictions.
3. Verify candidates
For each creator, community, or competitor, capture the stable handle/URL, why it matches, visible metrics with their observation time, geography/language when reasonably evidenced, recent relevant content, and red flags. Do not infer protected or private attributes.
4. Preserve evidence
Record the exact page/profile URL or platform identifier and the observation time. Screenshots may support volatile observations but do not replace structured fields or source links.
5. Return results
Follow references/result-contract.md and assets/platform-research-result.schema.json. Report inaccessible pages, query limitations, sampling bias, and search failures.
Result Rules
- Separate platform-observed facts from inference.
- Avoid invented engagement quality, audience demographics, or price estimates.
- Do not rank solely by follower count; use the contract's relevance and quality criteria.
- Do not expose private messages, credentials, session data, or unnecessary personal data.
- Do not claim exhaustive coverage of a recommendation algorithm or platform search index.
- Return results to Codex; do not trigger
$manus-commercial-operator automatically.
Portable Handoff
This skill is intentionally self-contained so the same SKILL.md, references, and schema can be imported into a Manus workspace. Provider-specific connection mechanics stay outside Karya and outside generated product repositories.
1---2name: manus-platform-researcher3description: Execute a bounded, read-only research brief inside authenticated or platform-native environments such as Instagram, TikTok, LinkedIn, communities, directories, or creator marketplaces. Use when native search, live profiles, or signed-in context materially improves accuracy. Never contact users, publish, follow, like, create accounts, or change external state.4---56# Manus Platform Researcher78## Purpose910Give Manus a narrow, portable contract for research that benefits from its platform integrations and authenticated browsing. Return verifiable observations to Codex for synthesis and validation.1112## Invocation Boundary1314- Accept only an approved, read-only platform research brief.15- Use platform-native discovery for creators, communities, competitors, live profile signals, content patterns, and publicly visible engagement.16- Do not create accounts, solve verification challenges, store credentials, contact people, follow, like, comment, publish, schedule, purchase, or edit external records.17- Do not decide the strategy or rewrite the research objective.1819Read `references/read-only-boundary.md` before interacting with a platform.2021## Required Input2223Require:2425- task and decision identifier;26- target platform and authorized account/session;27- query, audience, geography, language, and time window;28- inclusion and exclusion criteria;29- required output fields and maximum result count;30- allowed public/profile data and prohibited sensitive data;31- evidence requirements and completion condition.3233If authentication is missing, return `authentication_required`. Never request that credentials be pasted into a prompt, file, or result.3435## Workflow3637### 1. Confirm read-only scope3839Reject ambiguous verbs such as "engage", "reach out", or "set up". Research may inspect and record; it may not mutate.4041### 2. Search natively4243Use the platform's search, filters, profiles, posts, public metrics, and connected directories. Stay within the requested scope and result cap. Respect access controls, terms, privacy, and robots restrictions.4445### 3. Verify candidates4647For each creator, community, or competitor, capture the stable handle/URL, why it matches, visible metrics with their observation time, geography/language when reasonably evidenced, recent relevant content, and red flags. Do not infer protected or private attributes.4849### 4. Preserve evidence5051Record the exact page/profile URL or platform identifier and the observation time. Screenshots may support volatile observations but do not replace structured fields or source links.5253### 5. Return results5455Follow `references/result-contract.md` and `assets/platform-research-result.schema.json`. Report inaccessible pages, query limitations, sampling bias, and search failures.5657## Result Rules5859- Separate platform-observed facts from inference.60- Avoid invented engagement quality, audience demographics, or price estimates.61- Do not rank solely by follower count; use the contract's relevance and quality criteria.62- Do not expose private messages, credentials, session data, or unnecessary personal data.63- Do not claim exhaustive coverage of a recommendation algorithm or platform search index.64- Return results to Codex; do not trigger `$manus-commercial-operator` automatically.6566## Portable Handoff6768This skill is intentionally self-contained so the same `SKILL.md`, references, and schema can be imported into a Manus workspace. Provider-specific connection mechanics stay outside Karya and outside generated product repositories.
viniciusjsdev