Preconditions

CRITICAL — Read
Shared Rules
first, which includes
mocli
initialization, authentication, output parsing, and security rules

mocli discover - Mowen Discover & Activity

mocli disco activity [--recent]

This skill is used to view the Mowen activities of the currently authenticated user, including activities like being liked, being commented (or replied to), being followed, being collected, followed users publishing new notes, followed users publishing paid notes/collections, etc. This command only reads activities and does not perform write or delete operations.

Usage Principles

Use this command when the user wants to view "my activities/who liked, commented, followed me recently/what did followed users post".
When displaying, must take
```
reply.events
```
as the main sequence; for each event, use
```
eid
```
to find supplementary information in detail Maps such as
```
favors
```
,
```
comments
```
,
```
follow_notes
```
,
```
follow_fee_notes
```
.
Do not directly traverse the detail Maps to display activities, otherwise the original order will be lost.
Note IDs in activity details (such as
```
target_id
```
,
```
note_id
```
,
```
joins
```
) should be supplemented with title, abstract and link from
```
reply.notes
```
.
User UIDs in activity details (such as
```
favor_uid
```
,
```
cmt_uid
```
,
```
note_uid
```
) should be supplemented with nicknames from
```
reply.users
```
.

Optional Parameters:

```
--recent string
```
: Time range. Supported values:
```
today
```
,
```
yesterday
```
,
```
1h-24h
```
. Defaults to
```
1h
```
if not specified.

Usage Examples

View my latest Mowen activities:
```
mocli disco activity
```
View today's Mowen activities:
```
mocli disco activity --recent today
```
View yesterday's Mowen activities:
```
mocli disco activity --recent yesterday
```
View Mowen activities in the last 3 hours:
```
mocli disco activity --recent 3h
```
View Mowen activities in the last 24 hours:
```
mocli disco activity --recent 24h
```

Parameter Selection Rules

When the user says "today", use
```
--recent today
```
.
When the user says "yesterday", use
```
--recent yesterday
```
.
When the user says "recent N hours" and
```
N
```
is within the range of 1-24, use
```
--recent Nh
```
, e.g.,
```
--recent 6h
```
.
If the user provides an hour count exceeding
```
24h
```
, or requests filtering by days other than
```
today/yesterday
```
, inform the user that the current command only supports
```
today
```
,
```
yesterday
```
,
```
1h-24h
```
, and ask if they want to switch to a supported range.

Output Example

{
  "code": 0,
  "status": "OK",
  "reply": {
    "events": [
      {
        "eid": 2049020870318682148,
        "uid": "gMiYUcJU0GjBfKIMTmzeN",
        "type": 6,
        "sub_type": 1,
        "happened_at": 1777305989850
      }
    ],
    "follows": {},
    "favors": {
      "2048799112739434497": {
        "favor_uid": "2dsiQjSN3hrWhQu3W8nEx",
        "target_uid": "vtv_PV1fEMBb-8_BPlmDu",
        "target_id": "rdIP8aEyBDz_c38q3h0TC"
      }
    },
    "collects": {},
    "comments": {
      "2048795933738192897": {
        "cmt_uid": "0W1rAu9TJPU9ZFy_eOgqv",
        "cmt_id": "td2dQ5WXhKKD-h4PeN-Ks",
        "cmt_p_uid": "",
        "cmt_p_id": "",
        "target_uid": "vtv_PV1fEMBb-8_BPlmDu",
        "target_id": "rdIP8aEyBDz_c38q3h0TC"
      },
      "2048797711351394305": {
        "cmt_uid": "ua2x-_O32fcaYuURPi1Eo",
        "cmt_id": "eITFJYXSaElv_vIrVIeYs",
        "cmt_p_uid": "vtv_PV1fEMBb-8_BPlmDu",
        "cmt_p_id": "Eh8fTXFO-442JBUEmWCk4",
        "target_uid": "vtv_PV1fEMBb-8_BPlmDu",
        "target_id": "45JqKC3Y5PvSCj0htokSW"
      }
    },
    "trades": {},
    "follow_notes": {
      "2049020870318682148": {
        "note_id": "KS1x1z500bkEZa-PhsfQG",
        "note_uid": "0PoXMWF-V43tuXOOu-7Yw",
        "joins": []
      },
      "2048900500857122935": {
        "note_id": "iHQFI49mKnP8RclPopQSK",
        "note_uid": "_hA8gaYCCpwPkfpPhA4cA",
        "joins": [
          "GCwHPvJkl5Ox4lVB7fUWH"
        ]
      }
    },
    "follow_fee_notes": {
      "2049020870318682148": {
        "note_id": "KS1x1z500bkEZa-PhsfQG",
        "note_uid": "0PoXMWF-V43tuXOOu-7Yw",
        "joins": []
      },
      "2048900500857122935": {
        "note_id": "iHQFI49mKnP8RclPopQSK",
        "note_uid": "_hA8gaYCCpwPkfpPhA4cA",
        "joins": [
          "GCwHPvJkl5Ox4lVB7fUWH"
        ]
      }
    },
    "notes": {
      "3jv1AiAjXJ4aBC83LqdMC": {
        "note_id": "3jv1AiAjXJ4aBC83LqdMC",
        "uid": "Qiz5hxiY5wr5L76fyd8Kv",
        "title": "最近心情",
        "brief": "笔记摘要",
        "url": "https://note.mowen.cn/detail/3jv1AiAjXJ4aBC83LqdMC?from=mocli"
      },
      "ZVDGaChlin5voLpIp_9TM": {
        "note_id": "ZVDGaChlin5voLpIp_9TM",
        "uid": "Qiz5hxiY5wr5L76fyd8Kv",
        "title": "大家好呀，我是小白",
        "brief": "笔记摘要",
        "url": "https://note.mowen.cn/detail/ZVDGaChlin5voLpIp_9TM?from=mocli"
      }
    },
    "users": {
      "Qiz5hxiY5wr5L76fyd8Kv": {
        "uid": "xxxxxxxxxxxxxx",
        "name": "精卫鸟.",
        "intro": "一只小小鸟，订阅我的没几个人，所以你们都是特殊的。。"
      }
    }
  }
}

