Skip to content

Document TweetClaw skill install example#154

Open
kriptoburak wants to merge 2 commits into
runkids:mainfrom
kriptoburak:codex/add-tweetclaw-install-example
Open

Document TweetClaw skill install example#154
kriptoburak wants to merge 2 commits into
runkids:mainfrom
kriptoburak:codex/add-tweetclaw-install-example

Conversation

@kriptoburak
Copy link
Copy Markdown

Type

  • Bug fix
  • Small improvement (docs, typo, minor refactor)
  • Feature proposal (proposals/ only - see CONTRIBUTING.md)

Linked Issue

No issue. This is a small docs-only install example.

Summary

  • Add TweetClaw as a concrete OpenClaw nested-path install example.
  • Show skillshare install Xquik-dev/tweetclaw/skills/tweetclaw --track in the install command docs.
  • Explain why the nested path installs only the tweetclaw skill and leaves package/plugin files outside the skill path.

Validation

  • git diff --check
  • Added-line banned dash scan
  • Added-line sensitive-value scan
  • Isolated temp config install of Xquik-dev/tweetclaw/skills/tweetclaw
  • Isolated temp config install of Xquik-dev/tweetclaw/skills/tweetclaw --track
  • npm ci in website/
  • npm run build in website/

Note: npm ci reported 42 existing vulnerabilities in the website dependency tree, and the Docusaurus build emitted an existing webpack warning from vscode-languageserver-types. This PR only edits one docs markdown file.

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the documentation for the install command by adding examples of installing skills from nested GitHub paths. The review feedback suggests refining the descriptive text for the TweetClaw example to be more concise and focused on the installation mechanism rather than listing specific features, while also correcting grammatical errors.

When specifying a subdirectory path like `owner/repo/skill-name`, if the exact path doesn't exist in the repo, skillshare scans all `SKILL.md` files and matches by directory basename. If multiple skills share the same name, an ambiguity error is shown with full paths so you can specify the exact one.
:::

For example, `Xquik-dev/tweetclaw/skills/tweetclaw` installs TweetClaw's OpenClaw skill for search tweets, search tweet replies, post tweets, post tweet replies, follower export, user lookup, media workflows, monitor tweets, webhooks, and giveaway draws from the TweetClaw repository while leaving the package and plugin files outside the skill path.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The description of the TweetClaw skill is overly verbose for a command reference and contains grammatical issues (e.g., 'for search tweets' should be 'for searching tweets'). Since this is a reference for the install command, the focus should remain on the behavior of the nested path installation rather than listing every feature of the example skill.

Suggested change
For example, `Xquik-dev/tweetclaw/skills/tweetclaw` installs TweetClaw's OpenClaw skill for search tweets, search tweet replies, post tweets, post tweet replies, follower export, user lookup, media workflows, monitor tweets, webhooks, and giveaway draws from the TweetClaw repository while leaving the package and plugin files outside the skill path.
For example, `Xquik-dev/tweetclaw/skills/tweetclaw` installs the TweetClaw automation skill from its nested location in the repository. This ensures only the skill directory is installed, leaving top-level package and plugin files outside the skill path.

@kriptoburak
Copy link
Copy Markdown
Author

Updated in 308cb19.

Changes:

  • Replaced the feature list with a concise nested-path install explanation, matching the Gemini review suggestion.

Validation:

  • git diff --check
  • Markdown smoke check for the TweetClaw install example
  • changed-diff scan for blocked terms and private wording

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant