mo-user

Prerequisites

CRITICAL — Read first 共享规则, which contains mocli initialization, authentication, output parsing, and security rules

mocli user - Mowen user

mocli user info --uid [--note]

This command is used to get information about a specified Mowen user.--uid is a required parameter;--note helps the Agent summarize the user portrait by additionally returning a small sample of notes from the user's homepage.

When to use

• Use this command when the user explicitly wants to "view user information / get user profile / check user details for a certain UID."
• Use this command when the user has already provided a UID and wants to view that user's basic profile, following count, follower count, or note count.
• When the user wants to learn about the user's creative field, creative direction, popular works, which columns/collections they have released, whether they have paid content, and other portrait information, add --note to get samples before summarizing.
• When the user explicitly queries the profile or information of a certain user, use --noteby default; this way, in addition to the basic profile, it can more completely portray "what kind of creator this user is."
• If the user only provides a nickname, name, or alias, first resolve the UID according to the general process of mo-shared : prioritize using mo-remark, and if there is no match, use mocli user search or ask the user to provide the UID.

Optional parameters:

• --uid string: Target user UID (required).
• --note: Includes a small sample of notes from the user's homepage, used to assist in summarizing the user portrait. Not included by default in the CLI; the Agent includes it by default when explicitly querying a single user's profile.

Usage examples

• Get information/profile for the user with UID Qiz5hxiY5wr5L76fyd8Kv user information/bio mocli user info --uid "Qiz5hxiY5wr5L76fyd8Kv" --note
• Introduce Mowen "Erye"mocli user info --uid "Qiz5hxiY5wr5L76fyd8Kv" --note
• See what kind of creator Mowen "Lao Chi" is mocli user info --uid "Qiz5hxiY5wr5L76fyd8Kv" --note

Output example

{
  "code": 0,
  "status": "OK",
  "reply": {
    "info": {
      "uid": "Qiz5hxiY5wr5L76fyd8Kv",
      "name": "精卫鸟.",
      "intro": "一只小小鸟，订阅我的没几个人，所以你们都是特殊的。。",
      "home_url": "https://mowen.cn/u/Qiz5hxiY5wr5L76fyd8Kv",
      "regist_at": 1700000000
    },
    "counter": {
      "user_follow": 12,
      "user_follower": 345,
      "note_pub": 28,
      "note_fee": 3,
      "note_album": 2
    },
    "note_idx": {
      "note_top": ["note-top-1"],
      "note_pub": ["note-pub-1", "note-pub-2"],
      "note_fee": ["note-fee-1"],
      "note_album": ["note-album-1"],
      "note_popular": ["note-popular-1"]
    },
    "notes": {
      "note-top-1": {
        "note_id": "note-top-1",
        "uid": "Qiz5hxiY5wr5L76fyd8Kv",
        "title": "置顶笔记",
        "brief": "这是一条置顶笔记摘要",
        "url": "https://note.mowen.cn/detail/note-top-1?from=mocli"
      }
    }
  }
}

reply field descriptions

Field	Type	Description	Reference field
info	UserInfo	Target user basic information.	UserInfo - 用户信息
counter	object	User count information, including following count, follower count, public note count, paid note count, and collection count.	-
note_idx	object	Category index of a small sample of notes from the user's homepage. Only returned when using --note ; each category usually returns only a few items, and does not represent the complete list.	-
notes	map[string]NoteInfo	Note sample information Map, where the key is the note ID and the value is the note information. Only returned when using --note , used to assist in determining creative direction.	NoteInfo - 笔记信息

counter subfields

Field	Description
user_follow	The number of people the target user follows, which can help determine their information sources and social activity.
user_follower	The number of people following the target user, which can help determine their audience size and influence.
note_pub	Number of public notes, indicating the scale of the user's public creations.
note_fee	Number of paid notes, indicating whether the user has paid content offerings and the scale of paid content.
note_album	Number of collections/columns, indicating whether the user creates serialized content around themes.

note_idx subfields

Field	Description
note_top	Pinned note samples, which usually represent content the user actively highlights and can be prioritized for judging the creator's self-positioning.
note_pub	Public note samples, reflecting the user's recent or regular public creative content on their homepage.
note_fee	Paid note samples, reflecting the user's paid columns, paid topics, or commercialization content directions.
note_album	Collection/column note samples, reflecting which serialized topics, courses, columns, or content collections the user has created.
note_popular	Popular note samples, reflecting content directions that have attracted more reader attention and can help judge audience preferences.

Result parsing rules