Reply Field Description

Field	Type	Description	Reference Field
`events`	array	Ordered list of activity events. When displaying activities, you should traverse this field first, then retrieve data from the corresponding detail Map based on each event's `eid` .	`ActivityEvent - Activity Event`
`follows`	map[string]object	Detail Map for follow events, usually keyed by event `eid` . Used to display who followed the current user.	-
`favors`	map[string]ActivityEventFavor	Detail Map for like events, usually keyed by event `eid` . Used to display who liked which note.	`ActivityEventFavor - Like Activity`
`collects`	map[string]object	Detail Map for collect events, usually keyed by event `eid` . Used to display who collected which note.	-
`comments`	map[string]ActivityEventComment	Detail Map for comment events, usually keyed by event `eid` . Used to display who commented/replied to which note.	`ActivityEventComment - Comment Activity`
`trades`	map[string]object	Detail Map for transaction/paid-related events, usually keyed by event `eid` . Used to display who purchased the current user's notes or columns.	-
`follow_notes`	map[string]ActivityEventFollowNote	Detail Map for events where followed users of the current user published regular notes (empty `joins` ) or updated collections (non-empty `joins` ), keyed by event `eid` .	`ActivityEventFollowNote - Followed Note Activity`
`follow_fee_notes`	map[string]ActivityEventFollowFeeNote	Detail Map for events where followed users of the current user published paid notes (empty `joins` ) or updated paid collections (non-empty `joins` ), keyed by event `eid` .	`ActivityEventFollowFeeNote - Followed Paid Note Activity`
`notes`	map[string]NoteInfo	Map of note information, keyed by note ID. When fields representing note IDs such as `note_id` , `target_id` , `joins` appear in activity details, use this field to supplement note title, abstract, link, etc.	`NoteInfo - Note Information`
`users`	map[string]UserInfo	Map of user information, keyed by user UID. Used to supplement user information such as event initiators and note authors.	`UserInfo - User Information`

ActivityEvent - Activity Event

Field	Type	Description
`eid`	integer/string	Event ID. Used to look up event details in detail Maps like `follows` , `favors` , `collects` , `comments` , `trades` , `follow_notes` , `follow_fee_notes` . Note that it may appear as a number or string during JSON parsing; it's safer to convert it to a string uniformly when associating.
`uid`	string	User UID related to the event. Retrieve nickname, intro, etc. from `users[uid]` .
`type`	integer	Event type. `1` = Like event, `2` = Comment/reply event, `3` = Collect event, `4` = Follow event, `5` = Transaction event, `6` = Followed user published note or updated collection, `7` = Followed user published paid note or updated paid collection
`happened_at`	integer	Event occurrence time. Usually a millisecond-level timestamp; need to format it into readable time before displaying.

ActivityEventFavor - Like Activity

Field	Type	Description
`favor_uid`	string	UID of the user who liked. Retrieve nickname, intro, etc. of the liking user from `users[favor_uid]` .
`target_uid`	string	UID of the author of the liked note. Usually the currently authenticated user; you can also retrieve author information from `users[target_uid]` .
`target_id`	string	ID of the liked note. Retrieve note title, abstract, link, etc. from `notes[target_id]` .

Like Display Rules

Priority display copy:

users[favor_uid].name

liked

notes[target_id].title

If
```
notes[target_id]
```
does not exist, still display
```
target_id
```
and do not discard the event.
If
```
users[favor_uid]
```
does not exist, display the UID.

ActivityEventComment - Comment Activity

