SkillAgentSearch skills...

toneforge

Word add-in that checks for consistency across the document and can set a style by training on a style sample

Install / Use

npx skills add Gekko47/ToneForge

Installs into whichever agent you are using.

About this skill
🔧

.clinerules

Cline rules

Quality Score

59/100

Supported Platforms

Cline

Tags

Our assessment of toneforge

toneforge scores 59/100 on our quality scale, 1111th of 1,155 Content & Media skills we index.

Its .clinerules is 4.5 KB long, well organised into 8 sections with 1 code example: a solid amount of guidance for an agent.

It has no GitHub stars yet, so there is no community track record; judge it on its content.

Substance
26/30
Structure
17/20
Description
12/15
Adoption
0/20
Freshness
5/15

Maintenance, license and trust

  • We could not determine when the repository was last updated.
  • Our last check on 2026-11-10 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 68/100, with 3 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-02. Automated pattern scan on 2026-10-01. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

toneforge compared with similar skills

All 4 of these similar skills score higher than toneforge; compare them before choosing.

SkillScoreStarsUpdatedFormat
toneforge (this skill)by Gekko47590—.clinerules
siyuanby siyuan-note10047.3ktodayMCP Server
changelog-videoby heygen-com10083.8k3d agoSKILL.md
content-research-writerby ComposioHQ10079.4k59d agoSKILL.md
ad-creativeby coreyhaines3110060.1k5d agoSKILL.md

Frequently asked questions

How do I install toneforge?
Run npx skills add Gekko47/ToneForge. The install tabs above show the steps for each supported agent.
Which AI agents does toneforge work with?
It is written for Cline, as a .clinerules file. Other agents that read the same format can often use it too.
Is toneforge safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 68/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is toneforge still maintained?
We could not determine when the repository was last updated.

ToneForge Cline Rules

These rules govern how Cline (and other AI coding assistants) interact with the ToneForge repository. They are always active. The path-scoped rules in this directory add detail when you touch the relevant files, and the skills in .cline/skills/ load on demand.

Read before changing anything

  1. ROADMAP.md — the canonical stage ordering, status ledger, hard rules, and release gates. When another document disagrees with it, it wins.
  2. The relevant stage file in docs/stages/.
  3. docs/architecture.md — module boundaries, before adding any import.
  4. docs/decision-log.md — so you do not repeat a rejected decision.

Stage protocol

  1. Read the stage file and the canonical roadmap.
  2. Load only the skills the work actually needs.
  3. Inspect the current implementation before modifying it.
  4. Implement only the agreed stage scope.
  5. Run targeted tests.
  6. Run npm run verify.
  7. Update docs/project-state.md evidence and the ROADMAP status.
  8. Record architectural decisions in docs/decision-log.md.
  9. State the result as PASS / PASS WITH DOCUMENTED LIMITATION / IMPLEMENTED / PARTIAL / BLOCKED / FAIL, and name what remains open.
  10. Commit only after the gate passes.

Hard rules

  • Deterministic first. Anything measurable or safely enumerable is code.
  • AI only where interpretation is necessary. A model is for tone, voice, rhetorical style, semantic flow, register, and meaning-preserving rewrites. AI is optional and never required for deterministic governance.
  • One canonical profile. The same StyleProfile drives both Reformat and Consistency Review; GovernanceProfile is an additive envelope, not a replacement.
  • One mutation path. Rules and UI never mutate Word. Everything flows through ChangePlan → revision adapter → applyReviewedPlan.
  • No credential is ever persisted by the add-in. Not in Office.roamingSettings, not in localStorage, not in the bundle. Keys live in the gitignored .env read by the Node-side development broker, or in the local gateway's memory. ProviderConnection has no secret-capable field.
  • Never commit secrets.
  • Never claim verification you did not perform. The Word-host gate is human and currently open. A mocked result is a typed contract, not an integration.

Known open gates

  • npm run host:matrix reports hosts with 0 fully passing. Real Word verification is manual and recorded in docs/manual-verification.md.
  • Production credential custody is unresolved. The local dev broker is a development stand-in, not a release component.
  • The consistency engine (C1–C10) has never run against a real document or a real model; its checks are uncalibrated heuristics.

A green automated run is never a release claim (ADR-0051).

Skills

Roo Code equivalents live in .roo/ and are kept in sync with these.

Commit conventions

feat(word): add native revision adapter
feat(style): add deterministic style metrics
feat(ai): add resilient provider adapters
spike: verify Word revision and document capabilities
chore: scaffold ToneForge Office add-in
test: complete regression and review pass

Before committing

  • [ ] npm run typecheck passes
  • [ ] npm run lint passes with zero warnings
  • [ ] npm run format passes
  • [ ] npm run secrets:scan passes
  • [ ] npm run docs:validate passes
  • [ ] npm run skills:validate passes
  • [ ] npm run test passes
  • [ ] npm run test:coverage meets the 80% thresholds
  • [ ] npm run build succeeds
  • [ ] npm run validate succeeds
  • [ ] docs/project-state.md evidence updated
  • [ ] docs/decision-log.md updated if an architectural decision was made

npm run verify runs all of these in order.

Related Skills

View on GitHub
GitHub Stars0
CategoryContent
UpdatedNaNy ago
Forks0

Trust signals

68/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

2 medium1 low