← Back to Skills Marketplace
junetic

User Interview

by Junetic · GitHub ↗ · v1.0.2 · MIT-0
cross-platform ⚠ suspicious
271
Downloads
0
Stars
0
Active Installs
3
Versions
Install in OpenClaw
/install user-interview
Description
Run real user interviews via Usercall. Use when you need qualitative feedback from real users — onboarding drop-off, feature confusion, pricing clarity, prot...
Usage Guidance
This skill appears to do what it says (create and manage Usercall studies) but be cautious before installing or running it: - The SKILL.md requires USERCALL_API_KEY, yet the package metadata does not declare that — treat this as a packaging inconsistency and verify before trusting the skill. - The instructions explicitly echo your API key (echo "$USERCALL_API_KEY"). That prints your secret into the terminal/agent logs and can leak it. Do not run steps that print secrets; instead set the env var without echoing it. - Only provide a Usercall key you control; prefer a limited-scope or revocable key and rotate it after testing. Avoid pasting the key into chat messages. - Confirm that network calls go to https://app.usercall.co (as shown) and that you trust that service. - Consider asking the skill author (or the registry owner) to update the package metadata to declare USERCALL_API_KEY and to remove the echo step so secrets are never printed. If you understand and accept these risks (and use a scoped/revocable key), the skill's functionality is otherwise aligned with its description.
Capability Analysis
Type: OpenClaw Skill Name: user-interview Version: 1.0.2 The skill bundle provides a legitimate integration with the Usercall service (app.usercall.co) for conducting user interviews. It uses standard Bash commands and curl to interact with the service's API using a user-provided environment variable (USERCALL_API_KEY), with no evidence of data exfiltration, malicious execution, or prompt injection.
Capability Assessment
Purpose & Capability
The SKILL.md clearly targets Usercall and only needs a Usercall API key to create studies and fetch results, which is coherent with the stated purpose. However, the registry metadata listed under this bundle claims no required env vars while the instructions require USERCALL_API_KEY — an inconsistency between what the skill 'claims' and what it 'needs'.
Instruction Scope
Runtime instructions limit network calls to app.usercall.co and provide specific curl examples (expected). However, the instructions instruct the agent to run `echo "$USERCALL_API_KEY"` which will print the secret to the terminal/logs and can leak it in transcripts or logs. The SKILL.md also uses $ARGUMENTS (platform-provided) and tells the agent to accept media URLs — these are reasonable, but the explicit echo of the API key is an unnecessary and risky step.
Install Mechanism
Instruction-only skill with no install spec and no code files — lowest install risk. All network calls are to the documented app.usercall.co API.
Credentials
Requesting a single USERCALL_API_KEY is proportionate to the described functionality. But the manifest metadata omission (it didn't declare the required env var) and the instruction to echo the key increases the chance of accidental credential exposure. Consider whether a scoped/revocable key can be used and whether the skill could avoid printing the secret.
Persistence & Privilege
The skill does not request permanent/always-on presence and uses normal, user-invocable defaults. It does not modify other skills or request elevated platform privileges.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install user-interview
  3. After installation, invoke the skill by name or use /user-interview
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.2
- Updated skill description to clarify that only the USERCALL_API_KEY environment variable is required—no other credentials or installs needed. - No functional or command changes; usage instructions remain the same.
v1.0.1
user-interview 1.0.1 changelog - Switched from MCP-based integration to direct API usage via Bash and cURL commands. - Instructions now guide users to set USERCALL_API_KEY as an environment variable, removing MCP config steps. - Clearer, Bash-oriented setup for running and managing studies. - Expanded and clarified API usage examples for creating studies, checking status, updating slots, and fetching results. - Updated media attachment guidance (supports Figma prototypes and image URLs).
v1.0.0
user-interview 1.0.0 - Initial release enabling real user interviews via Usercall integration - Guides setup if Usercall MCP tools are not configured - Supports creating interview studies with research goals, participant numbers, and optional prototypes/images - Provides clear instructions and formatted results, including themes and verbatim quotes - Allows users to add interview slots and check study status
Metadata
Slug user-interview
Version 1.0.2
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 3
Frequently Asked Questions

What is User Interview?

Run real user interviews via Usercall. Use when you need qualitative feedback from real users — onboarding drop-off, feature confusion, pricing clarity, prot... It is an AI Agent Skill for Claude Code / OpenClaw, with 271 downloads so far.

How do I install User Interview?

Run "/install user-interview" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is User Interview free?

Yes, User Interview is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does User Interview support?

User Interview is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created User Interview?

It is built and maintained by Junetic (@junetic); the current version is v1.0.2.

💬 Comments