• When displaying user profile information, prioritize displaying reply.info.name、reply.info.uid、reply.info.intro；reply.info.home_url link display follows the shared display rules.
• When displaying counts, read the following, follower, public note, paid note, and collection counts from reply.counter ; do not fabricate when fields are missing.
• When explicitly querying a single user's profile, execute mocli user info --uid <uid> --noteby default, unless the user requests only basic information or wants to save request cost.
• After using --note , do not treat note_idx / notes as a complete homepage note list; they are only profile sampling data, and each category usually covers only the first several items.
• The profile summary should synthesize reply.info、reply.counter、reply.note_idx and reply.notes: summarize the creative field, content directions, columns/collections, and paid content characteristics from titles, summaries, collection/paid categories, and popular/pinned samples.
• When outputting to the user, prioritize giving a summary profile; you may cite a small number of representative note titles as evidence, but do not list them one by one as a "homepage note list."
• If --note after note_idx or notes is empty, clearly state "no note samples available for profiling were returned," and do not fill it in with search or homepage list results.

Display suggestions

• Basic profile: display info.name、info.uid、info.intro；info.home_url link display follows the shared display rules. When the bio is empty, state that the user has not filled in a bio; do not write one yourself.
• Registration time: display info.regist_at; if it is empty or is 0, simply skip it.
• Membership information: if info.member.is_member is true, you may briefly display the membership status; do not display or infer membership benefits, payment amounts, or other information not returned.
• Count information: read the following, follower, public note, paid note, and collection counts from counter ; do not fabricate when fields are missing.
• Creative profile: use --note returned by note_idx and notes for sampling summary, prioritizing the titles and summaries of pinned, popular, collection/column, and paid note samples.
• Representative content: you may select a small number of note titles and links as evidence in the order of note_idx.note_top、note_idx.note_popular、note_idx.note_album、note_idx.note_fee、note_idx.note_pub ; when the same note ID appears repeatedly, display it only once.
• When displaying notes, try to make the title a link, or attach notes[note_id].urlnext to the title; if a link is missing, display only the title and note ID.
• Sample boundaries:note_idx / notes are only a small number of homepage samples and do not represent the complete homepage, all works, or the complete paid content list; do not use sample counts to replace the counts in counter .
• Missing field handling:counter、note_idx、notes、info.member may all be empty; skip missing parts when displaying, and avoid repeatedly calling for multiple samples just to complete the profile. mocli user info --uid ... --note。

mocli user search [--keyword] [--count] [--filter]

This command is used to search for MoWen users by keyword.--keyword is a required parameter;--filter is used to limit the search scope (all, people I follow, people who follow me, mutual followers).

When to use

• Use this command when the user explicitly wants to "search for users/find people/look up a certain MoWen user".
• When another skill needs a UID, and mo-remark does not match a note, this command can be used to help find candidate users.
• If the search results contain multiple similar users, do not choose on your own; show the candidate users' name、uid、intro, and ask the user to confirm.

Optional parameters:

• --keyword string: Search keyword (required).
• --count int: Number of users to return. Range:1-100. Default:20。
• --filter string: Search scope. Supported:all(全部)、following(我关注的人)、follower(关注我的人)、friend(好友，即相互关注的人). Default:all。

Usage examples

• Search for the user named "Lao Chi" in MoWen mocli user search --keyword "老池"
• Search for 10 users whose names contain "AI" in MoWen mocli user search --keyword "AI" --count 10
• Search for the user named "Er Ye" in my MoWen following list mocli user search --keyword "二爷" --filter following
• Search for the user named "Sheji" among my MoWen friends mocli user search --keyword "设计" --filter friend

Output example

{
  "code": 0,
  "status": "OK",
  "reply": {
    "uids": [
      "Qiz5hxiY5wr5L76fyd8Kv",
      "9z8YxxxxxxXx9xXxXxXxX"
    ],
    "users": {
      "Qiz5hxiY5wr5L76fyd8Kv": {
        "uid": "Qiz5hxiY5wr5L76fyd8Kv",
        "name": "精卫鸟.",
        "intro": "一只小小鸟，订阅我的没几个人，所以你们都是特殊的。。"
      },
      "9z8YxxxxxxXx9xXxXxXxX": {
        "uid": "9z8YxxxxxxXx9xXxXxXxX",
        "name": "池老师",
        "intro": "AI 产品实践者"
      }
    }
  }
}

reply field description

Field	Type	Description	Reference field
uids	array	Ordered list of user UIDs. When users need to be displayed in search order, iterate through this field first.	-
users	map[string]UserInfo	User information Map, with keys as user UIDs and values as user information. It can be used to display in order based on uids , or to quickly query user details by UID.	UserInfo - 用户信息

Result parsing rules

• When displaying search results, iterate first in the order of reply.uids , then go to reply.users[uid] to get details.
• If there is only one high-confidence result and the user's subsequent task needs a UID, you can directly use that UID to continue execution.
• If there are multiple candidates or similar names, display the candidates first and ask the user to confirm; do not guess on your own based on the name.
• In list scenarios such as user search and following lists, do not call mocli user info --uid ... --noterepeatedly just to enrich the information of each item; this will trigger rate limiting and consume quota. Only when the user explicitly requests analysis of a certain candidate user should you call user info。
• on that single UID.

If there are no results, state that no matching user was found, and suggest that the user provide a more accurate nickname, UID, or search scope.

** Reference ** 公共展示规则