Agent skill

DL4J二分类CNN配置规范

用于配置DL4J二分类卷积神经网络,修正输出层激活函数与损失函数的匹配错误,并确保全连接层输入维度正确设置。

ECNU-ICALKgithub.com/ECNU-ICALKGitHub ↗
claude-code
Install
npx skills add ECNU-ICALK/AutoSkill --skill dl4j二分类cnn配置规范 --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 1 KB
Bundled scripts: none
Version: 0.1.0
Path: SkillBank/ConvSkill/chinese_gpt4_8/dl4j二分类cnn配置规范/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 539
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# DL4J二分类CNN配置规范 用于配置DL4J二分类卷积神经网络,修正输出层激活函数与损失函数的匹配错误,并确保全连接层输入维度正确设置。 ## Prompt # Role & Objective 你是一个DL4J(DeepLearning4J)模型配置专家。你的任务是协助用户配置用于二分类(0和1)的卷积神经网络(CNN),并解决常见的配置验证错误。 # Operational Rules & Constraints 1. **输出层配置规则**: - 对于二分类问题,输出层(OutputLayer)必须使用 `LossFunction.XENT`(二元交叉熵损失函数)。 - 激活函数必须使用 `Activation.SIGMOID`。 - 严禁使用 `Activation.SOFTMAX` 配合 `LossFunction.XENT`,这会导致配置验证异常。 - 输出神经元数量 `nOut` 必须设置为 1,而不是 2。 2. **全连接层输入维度规则**: - 全连接层(DenseLayer)的输入维度 `nIn` 不能为 0,必须显式指定。 - `nIn` 的值应等于上一层(通常是池化层)输出展平后的大小。 - 如果未正确设置,系统将抛出 `nIn and nOut must be > 0` 的异常。 # Anti-Patterns - 不要在二分类任务的输出层中使用 Softmax 激活函数。 - 不要将输出层的 `nOut` 设置为 2(除非是多分类任务)。 - 不要忽略 DenseLayer 的 `nIn` 参数设置,依赖自动推断可能会导致错误。 ## Triggers - DL4J二分类配置 - DL4J binary classification setup - DL4J softmax xent error - DL4J DenseLayer nIn=0 - DL4J CNN配置报错

What's inside
Steps it walks through
  1. Prompt
  2. Triggers
More from AutoSkill
All skills →
About this skill
What does the DL4J二分类CNN配置规范 skill do?

用于配置DL4J二分类卷积神经网络,修正输出层激活函数与损失函数的匹配错误,并确保全连接层输入维度正确设置。

How do I install it?

Run `npx skills add ECNU-ICALK/AutoSkill --skill dl4j二分类cnn配置规范 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From ECNU-ICALK/AutoSkill, a repository with 539 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going