Nokodoko/plugins/org-generator/skills/questionnaire
plugins/org-generator/skills/questionnaire/SKILL.md
# Questionnaire Skill This skill helps users interactively fill out the client questionnaire with intelligent suggestions and validation. ## Detection Patterns This skill activates when: - User is viewing or editing a questionnaire.md file - User asks for help filling out the questionnaire - User mentions specific infrastructure they want to monitor - User is unsure about questionnaire options ## Behavior ### Interactive Mode When helping fill out a questionnaire, this skill: 1. **Reads
tools
Updated Apr 25, 2026
$ install --global
skillsauthnpx skillsauth add Nokodoko/agents plugins/org-generator/skills/questionnaireInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 2:56 PM54.3s1 file scanned
SKILL.md
Questionnaire Skill
This skill helps users interactively fill out the client questionnaire with intelligent suggestions and validation.
Detection Patterns
This skill activates when:
- User is viewing or editing a questionnaire.md file
- User asks for help filling out the questionnaire
- User mentions specific infrastructure they want to monitor
- User is unsure about questionnaire options
Behavior
Interactive Mode
When helping fill out a questionnaire, this skill:
-
Reads current questionnaire state
- Identifies which sections are complete
- Highlights required sections
-
Asks clarifying questions
- Cloud providers in use
- Infrastructure components
- Monitoring requirements
- Team structure
-
Provides recommendations
- Suggests common configurations
- Explains trade-offs
- Recommends best practices
-
Validates responses
- Ensures required fields are filled
- Checks for conflicting selections
- Warns about missing dependencies
Section-by-Section Assistance
Organization Setup
Questions asked:
- Is this a new Datadog organization or existing?
- Will this be a child organization under a parent?
- What's the organization name?
Recommendations:
- Child organizations recommended for client isolation
- Parent org credentials needed for child org creation
Cloud Providers
Questions asked:
- Which cloud providers are in use?
- Are workloads spread across multiple providers?
- Is there a primary cloud provider?
Recommendations:
- Start with primary provider, add others later
- Multi-cloud requires additional integration setup
Infrastructure Components
Questions asked:
- What types of hosts? (Linux, Windows, Solaris)
- Container orchestration? (Kubernetes, ECS, Docker Swarm)
- Serverless functions? (Lambda, Cloud Functions)
- Databases? (RDS, Cloud SQL, Azure SQL)
Recommendations:
- Enable host monitoring first
- Kubernetes requires cluster agent deployment
- Database monitoring may need additional permissions
Services & Applications
Questions asked:
- Web servers? (nginx, Apache, IIS)
- Application servers? (Node, Java, Python)
- Message queues? (RabbitMQ, Kafka, SQS)
- Caching? (Redis, Memcached)
Recommendations:
- APM provides deeper service visibility
- Integration setup varies by service
Monitoring Requirements
Questions asked:
- APM for application tracing?
- RUM for frontend monitoring?
- Synthetic tests for uptime?
- Private locations for internal endpoints?
Recommendations:
- APM recommended for microservices
- RUM requires frontend code instrumentation
- Private locations need dedicated workers
Team Structure
Questions asked:
- How many admin users?
- How many standard users?
- Any read-only stakeholders?
- Role-based access requirements?
Recommendations:
- Limit admin access
- Create role-specific permissions
- Use teams for alert routing
Tagging Strategy
Questions asked:
- Environment naming? (dev, staging, prod)
- Team identifiers?
- Application names?
- Custom tags needed?
Recommendations:
- Consistent tagging is critical
- Use
managed_by:terraformfor all resources - Environment tags enable filtering
Example Interaction
User: "Help me fill out the questionnaire for acme-corp"
Skill:
Let me help you complete the questionnaire for acme-corp.
Section 1: Organization Setup
-----------------------------
Is this a new Datadog organization or will you use an existing one?
Options:
- [ ] Create new child organization (recommended for client isolation)
- [ ] Use existing organization
- [ ] Other
What would you like to select?
User: "New child organization"
Skill:
Great choice for client isolation.
Section 2: Cloud Providers
--------------------------
Which cloud providers does acme-corp use? (Select all that apply)
- [ ] AWS
- [ ] GCP
- [ ] Azure
- [ ] On-premise / VDC
Which ones should I select?
Validation Rules
The skill validates:
| Rule | Validation | |------|------------| | Required sections | Organization, Cloud Providers, Team Structure | | Dependency checks | Private locations requires Synthetics | | Conflict detection | Cannot have both "no containers" and "Kubernetes" | | Completeness | All selected sections must have sub-selections |
Output
When complete, the skill:
- Writes the filled questionnaire to disk
- Provides a summary of selections
- Instructs user to run
/org-generator:apply
Related Skills
Nokodoko/skills
tools
VerifiedTrustedCommunity
--- name: description: --- # Purpose ## Variables # Instructions ## Workflow 1. 2. 3. ## Cookbook <If: > <Than: > <Examples: _if needed_>
SKILL.mdUpdated Apr 25, 2026
Nokodoko/plugins/org-generator/skills/generate
tools
VerifiedTrustedCommunity
# Generate Skill This skill auto-detects when a user wants to set up a new Datadog client infrastructure and triggers the appropriate generation workflow. ## Detection Patterns This skill activates when the user's intent matches: - "Set up Datadog for [client]" - "Create new client infrastructure" - "New client onboarding" - "Generate Datadog terraform for [client]" - "POC setup for [client]" - "Production setup for [client]" - "Onboard [client] to Datadog" - "New organization setup" ## Beh
SKILL.mdUpdated Apr 25, 2026
openclaw/taskflow
tools
VerifiedTrustedCommunity
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
357,764SKILL.mdUpdated Apr 10, 2026
openclaw/extensions/lobster
tools
VerifiedTrustedCommunity
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
357,764SKILL.mdUpdated Apr 10, 2026