doc

Documentation Community

Skill notes

Process

Read existing docs and code. Identify the audience: user, developer, operator, maintainer. Update the smallest relevant document. Include commands, environment variables, and examples when useful. Verify commands if practical.

Self-validation

Before final output, verify: Route, side-effect, and confirmation requirements match metadata. Required artifacts or read-only result are explicit. Verification, blockers, and next route are stated.

Rules

Do not document features that do not exist. Do not create a new docs system for a small change. Keep generated docs concise and maintainable.

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
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@hihol-labs · MIT
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Env read
Network behavior
Local-only
Install commands
None (reference only)

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

Author source file SKILL.md

# Doc

Write documentation that matches the project.

## Process

1. Read existing docs and code.
2. Identify the audience: user, developer, operator, maintainer.
3. Update the smallest relevant document.
4. Include commands, environment variables, and examples when useful.
5. Verify commands if practical.

## Self-validation

Before final output, verify:

- Route, side-effect, and confirmation requirements match metadata.
- Required artifacts or read-only result are explicit.
- Verification, blockers, and next route are stated.

## Rules

- Do not document features that do not exist.
- Do not create a new docs system for a small change.
- Keep generated docs concise and maintainable.

Discussion

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