Query foreign LLM for chat. Use this skill if a foreign LLM like OpenAI ChatGPT, Google Gemini, DeepSeek or xAI Grok should be queried with a single chat message.
Scanned 9/1/2026
Install to Claude Code
npx -y skills add rse/ase --skill ase-meta-chat --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Ase Meta Chat?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/rse-ase-meta-chat)More formats (shields.io, HTML) on the badges page.
---
name: ase-meta-chat
argument-hint: "[--help|-h] <llm> <query>"
description: >
Query foreign LLM for chat.
Use this skill if a foreign LLM like OpenAI ChatGPT, Google Gemini,
DeepSeek or xAI Grok should be queried with a single chat message.
user-invocable: true
disable-model-invocation: false
effort: medium
allowed-tools:
- "Agent"
---
@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md
@${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
@${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
<purpose name="ase-meta-chat">
Query Foreign LLM for Chat
</purpose>
<expand name="getopt" arg1="ase-meta-chat">
$ARGUMENTS
</expand>
<objective>
Query foreign LLM for: <query><getopt-arguments/></query>
</objective>
<if condition="<query/> is empty">
Only output the following <template/> and then immediately *STOP*
processing the entire current skill:
<template>
⧉ **ASE**: ✪ skill: **ase-meta-chat**, ▶ ERROR: expected a `<query>` argument
</template>
</if>
1. You *MUST* *NOT* output anything in this step.
Just call the underlying agent with the following tool:
```text
Agent(
description: "Query Foreign LLM for Chat",
subagent_type: "ase:ase-meta-chat",
prompt: <query/>,
run_in_background: false
)
```
2. Output the *plain response* of the `ase:ase-meta-chat` agent
*verbatim* and *without any modifications*. Especially, do *NOT* add or
remove any text from the agent response on your own and do not interpret
the result in any way.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.