functions-development
Build serverless Go or Python functions for Falcon Foundry apps. TRIGGER when user asks to "create a function", "write a serverless function", "build backend logic", runs `foundry functions create`, or needs help with FDK handler patterns, function testing, or collection integration from functions. DO NOT TRIGGER for calling Falcon platform APIs from functions — use functions-falcon-api instead. DO NOT TRIGGER for workflow YAML or UI components.
86
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 an excellent skill description that hits all the marks. It provides specific capabilities, rich trigger terms covering both natural language and CLI commands, explicit when-to-use and when-not-to-use guidance, and clear boundaries against related skills. The DO NOT TRIGGER exclusions are particularly valuable for preventing conflicts in a multi-skill environment.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: building serverless Go or Python functions, FDK handler patterns, function testing, collection integration. Also specifies the platform context (Falcon Foundry apps). | 3 / 3 |
Completeness | Clearly answers both 'what' (build serverless Go/Python functions for Falcon Foundry apps) and 'when' (explicit TRIGGER clause with multiple scenarios). Also includes explicit DO NOT TRIGGER exclusions to prevent misuse, which strengthens the 'when' guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'create a function', 'write a serverless function', 'build backend logic', 'foundry functions create', 'FDK handler patterns', 'function testing', 'collection integration'. Includes both user-facing phrases and CLI commands. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with explicit boundary-setting via two DO NOT TRIGGER clauses that delineate this skill from 'functions-falcon-api' (for API calls) and workflow YAML/UI components. The niche of serverless function creation for Falcon Foundry is very specific. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-structured skill that provides actionable, executable guidance for building Foundry serverless functions in both Go and Python. Its main strengths are comprehensive code examples, clear progressive disclosure with well-organized references, and a useful common pitfalls section. The primary weaknesses are the unnecessary 'SYSTEM INJECTION' framing, some verbose explanatory sections, and the lack of an explicit end-to-end workflow with validation checkpoints.
Suggestions
Remove or drastically shorten the 'SYSTEM INJECTION' block — it's verbose role-play framing that wastes tokens and Claude doesn't need to be told its role this way.
Add an explicit end-to-end workflow section (e.g., 'scaffold → implement handler → write tests → run tests locally → deploy → verify') with validation checkpoints at each step.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary content. The 'SYSTEM INJECTION' block at the top is verbose role-play framing that wastes tokens. The 'Functions as a Last Resort' section explains alternatives Claude could infer. The language comparison table and some explanatory prose could be tightened. However, most code examples and tables are lean and informative. | 2 / 3 |
Actionability | The skill provides fully executable code examples for both Go and Python FDK patterns, CLI scaffolding commands, manifest YAML, authentication patterns, error handling, and requirements.txt. Examples are copy-paste ready with specific imports, function signatures, and response structures. The common pitfalls section provides concrete anti-patterns with corrections. | 3 / 3 |
Workflow Clarity | While individual patterns are clear, there's no explicit end-to-end workflow with validation checkpoints for creating and deploying a function. The CLI scaffolding is shown but there's no sequence like 'scaffold → implement → test → validate → deploy' with verification steps. For a skill involving deployment and runtime operations, explicit validation/testing steps in the main flow would strengthen this. | 2 / 3 |
Progressive Disclosure | The skill has a clear reference table at the top pointing to python-patterns.md, go-patterns.md, and testing-patterns.md for detailed implementations. Use cases and reference implementations are linked at the bottom. The main file provides enough context to get started while deferring deep patterns to one-level-deep references. Navigation is well-signaled with a table format. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
- Repository
- CrowdStrike/foundry-skills
- Commit
e7fa026
- 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.