tomevault-io Gemini Interactions API
Design Gemini interaction flows with explicit conversation state, tool boundaries, safety review, and reproducible request traces.
Verified Surface
- Provider lane: gemini
- Native surface: Gemini CLI SKILL.md packages
- Harness export: gemini
- Import mode: direct-import-normalized
- Source evidence: load
references/source-evidence.mdbefore promoting third-party material.
Workflow
- Map user intents, conversation state, tool calls, and completion criteria.
- Separate system, developer, user, and tool context in the implementation plan.
- Guard against prompt injection, stale state, and unapproved tool mutation.
- Log redacted request metadata and verification evidence, not raw private prompts.
- Test happy path, refusal path, tool failure, and recovery behavior.
Output Contract
Return:
- provider lane and native surface
- source evidence used
- promotion decision or operating recommendation
- security and privacy notes
- verification still required
Guardrails
- Keep third-party source bodies out of public artifacts unless direct import has clean license, attribution, and manual review.
- Do not use star counts, popularity, screenshots, or social posts as the sole evidence for promotion.
- Do not install or execute unreviewed external scripts as part of source research.
- Quarantine missing licenses, unclear ownership, vague prompt packs, duplicate skill packs, and unsupported native-surface claims.
- Preserve Alex Cinovoj / TechTide ownership for TechTide-authored synthesis while citing third-party sources as references.
Source: TechTideOhio/techtide-harness-kit — distributed by TomeVault.