B24 LaunchKit: Bitrix24 app documentation skills
B24 LaunchKit Skills
Five Codex skills that walk a Bitrix24 app from project facts to marketplace-ready copy: manual, positioning, description, final review
- 0 ★ on the repository
- Last commit
- MIT
Minimal access
Why this level
- It only writes local Markdown artifacts under docs/launchkit and does not call external systems
- It requires launching subagents that perform file operations in the project
Install
- Works in
- Services
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/b24-launchkit-skillsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- It only writes local Markdown artifacts under docs/launchkit and does not call external systems
- It requires launching subagents that perform file operations in the project
This is third-party code. Review the repository files before installing.
What it does
The set implements a strict documentation pipeline: b24-manual extracts confirmed facts about the app from the codebase and writes a factual user manual, b24-positioning turns it into a positioning brief with audience, value and an explicit do-not-claim list, b24-description writes public marketplace copy (headline, description, FAQ) without inventing capabilities, and b24-reviewer checks every artifact against the facts and the rules. The b24-launchkit orchestrator runs these stages through subagents in order and will not jump straight to marketing copy unless the user explicitly asks for a shortened route. Results are saved under docs/launchkit/ with a language suffix in the file name.
Who it is for. For Bitrix24 developers and partners who need a manual and marketplace copy without invented capabilities.
Good fit when
- You need a factual user manual built from the project's code, not from memory
- You are preparing or updating an app description for the Bitrix24 marketplace
- You need a final check that the copy matches the stated facts before publishing
Not a fit when
- You use an agent other than Codex: the install targets the Codex skills directory
- You just want a quick draft without the full review cycle: the pipeline defaults to strict and sequential
Example request
Prepare documentation for publishing this Bitrix24 app in the marketplaceLimitations
Install and validation target Codex (${CODEX_HOME:-$HOME/.codex}/skills); there is no explicit support for other agents. The orchestrator requires a subagent launch tool; without one in the environment, work stops before producing artifacts and the agent should ask whether to continue in the current dialog. Multi-language autogeneration and multi-marketplace formatting are stated as out of scope for the MVP.
How to disable. Delete the skills/b24-launchkit, skills/b24-manual, skills/b24-positioning, skills/b24-description and skills/b24-reviewer folders from the Codex skills directory.
FAQ
Can I skip the manual and get marketplace copy right away?
Yes, but only if you explicitly ask for the shortened route; by default the orchestrator runs the full pipeline: manual, positioning, description, review.
Does the skill search the web for marketplace requirements?
No, it does not browse for publication rules by default unless you explicitly ask for current external research.
Discussion
No questions or reviews yet.
Related
All Bitrix24 toolsCodex skills for Bitrix development
Bitrix Agent Skills (Core)
Four Codex skills for Bitrix and Bitrix24 development: project audit and architecture, migrating tables to Grid, FTP deploy and incident triage
A skill for administering, diagnosing and developing boxed Bitrix24 and Bitrix Framework, built from official documentation
Bitrix24 app development skill pack
bitrix24-skills-emcsoft
Four skills for Bitrix24 apps: install and OAuth, a batching REST client, events and iframe placements, CRM business processes and calendar
The @bitrix24/b24jssdk skill set
@bitrix24/b24jssdk skills
Seven official Bitrix24 skills for the JS/TS SDK: picking B24Hook, B24Frame or B24OAuth, REST calls, filters, iframe managers and 12 ready mini-apps
Bitrix24 PHP SDK developer skill
Bitrix24 PHP SDK
A skill for Bitrix24's official PHP SDK that teaches an agent to wire up webhooks and OAuth, call SDK services, and handle results, errors and pagination
A skill for building on VibeCode Bitrix24: docs routing, keys and auth, Black Hole deployment and common mistakes
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| B24 LaunchKit: Bitrix24 app documentation skills (this card) | no | 0 | |
| awesome-gamedev-agent-skills | no | 8,686 | a skill router |
| Design Judge Skills | no | 709 | award submission skills |
| Journalism agent skills | no | 452 | plugins for journalists and source checking |
README in short
The README describes the five skills and their roles, the pipeline from intake to final review, the full and shortened routes, the artifact file format with a language suffix, installation via install-local-skills.sh with symlinks or copies, validation through validate-skills.sh, and explicitly scoped MVP boundaries.
README badge
Original SKILL.md
--- name: b24-launchkit description: Use when a Bitrix24 app developer needs release or marketplace documentation, including user manuals, positioning briefs, marketplace descriptions, or improvement of existing app publication text. --- # B24 App LaunchKit ## Goal Orchestrate public documentation work for Bitrix24 applications. Help developers and partners turn project evidence, manuals, and old copy into clear user-facing materials for release and marketplace publication. This is the entry skill for the B24 App LaunchKit group. ## Operating Rule Do not jump straight to marketplace copy unless the user explicitly asks for that shortened route. Default to a strict artifact pipeline: intake -> user manual -> positioning brief -> marketplace description -> reviewer final claim review The orchestrator must make each artifact visible before moving to the next one. Later artifacts must be based on earlier artifacts, not on fresh assumptions.