zhongcao-note-copywriter – skill Khác cho agent AI

Xiaohongshu Copywriter Skill

Overview

Turn a product, experience, topic, or audience brief into Xiaohongshu (REDnote) title options, a readable note body, cover text, hashtags, and a natural comment starter, then render one matching vertical cover, from inside Claude Code, Codex, or OpenClaw. The work is produced on the hosted, paid Beatra service

(mcp.beatra.ai).

This catalog entry is a reviewed pointer, not the executable package. It

contains no client code and performs no Beatra operation by itself. The package

it points to bundles three standard-library Python scripts that make network

calls and store a credential. It has no self-updater: it never downloads

code and never changes its own files. Read

[Install](#install-pinned-verified-approved-twice) and

[Security & Safety Notes](#security--safety-notes) before activating it.

| Pinned identity | Value |

| --- | --- |

| Package | zhongcao-note-copywriter 0.2.6 |

| Source commit | [beatra-ai/xiaohongshu-copywriter-skill@3133588](https://github.com/beatra-ai/xiaohongshu-copywriter-skill/tree/313358800e2c5abc992fffb27b6ba66192a771eb/skills/zhongcao-note-copywriter) (full SHA 313358800e2c5abc992fffb27b6ba66192a771eb) |

| Package tree | ad06fe8adc4ef41f2f77063b011dbfad67b40467 (Git tree ID of skills/zhongcao-note-copywriter at that commit) |

| License | MIT No Attribution (MIT-0) |

The pinned tree holds regular files only (no symlinks, no executable bits, no

binaries). Confirm that with the inspect commands below.

When to Use This Skill

• Use when the user wants Xiaohongshu (REDnote) note copy with a matching cover rendered on Beatra, and accepts that the cover is paid.
• Use when they have agreed to send the cover prompt to a third party.
• Do not use for public Xiaohongshu lookup until the user approves that exact read and its price.
• Do not use for a cover built from the user's photos or several references; that is zhongcao-cover-maker.

Install (pinned, verified, approved twice)

Step 1: Fetch the pinned tree into a review directory

Explain that this fetches an external package from github.com, then ask

for approval. Only after approval:

set -e
umask 077
review_dir="$(mktemp -d)"
cd "$review_dir" || exit 1
git clone --quiet --filter=blob:none --no-checkout https://github.com/beatra-ai/xiaohongshu-copywriter-skill.git src
git -C src checkout --quiet 313358800e2c5abc992fffb27b6ba66192a771eb -- skills/zhongcao-note-copywriter
test "$(git -C src rev-parse '313358800e2c5abc992fffb27b6ba66192a771eb:skills/zhongcao-note-copywriter')" = 'ad06fe8adc4ef41f2f77063b011dbfad67b40467' && echo TREE-OK

Stop if the last command does not print TREE-OK. The expected commit and

tree IDs come from this catalog entry, not from the package or its website,

and Git addresses every fetched object by its hash.

Step 2: Inspect before activation

git -C src ls-tree -r 313358800e2c5abc992fffb27b6ba66192a771eb -- skills/zhongcao-note-copywriter | awk '$1 != "100644"'  # expect no output
grep -n -E 'maybe_auto_update|download_update|_apply_update' src/skills/zhongcao-note-copywriter/scripts/mcp_client.py  # expect no output

The first check lists any symlink, executable, or submodule entry; the second

finds the entry points of the self-updater that earlier versions shipped.

Report to the user what the review found: SKILL.md, manifest.json,

install-source.json (the one-line marker {"schema_version":1,"source":"github"}),

the bundled Markdown references, and scripts/authorize.py,

scripts/mcp_client.py, scripts/uninstall.py (Python 3.10+, standard

library only, no dependency installation, no lifecycle hooks). Summarize the

network, credential, local-state, telemetry, and version-notice behavior

listed under [Security & Safety Notes](#security--safety-notes).

The manifest and pattern scans above are only inventory aids. Before activation, read every file in the pinned tree, including each script, reference and hook, and inspect all dependency and network behavior. Do not claim source review from grep output. If complete review cannot be performed, stop before copying or executing; ask for a separate review rather than treating a digest as evidence of safety.

Step 3: Copy in

Ask for a second, separate approval, because this changes agent

configuration. Then copy the reviewed tree to the host's skills directory

(Claude Code shown; use the equivalent path for other hosts):

dest="$HOME/.claude/skills/zhongcao-note-copywriter"
test ! -e "$dest" && test ! -L "$dest" || { echo "destination exists; stop and ask the user"; exit 1; }
cp -R "src/skills/zhongcao-note-copywriter" "$dest"

There is no update switch to turn off in this version.

Step 4: Authorize as its own decision

Authorization opens a browser sign-in and stores a bearer token. Ask first.

python3 "$dest/scripts/authorize.py"

Start a new agent session if the host discovers skills only at startup.

How It Works

1. Read the installed package's SKILL.md and its references; they define the

routes, payload shapes, and review loop.

2. Use free, non-billable discovery first (beatra.models.list, task list) to

read current model cards and credit estimates.

3. Show the user a cost card for exactly one paid call: tool, model, estimate,

and which files will be uploaded. Wait for explicit approval. Planning or

"just do it" is not approval.

4. Upload only files the user supplied and approved for this task, then submit

once with a stable client_request_id and poll the returned task.

5. Report the delivered artifact and billing.net_charged_credits, review the

result with the user, and ask again before any further paid stage.

Examples

Free connection check (non-billable)

python3 "$HOME/.claude/skills/zhongcao-note-copywriter/scripts/mcp_client.py" verify

One approved paid call

After the user approved the cost card for this exact payload, submit once with

a stable request id using the tool name from the installed SKILL.md. If the

response is lost, retry only with the same client_request_id and identical

arguments; never submit a replacement while the task is running.

Update

This pinned version cannot update itself: it has no code that downloads or

replaces package files. update only reports what the store or tool that

installed the copy offers; for a copy installed by the steps above it finds

no such record and says to update the way you installed it. See the version

notice under [Security & Safety Notes](#security--safety-notes).

To move to a newer version, repeat Steps 1 to 3 for that commit in a new

review directory, show the user the file-level changes against the installed

copy (for example git -C src diff --stat 3133588 <new-commit> -- skills/zhongcao-note-copywriter),

and replace the directory only after approval. A version not listed in this

entry has not been reviewed here.

Uninstall

dest="$HOME/.claude/skills/zhongcao-note-copywriter"
python3 "$dest/scripts/uninstall.py" --dry-run
python3 "$dest/scripts/uninstall.py"

Read the JSON decision. disconnected means this was the last Beatra skill on

the device: the token was revoked (when revoked is true), the files

credentials.json, installation.json, host.json, skills.json,

network.json, balance-holds.json, pending_authorization.json, and

.authorize.lock under ~/.beatra were removed, and so were the records

state.json, source.json, registration.json, and update.lock in each

~/.beatra/updates/<id>/. A directory is removed only once it is empty; the

script never deletes recursively and leaves anything it does not know, such

as an interrupted update's transaction/. keep_connection means another

Beatra skill still uses the shared token, which stays. revoke_retry means

the server refused the revocation and nothing changed; run it again shortly.

The script never deletes the package directory: after confirming the path it

prints with the user, delete $dest.

If anything is still under ~/.beatra after a disconnected decision, show

it to the user before removing it. A token that could not be revoked expires

after 15 days idle and can be revoked at once in the Beatra Console under

Agents.

Best Practices

• ✅ Keep one approval per paid call, per upload set, and per install step.
• ✅ Report net charged credits from the terminal task, not the estimate.
• ❌ Do not replace the installed copy with an unreviewed version silently.
• ❌ Do not print, paste, or move the token out of ~/.beatra/credentials.json.
• ❌ Do not retry a paid call with a new request ID after an uncertain response.

Limitations

• Requires a Beatra account, network access, Python 3.10+, and prepaid credits.
• Models, prices, schemas, and availability are controlled by Beatra and its

upstream model providers and can change; the service is provided as is.

• Outputs are probabilistic, not guara

… (nội dung đầy đủ có trong gói tải về)