skillshare update docs

Documentation Community

Skill notes

Step 1: Detect Changes

Map changed files to affected documentation using this guide: Command docs (website/docs/reference/commands/): cmd/skillshare/<cmd>.go → website/docs/reference/commands/<cmd>.md Flag changes, new subcommands, output format changes Concept docs (website/docs/understand/):

Step 2: Cross-Validate Flags

For each affected command: Read the Go source to extract actual flags and behavior: Read the corresponding doc page: Compare and fix: New flags in code → add to docs with usage example

Step 3: Update Documentation

Apply changes following existing doc conventions: Match heading structure of neighboring doc pages Include CLI examples with expected output Keep flag tables consistent in format

Step 4: Check Built-in Skill

If changes affect user-visible CLI behavior: Read skills/skillshare/SKILL.md Check if the built-in skill description needs updating Verify description stays under 1024 characters (CodeX limit)

Step 5: Check README

Review README.md for sections that may need updates: Recent Updates callout Why skillshare bullet points (5 selling points) Highlights section (core feature examples)

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Documentation
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@runkids · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Detect Changes

Map changed files to affected documentation using this guide: Command docs (`website/docs/reference/commands/`): `cmd/skillshare/<cmd>.go` → `website/docs/reference/commands/<cmd>.md` Flag changes, new subcommands, output format changes Concept docs (`website/docs/understand/`):

02
Step 2: Cross-Validate Flags

For each affected command: Read the Go source to extract actual flags and behavior: Read the corresponding doc page: Compare and fix: New flags in code → add to docs with usage example

03
Step 3: Update Documentation

Apply changes following existing doc conventions: Match heading structure of neighboring doc pages Include CLI examples with expected output Keep flag tables consistent in format

04
Step 4: Check Built-in Skill

If changes affect user-visible CLI behavior: Read `skills/skillshare/SKILL.md` Check if the built-in skill description needs updating Verify description stays under 1024 characters (CodeX limit)

05
Step 5: Check README

Review `README.md` for sections that may need updates: Recent Updates callout Why skillshare bullet points (5 selling points) Highlights section (core feature examples)

06
Step 6: Build Verification

Confirm no broken links or build errors.

07
Step 7: Report

List all changes made with rationale:

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.