Field	Type	Description
`cmt_uid`	string	UID of the comment initiator. Retrieve nickname, intro, etc. of the commenting user from `users[cmt_uid]` .
`cmt_id`	string	Comment ID. The current activity list usually only provides the comment ID, not necessarily the comment content.
`cmt_p_uid`	string	UID of the author of the replied comment. Empty means it's a direct comment on the note; non-empty means it's a reply to someone's comment.
`cmt_p_id`	string	ID of the replied comment. Empty means it's a direct comment on the note; non-empty means it's a reply to a specific comment.
`target_uid`	string	UID of the author of the commented note. Usually the currently authenticated user; you can also retrieve author information from `users[target_uid]` .
`target_id`	string	ID of the commented note. Retrieve note title, abstract, link, etc. from `notes[target_id]` .

Comment Display Rules

When

cmt_p_id

is empty, display as:

users[cmt_uid].name

commented on

notes[target_id].title

When

cmt_p_id

is non-empty, display as:

users[cmt_uid].name

replied to

users[cmt_p_uid].name

's comment under

notes[target_id].title

If the comment content is not in
```
comments[eid]
```
, do not fabricate content; only display the comment ID
```
cmt_id
```
and associated note information.
If
```
notes[target_id]
```
or related user information is missing, retain the ID for display.

ActivityEventFollowNote - Followed Note Activity

Field	Type	Description
`note_id`	string	Main note ID. Retrieve title, abstract, link, etc. from `notes[note_id]` .
`note_uid`	string	UID of the author of the main note. Retrieve author information from `users[note_uid]` .
`joins`	array[string]	List of associated note IDs, usually used in collection update scenarios, representing the note IDs added to the main note. Retrieve the title of each sub-note from `notes[join_note_id]` .

ActivityEventFollowFeeNote - Followed Paid Note Activity

Current fields are consistent with

ActivityEventFollowNote

, but semantically independent: this structure is only used for

follow_fee_notes

, indicating that followed users published paid notes or updated paid collections. If fields such as price, order, permissions are added to paid activities in the future, this structure should be extended instead of merging into

ActivityEventFollowNote

Field	Type	Description
`note_id`	string	ID of the main paid note or paid collection. Retrieve title, abstract, link, etc. from `notes[note_id]` .
`note_uid`	string	UID of the author of the main paid note. Retrieve author information from `users[note_uid]` .
`joins`	array[string]	List of associated note IDs, usually used in paid collection update scenarios, representing the note IDs added to the main paid collection. Retrieve the title of each sub-note from `notes[join_note_id]` .

Activity Parsing Rules

Use the order of
```
reply.events
```
as the display order; do not directly traverse various detail Maps.
For each event, convert
```
eid
```
to a string, then search for corresponding details in
```
follows
```
,
```
favors
```
,
```
collects
```
,
```
comments
```
,
```
trades
```
,
```
follow_notes
```
,
```
follow_fee_notes
```
in sequence.
If
```
favors[eid]
```
is hit, display as a certain user liked a certain note; use
```
favor_uid
```
to find the liking user,
```
target_id
```
to find the note, and
```
target_uid
```
to find the note author.
If
```
comments[eid]
```
is hit, display as a certain user commented or replied to a certain note; use
```
cmt_uid
```
to find the commenting user,
```
target_id
```
to find the note; when
```
cmt_p_id
```
is non-empty, use
```
cmt_p_uid
```
to find the replied user.
If
```
follow_notes[eid]
```
is hit, display as the current user's followed user published a new note or updated a collection; use
```
note_uid
```
to find the author,
```
note_id
```
to find the note title, abstract and link; if
```
joins
```
is not empty, use the note IDs in
```
joins
```
to find the title, abstract and link of sub-notes.
If
```
follow_fee_notes[eid]
```
is hit, display as the current user's followed user published a paid note or updated a paid collection; use
```
note_uid
```
to find the author,
```
note_id
```
to find the note title, abstract and link; if
```
joins
```
is not empty, use the note IDs in
```
joins
```
to find the title, abstract and link of sub-notes.
If collect, follow, transaction, etc. Maps are hit, prioritize using fields like UID, note_id, target_id, comment/content in the detail object, and supplement nicknames and note titles through
```
users
```
and
```
notes
```
.
If an event does not hit any detail Map, do not discard it; display the event ID, user, type, occurrence time, and indicate that this event type is not yet recognized.
The timestamp
```
happened_at
```
may be microsecond-level; when formatting, you need to judge by length/value to avoid mistaking it for a second-level timestamp.

Display Suggestions

When there is little data, display each item in reverse chronological order: time, activity type, user, note title, abstract, link.
When there is a lot of data, you can first summarize the quantity by type, then list the recent key activities.
Prioritize using
```
notes[note_id].title
```
for the note title; if the title itself does not contain「」or『』, wrap it with『』; prioritize using
```
users[note_uid].name
```
for the author.
For paid notes/collections, if
```
flag.with_fee
```
is true, clearly mark "Paid".

Display Rules

** Reference **

Common Display Rules

mo-discover

NPX Install

Tags

SKILL.md Content (Chinese)