using-stronghelp
Skill4 starsChanged 7 months agoMITView on GitHub
Development and maintenance of StrongHelp manuals for RISC OS. Use when the agent needs to create, edit, or build StrongHelp manuals, or when processing help pages in the StrongHelp format.
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 3 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
Every StrongHelp page is a text file where the first line is the title.
- Very specific: line 27
List the manual: Use riscos-shextract --list to see the real page names and directories before making assumptions about the structure.
- Very specific: line 28
Extract the manual: Use riscos-shextract --extract-dir and inspect the extracted files in the filesystem.
- Distinctive: line 30
Apply Syntax: Use the syntax guide in references/syntax.md for formatting and links.
- Distinctive: line 31
Organize Structure: Use the structure guide in references/structure.md for directory organization and special files.
- Distinctive: line 32
Verify Links: Ensure all links point to valid page names or files.
- Very specific: line 33
Build: Use riscos-strongcopy to package the directory into a .3d6 manual file.
- Very specific: line 42
Inspection: Do not treat a packed ,3d6 manual as plain text and do not run unrelated decoders over it.
- Very specific: line 44
Columns: Use TAB for alignment instead of spaces to ensure correct rendering.
- Very specific: line 45
Formatting: Use #fCode for examples and #H1 for main headers.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
StrongHelp Development
This skill provides guidance for developing StrongHelp manuals, which are the standard hypertext help format for RISC OS.
Quick Start
- List the container contents first:
riscos-shextract --list <manual_file,3d6> - Extract a manual for inspection or editing:
riscos-shextract --extract-dir <dirname> <manual_file,3d6> - Read the extracted page files, not the packed
,3d6bytes directly. - Build a manual:
riscos-strongcopy -o <manual_file,3d6> <directory>
Developing Pages
Every StrongHelp page is a text file where the first line is the title. Use #Parent on every page to ensure navigation works correctly.
Workflow
- List the manual: Use
riscos-shextract --listto see the real page names and directories before making assumptions about the structure. - Extract the manual: Use
riscos-shextract --extract-dirand inspect the extracted files in the filesystem. - Identify the target page: Find the existing page or determine the filename for a new one.
- Apply Syntax: Use the syntax guide in references/syntax.md for formatting and links.
- Organize Structure: Use the structure guide in references/structure.md for directory organization and special files.
- Verify Links: Ensure all links point to valid page names or files.
- Build: Use
riscos-strongcopyto package the directory into a.3d6manual file.
Tools
- riscos-shextract: Extracts contents from a StrongHelp
.3d6container. - riscos-strongcopy: Packages a directory into a StrongHelp
.3d6container.
Best Practices
- Inspection: Do not treat a packed
,3d6manual as plain text and do not run unrelated decoders over it. Extract it first, then read the extracted page files. - Navigation: Include
#Parent !Root(or the appropriate parent) on every page. - Columns: Use
TABfor alignment instead of spaces to ensure correct rendering. - Formatting: Use
#fCodefor examples and#H1for main headers. - Organization: For manuals with many pages, use prefix directories (e.g.,
Wimp_) or first-letter ranges (e.g.,[a-z]). - Filenames: Remember that StrongHelp uses special filenames for redirection (e.g.,
OLD>NEW).
In this repository47 other files it gives its agents.
- allocating-resourcesSkill
- ci-testingSkill
- creating-pull-requestsSkill
- designing-modulesSkill
- porting-to-riscos-cSkill
- reading-assemblySkill
- riscos-commandsSkill
- riscos-desktop-fileractionSkill
- riscos-filer-likeSkill
- riscos-filesystemSkill
- riscos-graphics-convertersSkill
- riscos-network-dcistatisticsSkill
- riscos-network-resolverSkill
- riscos-outputSkill
- riscos-reSkill
- riscos-styleSkill
- riscos-throwbackSkill
- riscos-urls-fetchingSkill
- riscos-urls-launchingSkill
- riscos-wimp-appSkill
- riscos-wimpSkill
- riscos-wimp-templatesSkill
- updating-robe-skillsSkill
- using-bbcbasicSkill
- using-cmhgSkill
- using-ghSkill
- using-gitSkill
- using-libasmSkill
- using-libgcontextSkill
- using-liboslibSkill
- using-libriscoslibSkill
- using-libtoolboxSkill
- using-makefilesSkill
- using-perlSkill
- using-toolbox-imagefilegadgetSkill
- using-tooltesterSkill
- writing-assemblySkill
- writing-assembly-testsSkill
- writing-cmodulesSkill
- writing-cplusplusSkill
- writing-cSkill
- writing-fortranSkill
- writing-oslib-defsSkill
- writing-pascalSkill
- writing-prminxmlSkill
- writing-pymodulesSkill
- writing-pyromaniac-integration-testsSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

