instantly-hello-world
Create a minimal working Instantly example. Use when starting a new Instantly integration, testing your setup, or learning basic Instantly API patterns. Trigger with phrases like "instantly hello world", "instantly example", "instantly quick start", "simple instantly code".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill instantly-hello-world71
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-structured skill description with excellent trigger terms and completeness. The main weakness is the lack of specific concrete actions - it describes the purpose (minimal example, quick start) but doesn't detail what the example actually does (e.g., authenticate, send test email, fetch campaigns).
Suggestions
Add 1-2 concrete actions the example performs, e.g., 'Create a minimal working Instantly example that authenticates and fetches campaign data.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Instantly integration) and mentions some actions (testing setup, learning API patterns), but lacks concrete specific actions like 'authenticate', 'send campaign', or 'fetch leads'. | 2 / 3 |
Completeness | Clearly answers both what ('Create a minimal working Instantly example') and when ('Use when starting a new Instantly integration, testing your setup, or learning basic Instantly API patterns') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'instantly hello world', 'instantly example', 'instantly quick start', 'simple instantly code' - good coverage of common variations. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Instantly API specifically with distinct triggers like 'instantly hello world' and 'instantly example' - unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill has good structure and organization but fails at its core purpose: providing a working hello world example. The code snippets are incomplete templates rather than executable examples, which defeats the purpose of a 'minimal working example.' The error handling table is useful but the main content needs actual API calls.
Suggestions
Replace placeholder comments with actual API calls (e.g., fetching account info or listing campaigns) that demonstrate a complete working example
Add a validation step showing how to confirm the connection works (e.g., expected response structure or a simple assertion)
Remove the duplicated TypeScript code between Steps 2-3 and the Examples section - show the complete example once
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Contains some redundancy - the TypeScript example is duplicated in both Step 2/3 and the Examples section. The step-by-step breakdown adds structure but could be tighter. | 2 / 3 |
Actionability | The code examples are incomplete placeholders with '// Your first API call here' comments instead of actual executable API calls. A hello world should show a real working call, not a template. | 1 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but there's no validation checkpoint to confirm the setup works. The 'Output' section describes expected results but doesn't show how to verify success. | 2 / 3 |
Progressive Disclosure | Good structure with clear sections, appropriate length for a hello world skill, and well-signaled references to external docs and next steps. Content is appropriately scoped. | 3 / 3 |
Total | 8 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.