agentleFS
SuShuhengSuShuheng/obshare-cli/skills/config/SKILL.md

config

Skill2 starsChanged 8 months agoMITView on GitHub

Use when configuring obshare-cli credentials, checking saved settings, testing connectivity, clearing local config, or setting optional Obsidian bridge values used by the V0.2.0 direct-share stack.

24 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use uninstall and resume.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AnthropicSkill

    uninstall

    Uninstall a community skill that was installed via the hub. Confirms before deleting files, refuses to touch first-party plugin skills, and logs every action. Use when the user wants to fully remove a community skill ("uninstall [skill]", "remove this skill") rather than just disable it.

    Also in 3 projects that use this

  • genomewalkerSkill

    resume

    Resume a thread by loading its ~800-token context capsule

    Also in 3 projects that use this

The file

Files
SKILL.md

obshare-cli config

Manage saved configuration for Feishu uploads and optional Obsidian bridge integration. These settings are consumed by both the CLI and the Obsidian companion plugin's direct-share flow in V0.2.0.

Quick Reference

CommandPurpose
set-app-id <app_id>Save Feishu App ID
set-app-secret <app_secret>Save Feishu App Secret
set-user-id <user_id>Save Feishu user ID
set-folder <folder_token>Save target folder token
set-obsidian-cli <command>Save Obsidian CLI command name/path
set-obsidian-bridge-dir <dir>Save shared bridge directory
set-obsidian-command-id <id>Save Obsidian render command ID
showShow current config with sensitive values masked
testTest Feishu connectivity
clearRemove saved local config

Common Usage

# Required Feishu settings
conda run -n obsd obshare-cli config set-app-id "cli_xxx"
conda run -n obsd obshare-cli config set-app-secret "xxx"
conda run -n obsd obshare-cli config set-user-id "ou_xxx"
conda run -n obsd obshare-cli config set-folder "fldcnxxx"

# Optional Obsidian bridge settings for Mermaid rendering
conda run -n obsd obshare-cli config set-obsidian-cli obsidian
conda run -n obsd obshare-cli config set-obsidian-bridge-dir /path/to/shared/bridge
conda run -n obsd obshare-cli config set-obsidian-command-id obshare-cli:process-render-request

# Inspect and test
conda run -n obsd obshare-cli config show
conda run -n obsd obshare-cli --json config show
conda run -n obsd obshare-cli config test

Notes

  • Uploads require app_id, app_secret, user_id, and folder_token.
  • Config is stored in ~/.obshare/config.json.
  • Sensitive fields are stored encrypted when cryptography support is available.
  • --json is a global option: place it before the subcommand, not after show or test.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.