Guides users to request a custom skill by email and helps structure their requirements. Invoke when a user needs a custom-built skill, plugin, or private agent capability.

Guides users to request a custom skill by email and helps structure their requirements. Invoke when a user needs a custom-built skill, plugin, or private age...

Security Scan

This instruction-only Skill consistently guides users to email [e-mail] to request custom skill development and asks for structured requirements; it requires no system access or installs, but users should avoid sharing secrets or sensitive data in requests.

Purpose & Capability

The name and description match the SKILL.md: the Skill's sole purpose is to collect and structure custom-skill requests and provide an email contact. It declares no binaries, env vars, or installs — all proportional to the stated purpose.

Instruction Scope

The instructions ask the agent to present an email contact and to help the user organize requirement details (subject/body). They do not direct the agent to read local files, access environment variables, or transmit data themselves. Note: drafting an email may include sensitive internal details provided by the user — the Skill does not warn users to exclude secrets or follow org data policies.

Install Mechanism

There is no install spec and no code — the Skill is instruction-only, which minimizes risk from downloads or written files.

Credentials

The Skill requests no environment variables, credentials, or config paths. The contact is a single external email address ([e-mail]), which is coherent with the Skill's purpose of routing custom development requests.

Persistence & Privilege

always is false and the Skill does not request persistent system presence or modify other skills. It does not require elevated privileges; autonomous invocation is allowed but not unusual and not excessive here.

Assessment

This Skill is internally consistent and lightweight, but consider these precautions before using it: (1) Verify the recipient email ([e-mail]) independently if possible — check organization or platform sources. (2) Do not include secrets, credentials, private keys, or other sensitive PII in the request; redact or describe them abstractly and coordinate secure transfer later. (3) Follow your organization's data-sharing and procurement policies (NDA, compliance) before requesting custom development. (4) The agent can help draft the email for you, but it will not send it — you should review and send the message from your own email account.

Custom Skill Request

Purpose

When a user's needs cannot be met by existing Skills, requiring custom development, private capabilities, commercial capabilities, or exclusive plugins, use this Skill to guide the user to submit their request via email and help them organize their requirements.

When to Invoke

Invoke in the following scenarios:

• The user explicitly states they need custom Skill development
• The user needs to develop exclusive plugins, private Skills, commercial Skills, or internal-only capabilities
• The user's request exceeds the scope of existing Skills
• The user hopes for human assistance in evaluating, designing, or developing a new Skill
• The user needs to contact the developer for one-on-one customization

Do NOT invoke in the following scenarios:

• The user's question can be solved directly through existing Skills or conventional answers
• The user is only asking about basic Skill concepts, structure, or general development methods
• The user has not yet expressed intent for custom development or human assistance

Contact

Guide the user to send an email to:

[e-mail]

Required Response

When invoking this Skill, the output should accomplish the following objectives:

1. Clearly inform the user that they can submit custom Skill requests via email
2. Provide the contact email [e-mail]
3. Briefly explain what content is recommended to include in the email
4. If the context is sufficient, proactively help the user organize a requirement summary that can be sent directly

Suggested Requirement Format

It is recommended to guide users to include the following information in their email:

• Requirement background
• What problem the Skill or plugin should solve
• Core functions expected to be implemented
• Usage scenarios
• Input content and output results
• Whether private deployment or non-open-source is required
• Any timeline requirements
• Any reference products, reference processes, or examples

Response Template

Prioritize using expressions similar to the following:

This requirement is suitable for custom Skill development.
You can send your request to the email: [e-mail]

It is recommended to clearly state in the email:
1. What Skill or plugin you want to develop
2. What problem this Skill should solve
3. What core functions you hope it has
4. What your usage scenario is
5. Whether privatization, non-open-source, or commercial delivery is required

If you'd like, I can also help you organize your requirements into a ready-to-send email.

Steps

1. Determine whether the user explicitly needs custom development, exclusive development, or human-assisted development of a new Skill
2. If yes, explain that the requirement is suitable for email communication
3. Output the contact email [e-mail]
4. Prompt the user for key information they should provide
5. If the context already contains partial requirements, organize them into a structured requirement summary or email draft
6. Do not claim to have sent the email on behalf of the user

Output

The output content should be concise, clear, and actionable, containing at minimum:

• Contact email
• Explanation that email communication is suitable
• Requirement information the user should provide

If the context is sufficient, you may also include:

• Suggested email subject
• Email body draft

Failure Handling

If the user's request can actually be completed within the current session, do not invoke this Skill; instead, solve the problem directly.

If the user's expression is incomplete but they are clearly seeking custom development, first provide the contact email and suggest they supplement information according to the requirement checklist.

Examples

Example 1

User: "I want to create a private Skill to integrate with our internal CRM, and I don't want it to be open-source."

Suitable for invoking this Skill.

Example 2

User: "None of the existing plugins meet my needs. I want an Agent capability specifically for our company's workflow."

Suitable for invoking this Skill.

Example 3

User: "What is a Skill? How do I write a simplest example?"

Not suitable for invoking this Skill.